mcp-chatgpt-bridge
MCP server that lets Claude Code consult ChatGPT for a second opinion mid-task, with explicit context passed by the caller.
README
mcp-chatgpt-bridge
MCP server that lets Claude Code consult ChatGPT (OpenAI) for a second opinion mid-task, with explicit context passed by the caller.
What it does
When Claude Code is stuck on a design decision, needs a cross-check, or wants an independent opinion, it can call the ask_chatgpt tool to consult OpenAI's ChatGPT. ChatGPT sees only the context you provide — it has no access to your repo, files, or conversation history.
Every consultation is automatically pushed to Telegram/Slack (if configured) so you can review the advice independently later.
Quickstart
See Deployment Guide for full setup instructions.
TL;DR:
npm install && npm run build
export OPENAI_API_KEY=sk-...
claude mcp add chatgpt-bridge -- node /Users/hieuho/Desktop/mcp/dist/index.js
The ask_chatgpt tool
ask_chatgpt({
question: string, // The specific question to ask
context: string, // Self-contained background ChatGPT needs
model?: string // Optional model override (defaults to "gpt-5")
})
ChatGPT responds in Vietnamese with three sections: Câu hỏi (question recap), Khuyến nghị (recommendation), Giải thích (reasoning).
Architecture
Claude Code calls the ask_chatgpt MCP tool via stdio. The server forwards to OpenAI's API (or OpenRouter if you use an sk-or- key). The answer is returned to Claude Code and simultaneously pushed to Telegram/Slack as a side-channel for offline review.
A global Claude Code hook enforces auto-consult: Claude cannot end a turn with a question until it has called this tool first.
See System Architecture for a detailed diagram.
Project Status
- Maturity: Demo / personal use (0.1.0)
- Test suite: None yet
- CI/CD: None yet
- Known gap: No rate-limit or cost-cap enforcement on
ask_chatgptcalls
See Project Roadmap for details.
Documentation
- Project Overview & PDR — Purpose, scope, non-goals
- Codebase Summary — File-by-file breakdown and data flow
- Code Standards — Conventions observed in this codebase
- System Architecture — Architecture diagram and component details
- Deployment Guide — Setup, registration, environment variables
- Project Roadmap — Current state and open items
License
See LICENSE file if present.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.