opengpt-connect
MCP server bridging ChatGPT to local OpenHarness tools, enabling file reads/writes, grep, LSP, and shell execution on a workspace.
README
OpenGPT
ChatGPT Developer Mode drives local OpenHarness tools through a thin Python MCP bridge.
uv run opengpt-connect --root <abs-path> --mode read|write [--tunnel cloudflare|none]
Clone:
git clone --recurse-submodules <this-repo>
OpenHarness is the upstreams/openharness submodule (https://github.com/HKUDS/OpenHarness.git, pinned SHA). See AGENTS.md (wrap): OpenGPT adapters live in packages/chatgpt-mcp.
Paste the printed ChatGPT MCP URL into ChatGPT as a Server URL (Streamable HTTP, auth none).
--tunnel none is loopback/tests only. It does not print a ChatGPT URL.
v1 file tools are jailed to --root. bash is a host-equivalent shell (cwd pinned, host otherwise reachable). Do not treat the whole MCP as jailed. Workspace .env is readable in read mode unless later deny-listed.
Prefer fast_context for exploratory questions, then read_many and apply_changes (up to 20 files per call). Oversized grep / bash / glob / lsp / read_many / fast_context results are written to --root/.opengpt-spill/ and the model gets a head/tail preview plus that path.
v2 optimizes ChatGPT ↔ MCP round-trips, not Python function-call latency. Typical exploration: v1 used 3–6 tool turns; v2 uses 1 fast_context turn plus ChatGPT's semantic decision. Do not treat that as a fixed wall-clock speedup until measured in ChatGPT Web.
The router does not understand code semantically. It uses OpenHarness's local dry-run candidate scoring plus small deterministic intent rules. ChatGPT remains responsible for semantic decisions. fast_context is read-only. On a strong skill-name match it may prepend bundled/project skill text. Trust model: checked-in project skills are treated as trusted workspace instructions, not untrusted third-party content. Do not point --root at an untrusted repo if those skills should be ignored. Heuristic project memory is appended after repo evidence and must not override it. Direct write tools remain write-mode-only. isolated_change requires a clean git working tree and writes only inside the worktree (shared-dir symlinks such as .venv / node_modules are rejected as write targets).
ChatGPT
│
│ one MCP call
▼
fast_context
│
├─ OpenHarness dry-run candidate routing
│ no LLM
│
└─ deterministic recipe
│
├─ grep
├─ read_many
└─ optional LSP
Recommended tool use:
Exploring an unfamiliar code area: fast_context
Exact known search: grep
Exact known files: read_file / read_many
Applying known edits: apply_changes
Trial edits + verification: isolated_change
Running verification: verify_project
Ad-hoc / short shell: bash
Long test/build/dev server: long_task
Tools
Read mode: fast_context, read_file, glob, grep, lsp, read_many.
Write mode adds: write_file, edit_file, apply_changes, verify_project, isolated_change, long_task, bash.
route_preview is local-debug only (opengpt-connect --debug-tools). It is not in the production MCP catalog.
Not exposed: agent/plan/image/MCP-client tools, cron, task_create/local_agent, web, and other OpenHarness extras. verify_project / isolated_change / long_task reuse OpenHarness model-free runners.
How it works
You ──ask──► ChatGPT Developer Mode
│
│ Server URL (Streamable HTTP, auth none)
▼
┌──────────────────────────┐
│ Cloudflare quick tunnel │ default --tunnel cloudflare
│ *.trycloudflare.com │
└────────────┬─────────────┘
│ HTTPS
▼
┌──────────────────────────────────────────────┐
│ opengpt-connect (127.0.0.1:8787) │
│ │
│ /t/<16-byte-hex>/mcp POST GET DELETE │
│ /health │
│ │
│ Origin check → path token → sessions │
│ (100 max, 30 min idle) │
└────────────┬─────────────────────────────────┘
│ tools/call 1:1
▼
┌──────────────────────────────────────────────┐
│ ToolAdapter │
│ │
│ small allowlist │
│ OpenHarness: read/grep/glob/lsp/edit/bash │
│ + read_many / apply_changes │
│ + spill oversized output to .opengpt-spill │
│ │
│ path jail for file/glob/grep/edit │
│ SENSITIVE_PATH_PATTERNS extra deny │
│ bash: host-equivalent (cwd pin only) │
└────────────┬─────────────────────────────────┘
│ tool.execute(..., cwd=root)
▼
┌──────────────────────────────────────────────┐
│ OpenHarness tool classes (library) │
│ Not exposed: agent, cron, tasks, web, … │
└────────────┬─────────────────────────────────┘
│
▼
approved --root workspace
No inner LLM. The bridge does not read ANTHROPIC_API_KEY or OPENAI_API_KEY. ChatGPT is the only model.
--tunnel none skips Cloudflare and serves /mcp on loopback only.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。