Checked: 2026-09-03
Connect your own MCP server
Client support, account requirements, transport choices, and official sources for connecting developer-owned MCP servers.
These requirements change frequently. Recheck the linked official documentation and the actual account UI before paying, deploying, or changing authentication.
supported-with-plan
ChatGPT
Recommended: Deploy a private HTTPS MCP with OAuth. Use Secure MCP Tunnel when the server must remain on a private network.
Account and cost: Pro supports custom read/fetch MCP connections. Full MCP, including write actions, requires Business, Enterprise, or Edu and workspace administration.
Transport: Streamable HTTP, Secure MCP Tunnel
Limitations: Do not rely on Plus for an individually developed MCP: the dedicated Developer Mode requirements do not clearly list it. Custom apps are added on the web; Agent mode does not use them.
Official sources:
supported
Qwen Code
Recommended: Use stdio for a local server or Streamable HTTP for a hosted server, configured with qwen mcp add or settings.json.
Account and cost: MCP itself needs no premium client tier. Model access still requires a Coding Plan or API provider; the free Qwen OAuth tier ended on April 15, 2026.
Transport: stdio, Streamable HTTP, SSE
Limitations: The consumer qwen.ai web chat does not document the same arbitrary MCP URL flow as Qwen Code.
Official sources:
not-documented
Doubao chat
Recommended: Use TRAE for a developer client, or Coze and Volcengine products for a hosted agent using Doubao models.
Account and cost: No general account path for adding an arbitrary self-hosted MCP URL is currently documented.
Transport: No arbitrary custom transport documented
Limitations: Built-in or partner MCP availability in a product does not prove that arbitrary custom servers can be added.
supported
TRAE
Recommended: Use TRAE instead of the consumer Doubao chat app when manually connecting a developer-owned MCP server.
Account and cost: MCP servers can be selected from the marketplace or added manually. Model quota, region, and client availability remain separate conditions.
Transport: stdio, remote MCP
Limitations: Recheck the current client UI and quota before setup because product availability can change.
Official sources:
supported
Coze
Recommended: Provide an HTTPS hostname, choose no auth, service token/API key, or OAuth, then test and publish the plugin before using it in an agent or workflow.
Account and cost: Creating an MCP-based plugin is free; hosting, model, and third-party service usage can still cost money. Private-network connections are an enterprise-tier feature.
Transport: HTTPS MCP
Limitations: A bare IP address is not accepted as the plugin URL. Workspace administrators can restrict feature and resource visibility.
Official sources:
supported-with-plan
Claude
Recommended: Use a desktop extension for local access or add a remote connector URL in Settings > Connectors.
Account and cost: Local desktop extensions are available to free Claude Desktop users. Remote custom connectors require Pro, Max, Team, or Enterprise.
Transport: desktop extension, Streamable HTTP, SSE
Limitations: On Team and Enterprise, an Owner or Primary Owner must first add the organization connector.
Official sources:
limited-preview
Gemini Spark
Recommended: Add the MCP URL from Gemini web Connected Apps, then use the connection in Spark on web or mobile.
Account and cost: Requires Gemini Spark access, age 18 or over, a personal Google Account, Keep Activity enabled, and current eligibility in the United States.
Transport: remote MCP
Limitations: Currently English-only and not a general connection path for accounts in Japan, or for work and school accounts.
Official sources:
Two deployment patterns
- stdio: The desktop client starts the server locally. No public hostname is needed, but a phone cannot connect directly.
- Streamable HTTP: A cloud client connects to a stable HTTPS endpoint. Keep it private and authenticated.