codexpro-bridge
A companion MCP server that exposes live Hermes Skills, filtered native MCP tools, and conditional Memos recall to ChatGPT while isolating Bridge failures from CodexPro VPS operations.
README
CodexPro Bridge
CodexPro Bridge is a small companion MCP server for a deployment that already has both CodexPro and Hermes. CodexPro keeps ownership of files, Bash, Git, and VPS changes. This Bridge exposes live Hermes Skills, filtered Hermes Native MCP tools, conditional Memos recall, and a health check to ChatGPT.
It is intentionally a separate MCP connection. Keeping it separate avoids turning CodexPro into a permanent fork and lets a Hermes integration failure stay isolated from VPS operations.
Capabilities
- Live Skill discovery and real SKILL.md loading through Hermes public Skill APIs.
- Read-only loading of allowed Skill resources below references, templates, scripts, and assets.
- Listing and one-at-a-time dispatch of enabled Hermes Native MCP tools after Hermes include and exclude filtering.
- Conditional Memos recall for explicit history, preference, or second-brain questions.
- A fixed eight-tool MCP surface with redacted, bounded results.
- A two-connection Plugin template that routes work to CodexPro or Bridge.
The Bridge does not provide file editing, shell access, Docker, systemd, or root operations. Those belong to the separate CodexPro connection.
Requirements
- Python 3.12 or newer.
- A locally installed Hermes runtime whose Skill and Native MCP APIs are compatible with this package.
- A separately configured CodexPro MCP connection for VPS operations.
- An authenticated HTTPS reverse proxy or tunnel if the endpoint will be used outside the host. The server itself binds to loopback only.
Quick Start
Create a virtual environment and install the package:
python3.12 -m venv .venv
.venv/bin/python -m pip install --upgrade pip
.venv/bin/python -m pip install -e '.[dev]'
Copy .env.example to a protected environment file outside the repository, set a dedicated random value for CODEXPRO_BRIDGE_HTTP_TOKEN, and adapt the Hermes paths. Load that file in the service manager, then start the server:
set -a
. /etc/codexpro-bridge.env
set +a
.venv/bin/codexpro-bridge
The default endpoint is http://127.0.0.1:18787/mcp. It accepts either an Authorization header using the Bearer scheme or the codexpro_token query parameter. Do not place a real authenticated URL in Git, screenshots, tickets, or logs.
Run the offline suite before deploying:
.venv/bin/python -m pytest -q
The example systemd unit in examples/codexpro-bridge.service is a starting point only. Adapt its user, paths, and read-only access to your own Hermes installation. Use any reverse proxy or tunnel you already operate; this repository deliberately does not manage a DNS zone or Cloudflare account.
ChatGPT Plugin
The bundled Plugin joins two pre-registered MCP connections: one CodexPro connection and one Bridge connection. Render the local-only app manifest with opaque connection IDs supplied by ChatGPT, then install the Plugin directory:
python scripts/render_plugin_app_manifest.py \
--codexpro-connection-id '<codexpro-connection-id>' \
--bridge-connection-id '<bridge-connection-id>'
The generated plugin/codexpro-bridge/.app.json is ignored by Git. The routing Skill tells ChatGPT to use Bridge for Hermes capabilities and CodexPro for VPS operations. See docs/plugin.md for the exact boundary.
Important Limits
This project calls Hermes integration APIs that are not a stable public Python SDK. Test a Hermes upgrade in staging and restart Bridge after MCP connection configuration changes. Bridge creates its own Hermes MCP connections; it does not share the Hermes Agent process's already-open sessions.
The generic Hermes MCP call tool can reach tools with side effects. The deployment's Hermes configuration remains the authority for which upstream tools are visible and callable. Require explicit confirmation in the calling product for mutating operations.
Documentation
- docs/architecture.md - ownership and data flow.
- docs/configuration.md - environment variables and deployment boundary.
- docs/capability-contract.md - fixed public MCP tools.
- docs/plugin.md - two-connection Plugin installation.
- docs/development.md - tests and local development.
- docs/security.md - redaction and secret boundaries.
- docs/known-limitations.md - current operational limits.
License And Affiliation
MIT licensed. This is an independent community project and is not affiliated with or endorsed by OpenAI, CodexPro, Hermes, Memos, or Cloudflare. It includes no credentials, private deployment configuration, or third-party runtime code.
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。