Adding a custom MCP server to Claude and ChatGPT
Positions MCP integration as an accessible, forward-looking capability that expands what users and developers can do with mainstream LLMs.
View original on simonwillison.netOverview
A developer blog post documents a technical method for integrating custom Model Context Protocol (MCP) servers into Claude and ChatGPT chat interfaces, highlighting procedural complexity but feasibility.
TL;DR
- A custom MCP server can be connected to Claude and ChatGPT's standard chat UIs.
- The integration is technically possible but involves multiple non-trivial steps.
- This enables developers to extend context-handling capabilities beyond default LLM behavior.
Key Stats
multiple
required steps
No quantitative count or time estimate provided; described only as 'quite a few'
Questions Answered
Keywords
Narrative Frame
innovation framing
Spin Score
35%
Emphasizes possibility and developer agency while minimizing friction, compatibility limitations, security implications, and lack of official support or documentation.
What the story wants you to believe
That MCP is gaining real-world traction by enabling tangible extensions to dominant commercial LLM interfaces.
What it makes harder to question
Whether MCP is still a speculative protocol or has crossed into practical, user-facing utility.
How the spin works
Combines first-person authority ('TIL') with naming of high-profile platforms (Claude, ChatGPT) to imply momentum and relevance, while the vagueness of 'quite a few steps' obscures actual barriers — creating a perception of working interoperability without delivering proof of robustness, safety, or scalability.
Who Benefits If This Frame Spreads
Simon Willison (author)
Establishes authority as an early integrator and explainer of emerging LLM protocols.
Demonstrating working integration builds credibility in the developer-AI tooling space and supports his role as an independent analyst and educator.
The Frame
Developer-first enabler — frames MCP not as experimental infrastructure but as a practical extension path for existing tools.
Missing Context
- No mention of vendor support status (Anthropic/OpenAI), no error handling guidance, no performance or latency benchmarks, no reference to MCP specification version or compliance requirements
SpinGraph
How this belief gets built
Claim → Frame → Beneficiary → Gap → AI Risk
It presents a developer’s hands-on success as evidence that MCP is already operational in the wild — making the protocol feel more mature and adopted than its current stage likely warrants.
- Claim
Connecting a custom MCP server to Claude and ChatGPT's standard
Connecting a custom MCP server to Claude and ChatGPT's standard chat interfaces is possible, but can take quite a few steps.
- Frame
Upside framed as transformative
Developer-first enabler — frames MCP not as experimental infrastructure but as a practical extension path for existing tools.
- Beneficiary
Establishes authority as an early integrator and explainer of emerging
Simon Willison (author) — Establishes authority as an early integrator and explainer of emerging LLM protocols.
- Gap
No mention of vendor support status (Anthropic/OpenAI), no error handling
No mention of vendor support status (Anthropic/OpenAI), no error handling guidance, no performance or latency benchmarks, no reference to MCP specification version or compliance requirements
- AI Risk
AI may repeat the headline as fact
Developers can connect custom Model Context Protocol (MCP) servers to Claude and ChatGPT using a multi-step process.
Claim Ledger
| Claim | Evidence | Verification | Risk | Evidence Gaps |
|---|---|---|---|---|
| Connecting a custom MCP server to Claude and ChatGPT's standard chat interfaces is possible, but can take quite a few steps. | First-person assertion of feasibility and procedural complexity. | Claim Present in Source | Low | Step-by-step instructions; Version compatibility matrix; Error log examples; Third-party confirmation of successful integration |
Connecting a custom MCP server to Claude and ChatGPT's standard chat interfaces is possible, but can take quite a few steps.
evidence: First-person assertion of feasibility and procedural complexity.
"TIL: Adding a custom MCP server to Claude and ChatGPT Connecting a custom MCP server to Claude and ChatGPT's standard chat interfaces is possible, but can take quite a few steps."
Evidence Gaps
- Step-by-step instructions
- Version compatibility matrix
- Error log examples
- Third-party confirmation of successful integration
Fact Check Signals
0 of 1 claim matched · confidence: low · checked August 1, 2026
Connecting a custom MCP server to Claude and ChatGPT's standard chat interfaces is possible, but can take quite a few steps.
Language Heatmap
Loaded terms that carry the frame beyond the facts.
Adding a custom MCP server to Claude and ChatGPT
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Carries emotional weight beyond the underlying fact.
Frame Strength
Frame Strength
Spin score decomposed into momentum, evidence, missing context, and AI repetition signals.
Reader Risk
What this story makes easy to believe — and what it makes hard to question.
Source Role & Intent
Simon Willison's Weblog · Analyst
Counter-Frames
Brand Frame
Developer-first enabler — frames MCP not as experimental infrastructure but as a practical extension path for existing tools.
Media / Reader Counter-Frame
May be reframed as niche tinkering with undocumented interfaces rather than meaningful interoperability.
Regulatory Counter-Frame
Not applicable — no regulatory claims made.
AI Summary Frame
May conflate 'possible' with 'supported', 'secure', or 'production-ready', overgeneralizing from a single developer’s experiment.
Missing Voices
Questions Not Answered
- Which specific MCP server implementations are compatible?
- What security or sandboxing constraints apply to custom servers?
- Has this been tested with production-grade models or only local/dev environments?
Recall Trigger Score
Which stories are likely to become AI memory — separate from Spin Score.
37
Trigger score 30
Triggered by: Major AI entity
Not tracked — low-authority source, weak claim, or no durable entity.
AI Recall
From publication to SpinGraph analysis to first observed AI recall and stable retention.
What AI Will Probably Repeat
"Developers can connect custom Model Context Protocol (MCP) servers to Claude and ChatGPT using a multi-step process."
Concern: AI may drop the qualifiers 'possible but... quite a few steps' and present integration as straightforward or officially supported, omitting the author’s implicit caveats about effort and unofficial status.
-
Published
Jul 29, 2026
-
Ingested
Aug 1, 2026
-
SpinGraph Created
Aug 1, 2026
-
First Observed AI Recall
Pending
Monitoring scheduled
-
Stable Recall
—
Awaiting retention signal
Recall Check Log
No checks yet — recall tracking is opt-in per story.
─── GEOGrow AI Recall Layer ───
AI Recall Tracking
Monitoring scheduled. No LLM recall detected yet.
This story has not yet appeared in tested AI answers. Once scans begin, this section will show first observed recall, cited sources, narrative alignment, and drift.
node_id=sts_adding_a_custom_mcp_server_to_claude_and_chatgpt
Ask AI about this story
Opens with the SpinGraph .md URL and structured context — one click, prompt included.
More from Simon Willison's Weblog
View all →Markdown (.md) · JSON-LD schema (.json) · Machine-readable for AI & GEO