OmniChat Harness

MCP开发工具

提供方 未标注

开发工具 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

支持双协议的本地 AI 网关和 MCP 智能体运行框架,适用于 Claude Desktop、Cursor 和 OpenAI 工具。

一句话选型结论

按资料字段整理

OmniChat Harness 属于开发工具类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权API Key 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

开发

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
# Start server immediately using bunx or npx bunx omnichat start --port 3132 # Or launch the terminal monitoring dashboard bunx omnichat tui

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
OmniChat Harness当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

14.6 KB
来自项目仓库与上游目录的原文,未做删改

OmniChat Harness

One Gateway. All AI.

Dual-protocol local AI gateway that drives web AI interfaces through headless browser sessions.

Drop-in compatible with OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) wire protocols.

> Building this in the open — if it saves you time, a star helps others find it.
> Found a bug, or have an idea? Open an issue.
> New here? Start with a good first issue.
> Questions and ideas? Say hello in Discussions.
> New provider adapters and protocol ideas welcome.


Overview

OmniChat Harness is a local API proxy that bridges AI developer agents (OpenCode, Claude Code, Cursor, Cline, Aider, LangChain) with consumer AI chat web interfaces (ChatGPT, Claude, Perplexity, and Gemini).

Instead of requiring paid API token credits for every single token query during local coding and experimentation, OmniChat runs local, headless Chromium browser sessions in the background, coordinates mouse/keystroke execution, and exposes drop-in compatible standard HTTP endpoints.```
┌────────────────────────────────────────────────────────────────────────────────┐
│ AI Agents, Developer Tools & Frameworks │
│ OpenCode · Claude Code · Cursor · Cline · Aider · OpenAI SDK · Anthropic │
└───────────────────────┬────────────────────────────────┬───────────────────────┘
│ OpenAI Wire Protocol │ Anthropic Wire Protocol
│ POST /v1/chat/completions │ POST /v1/messages
▼ ▼
┌────────────────────────────────────────────────────────────────────────────────┐
│ OmniChat Gateway (:3132) │
│ │
│ ├── Universal Base URL Router (supports /v1, root /, /api/v1, /v1/v1) │
│ ├── Dual Protocol Normalizer (OpenAI JSON/SSE ↔ Anthropic Messages/SSE) │
│ ├── Fuzzy Model Alias Engine (gpt-4o, claude-3-5-sonnet, gemini-pro) │
│ ├── Universal Tool Call Parser (Markdown JSON, XML, bare objects) │
│ └── Automatic Router Failover & Health Checks │
└───────────────────────┬────────────────────────────────┬───────────────────────┘
│ │
▼ ▼
┌───────────────────────────────────┐ ┌───────────────────────────────────┐
│ Playwright Stealth Pool │ │ AES-256-GCM Session Vault │
│ • Headless Chromium Engine │ │ • Zero-login anonymous support │
│ • Native coordinate mouse clicks │ │ • Encrypted cookies & storage │
│ • Non-empty stability poll loops │ │ • Zero secrets in server logs │
└─────────────────┬─────────────────┘ └─────────────────┬─────────────────┘
│ │
▼ ▼
┌──────────────┬──────────────┬──────────────┬──────────────┐
│ ChatGPT │ Claude Web │ Perplexity │ Gemini │
│ (Web UI) │ (Web UI) │ (Web UI) │ (Web UI) │
└──────────────┴──────────────┴──────────────┴──────────────┘


---

## Key Features

- **Dual-Protocol Gateway:**
  - **OpenAI Compatible (`POST /v1/chat/completions`):** Full support for Server-Sent Events (`stream: true`), non-streaming completions, and model discovery (`GET /v1/models`).
  - **Anthropic Compatible (`POST /v1/messages`):** Native support for Anthropic Messages API, `x-api-key` authentication, and the Anthropic streaming lifecycle (`message_start` → `content_block_delta` → `message_stop`).
- **Universal Base URL Normalization:**
  - Works with any base URL configuration: `http://localhost:3132/v1`, root `http://localhost:3132`, OpenRouter style `http://localhost:3132/api/v1`, or nested `/v1/v1`.
- **Full Tool & Function Calling:**
  - Accepts standard tool definitions (`tools` in OpenAI schema or `input_schema` in Anthropic schema).
  - Automatically parses tool executions (JSON blocks, XML tags, or raw objects) and delivers structured `tool_calls` / `tool_use` back to the calling agent.
- **Fuzzy Model Aliasing & Graceful Failover:**
  - Request standard commercial model identifiers (`gpt-4o`, `gpt-4`, `claude-3-5-sonnet`, `gemini-1.5-pro`, `sonar-medium`).
  - Automatically routes to the optimal backend and fails over to active providers if a provider is unauthenticated.
- **Zero-Login & Encrypted Session Persistence:**
  - Headless anonymous operation for ChatGPT and Perplexity out of the box.
  - Interactive login wizard (`bun run session:init`) saving AES-256-GCM encrypted browser cookies to `data/sessions/`.
- **Interactive ANSI Terminal Dashboard (`@omni/tui`):**
  - Standalone terminal monitoring dashboard providing real-time provider readiness, browser context states, and health metrics.

---

## Execution Modes

Every request routes dynamically based on the requested `model` parameter:

### 1. Direct Passthrough (`chatgpt`, `gemini`, `claude-web`, `perplexity`)
Zero overhead. Routes directly to the designated provider's web session:```json
{ "model": "chatgpt" }    // Direct ChatGPT headless session
{ "model": "perplexity" } // Direct Perplexity real-time search
{ "model": "claude-web" } // Direct Claude session
{ "model": "gemini" }     // Direct Gemini session (1M context)

2. Commercial Aliases (Automatic Resolution)

You don't need to reconfigure hardcoded model strings in your agents:```json
{ "model": "gpt-4o" } // Resolves to ChatGPT
{ "model": "claude-3-5-sonnet" } // Resolves to Claude (fails over to ChatGPT if offline)
{ "model": "gemini-1.5-pro" } // Resolves to Gemini
{ "model": "sonar-medium" } // Resolves to Perplexity


### 3. Multi-Provider Orchestration (`omni-*`)
OmniChat plans, fans out requests in parallel across multiple providers, and synthesizes results:```json
{ "model": "omni-code" }      // ChatGPT generates, Claude reviews, Gemini explains
{ "model": "omni-research" }  // Gemini researches, Perplexity cites, Claude analyzes
{ "model": "omni-fast" }      // Automatically routes to the fastest available provider
{ "model": "omni-consensus" } // All providers in parallel, synthesized by majority agreement

Quick Start

Option A: Instant CLI Run (Zero Setup)```bash

Start server immediately using bunx or npx

bunx omnichat start --port 3132

Or launch the terminal monitoring dashboard

bunx omnichat tui


---

### Option B: From Source (Recommended for Local Dev)

#### 1. Prerequisites
- Bun (v1.1 or higher)
- Google Chrome, Chromium, or Microsoft Edge installed on your machine```bash
# Clone the repository
git clone https://github.com/ziuus/omnichat-harness.git
cd omnichat-harness

# Install dependencies across all monorepo packages
bun install

2. Configure Environment```bash

cp .env.example .env

Default configuration uses port `3000` (or set `PORT=3132`):```ini
PORT=3132
OMNI_API_KEY=omni-local-dev-key
SESSION_ENCRYPTION_KEY=dev-key-change-in-production!!
BROWSER_HEADLESS=true

3. Launch the Server```bash

Start server in development mode (with hot reloading)

bun run dev:server

Or run in standard mode

PORT=3132 bun run start:server


You'll see:```text
╔═══════════════════════════════════════╗
║      OmniChat Harness v0.1.0          ║
║  Dual OpenAI & Anthropic AI Gateway   ║
╚═══════════════════════════════════════╝

✓ OmniChat Harness running at http://localhost:3132

  Point your AI agents at:
    OpenAI / Cursor / Aider:   OPENAI_BASE_URL=http://localhost:3132/v1
    Claude Code / Anthropic:   ANTHROPIC_BASE_URL=http://localhost:3132
    API Key (any format):      API_KEY=omni-local-dev-key

  Available endpoints:
    POST http://localhost:3132/v1/chat/completions (OpenAI Chat Completions)
    POST http://localhost:3132/v1/messages         (Anthropic Messages API)
    GET  http://localhost:3132/v1/models           (Model Discovery)
    GET  http://localhost:3132/health             (Health & Provider Status)

4. Optional: Terminal Dashboard

Launch the ANSI monitoring dashboard in another terminal window:```bash
OMNI_SERVER_URL=http://localhost:3132 bun run start:tui


---

## Connecting Your Agents & Tools

### OpenCode
In `opencode.json`:```json
{
  "provider": {
    "omnichat": {
      "name": "OmniChat",
      "npm": "@ai-sdk/openai-compatible",
      "options": {
        "apiKey": "omni-local-dev-key",
        "baseURL": "http://localhost:3132/v1"
      },
      "models": {
        "chatgpt": { "name": "chatgpt" }
      }
    }
  },
  "model": "omnichat/chatgpt"
}

Claude Code CLI / Anthropic SDK

OmniChat directly supports the Anthropic Messages wire protocol:```bash
export ANTHROPIC_BASE_URL="http://localhost:3132"
export ANTHROPIC_API_KEY="omni-local-dev-key"
``````typescript
import Anthropic from '@anthropic-ai/sdk';

const anthropic = new Anthropic({
baseURL: 'http://localhost:3132',
apiKey: 'omni-local-dev-key',
});

const message = await anthropic.messages.create({
model: 'claude-3-5-sonnet',
max_tokens: 1024,
messages: [{ role: 'user', content: 'Analyze this algorithm.' }],
});
console.log(message.content[0].text);


### Cursor & Cline
In Cursor or VS Code Cline settings:
- **Provider:** OpenAI / OpenAI-compatible
- **Base URL:** `http://localhost:3132/v1`
- **API Key:** `omni-local-dev-key`
- **Model ID:** `gpt-4o` or `omni-code`

### Aider```bash
aider --openai-api-base http://localhost:3132/v1 \
      --openai-api-key omni-local-dev-key \
      --model gpt-4o

Python OpenAI SDK & LangChain```python

from openai import OpenAI

client = OpenAI(
base_url="http://localhost:3132/v1",
api_key="omni-local-dev-key",
)

response = client.chat.completions.create(
model="gpt-4o",
messages=[{"role": "user", "content": "What is the capital of France?"}],
)
print(response.choices[0].message.content)


---

## API Reference

### 1. `POST /v1/chat/completions` (OpenAI Format)
- **Aliases:** `/chat/completions`, `/api/v1/chat/completions`
- **Headers:** `Authorization: Bearer `, `Content-Type: application/json`
- **Body:** Standard OpenAI chat completions payload (`model`, `messages`, `tools`, `stream`).

### 2. `POST /v1/messages` (Anthropic Format)
- **Aliases:** `/messages`, `/api/v1/messages`, `/v1/v1/messages`
- **Headers:** `x-api-key: ` or `Authorization: Bearer `, `anthropic-version: 2023-06-01`
- **Body:** Standard Anthropic payload (`model`, `messages`, `system`, `tools`, `stream`).

### 3. `GET /v1/models`
- **Aliases:** `/models`, `/api/v1/models`
- Returns OpenAI-standard `{"object": "list", "data": [...]}` containing all registered models and routing metadata.

### 4. `GET /health`
- Returns detailed status for browser pool contexts, uptime, and provider readiness.

---

## Testing & Verification

OmniChat includes a comprehensive test suite across monorepo packages, as well as end-to-end agentic verification scripts:```bash
# Run unit and integration tests (62 tests across 9 files)
bun test

# Run monorepo typechecks across all 8 packages
bun x turbo typecheck

# Run automated system self-test (Health, Completions, SSE, Tool Calls, Multi-Turn)
PORT=3132 bun run scripts/system-self-test.ts

# Run autonomous coding agent loop with real developer tools
PORT=3132 bun run scripts/autonomous-coding-agent.ts "Implement an LRU cache module with unit tests"

Monorepo Architecture```

omnichat-harness/
├── apps/
│ ├── server/ # Hono gateway exposing OpenAI + Anthropic endpoints
│ └── tui/ # Terminal dashboard (ANSI, zero external UI dependencies)
├── packages/
│ ├── core/ # Orchestrator, TaskRouter, schema compaction & types
│ ├── openai-adapter/ # Wire format conversions, SSEEmitter, ToolCallParser, ModelRegistry
│ ├── providers/ # Headless browser adapters (ChatGPT, Claude, Gemini, Perplexity)
│ ├── browser/ # Playwright pool, stealth launch flags, AES-256-GCM vault
│ ├── queue/ # Background request queueing (BullMQ integration)
│ └── db/ # Drizzle ORM + SQLite database layer
├── scripts/
│ ├── system-self-test.ts # Automated 5-stage health & completion test
│ ├── autonomous-coding-agent.ts # Real multi-turn autonomous coding loop
│ └── session-init.ts # Interactive login wizard for browser sessions
└── test-agent-workspace/ # Isolated workspace for agent tests and generated modules
```


Security & Ethics

  • Encrypted Local Storage: Browser cookies and storage states are encrypted at rest using AES-256-GCM under data/sessions/. Never commit .env or data/ directories.
  • Audit-Safe Logging: No tokens, decrypted session states, or sensitive cookies are ever logged.
  • Terms of Service: This project drives browser automation for local development, research, and testing. Review and comply with the respective Terms of Service for each web service you interact with.

License

MIT © 2026 OmniChat Contributors

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
OmniChat Harness 怎么安装?

在客户端按下面的安装命令接入:# Start server immediately using bunx or npx bunx omnichat start --port 3132 # Or launch the terminal monitoring dashboard bunx omnichat tui。装完在客户端配置里引用同一个包或端点。

OmniChat Harness 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

OmniChat Harness 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

OmniChat Harness 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

OmniChat Harness 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Cline、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

OmniChat Harness 能提供哪些能力?

资料显示能力标签包括 开发。具体工具清单以官方文档为准。

OmniChat Harness 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

OmniChat Harness 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。