Client compatibility
MCP client compatibility
Drop-in configuration snippets for the popular MCP clients. The endpoint is the public demo store; replace with your own slug for production.
Claude Desktop
- Transport
- MCP Streamable HTTP
- Authentication
- OAuth 2.1 web flow on first call (Discovery via /.well-known/oauth-protected-resource).
Configuration — claude_desktop_config.json
{
"mcpServers": {
"trusteed": {
"url": "https://trusteed.xyz/demo-store/mcp",
"transport": "streamable-http"
}
}
}Claude.ai (Custom Connectors)
- Transport
- MCP Streamable HTTP
- Authentication
- Browser OAuth flow within Claude.ai when connector is added.
Configuration — Settings → Connectors → Add Custom Connector
URL: https://trusteed.xyz/demo-store/mcp
Name: Trusteed
(OAuth handled in-browser by Claude.ai)ChatGPT / GPT Builder
- Transport
- OpenAPI Action
- Authentication
- API key (header X-Agent-Api-Key) — ChatGPT does NOT yet implement MCP transport.
Limitations
MCP transport is not supported in ChatGPT custom GPTs. Use the REST API via OpenAPI Action; the chatgpt-app PostMessage build runs at agenticmcpstores-production.up.railway.app and is for ChatGPT Apps SDK only, not Claude.ai.
Configuration — GPT Builder → Actions → Import OpenAPI
OpenAPI URL: https://api.trusteed.xyz/api/v1/openapi.json
Auth: API key, custom header "X-Agent-Api-Key"Cursor
- Transport
- MCP Streamable HTTP
- Authentication
- OAuth 2.1 launched from Cursor on first tool call.
Configuration — ~/.cursor/mcp.json
{
"mcpServers": {
"trusteed": {
"url": "https://trusteed.xyz/demo-store/mcp",
"type": "http"
}
}
}Continue.dev
- Transport
- MCP Streamable HTTP
- Authentication
- OAuth 2.1 (web flow on first call).
Configuration — ~/.continue/config.json
{
"experimental": {
"modelContextProtocolServers": [
{
"transport": { "type": "streamable-http", "url": "https://trusteed.xyz/demo-store/mcp" }
}
]
}
}