Updated
Connect your AI through MCP
To share the same context between several AIs, connect them all to the same md-doc MCP server with an MCP-type API key. What one writes, any other can read.
Connection details
| URL | https://app.md-doc.com/api/mcp |
| Transport | MCP over HTTP (Streamable HTTP), stateless |
| Authentication | MCP-type API key (mcp_…), created in Settings → API keys |
The key can be sent in any of these ways:
Authorization: Bearer mcp_…header (recommended).x-api-key: mcp_…header.- In the URL, as
?key=mcp_…, for clients that cannot set headers.
A key in the URL can end up in logs of intermediate servers or proxies. md-doc strips it from its own access logs, but use a header whenever the client allows it. If you suspect it leaked, revoke the key in Settings and create another.
Guides by client
Any other client that supports MCP servers over HTTP should work with the details in the table. If you try another one, let us know.
If you’ll use several at once, the guide Connect multiple AI assistants covers how to split the work and which rules to follow.
What each AI sees
Every request is authenticated with your key and only sees your data. The MCP key gives no access to environment values or to your passwords. The available tools cover notes, logs, issues, records, references, files and shared folders.
Frequently asked questions
How do I share the same context between Claude and ChatGPT?
Connect both to the same md-doc MCP server (https://app.md-doc.com/api/mcp) with an MCP-type API key. Notes, logs and issues are the same for both.
What transport does the md-doc MCP use?
MCP over HTTP (Streamable HTTP), stateless: every request is authenticated with your API key and only sees your data.