Skip to main content

Troubleshooting

Setup problems specific to one client live in that client's recipe — Claude Desktop's log locations, a Windows npx spawn quirk, and the like are called out inline in Connect Claude Desktop, Connect Claude Code, and Connect a custom client, right where you'd hit them.

This page is for the other kind: "I thought I was connected, but something's still off." These issues aren't tied to one client's install flow — they show up across clients, often after everything looked fine.

For raw HTTP statuses and JSON-RPC error codes (401, -32602, and friends), see Errors; that page owns the full error model.

Your client falls back to SSE, or you get a 405 / 307 on connect​

Symptoms vary by client — mcp-remote logs SSE error: Non-200 status code (405), SDK clients see a 307 or lose the connection right after the first call, curl just prints a redirect — but the cause is one thing: a trailing slash on the endpoint. The gateway 307-redirects …/mcp/ to a URL most clients can't follow, so they never complete the handshake.

Fix: connect to https://mcp.edited.com/mcp with no trailing slash. The full mechanism is in Concepts → Transports. Some clients also need a client-specific flag — e.g. mcp-remote wants --transport http-only — which is covered in that client's recipe.

Claude via the Anthropic API can't connect​

Anthropic's hosted MCP connector (the mcp_servers parameter on the Messages API) only forwards a bearer token via authorization_token, so it can't send the x-api-key header EDITED MCP requires — the connection will fail no matter how the key is set.

Fix: connect with the official MCP SDK client yourself and hand the resulting tools to the model with Anthropic's client-side MCP helpers. The custom-client recipe has TypeScript and Python examples; the ready-made app integrations in Connect Claude Code and Connect Claude Desktop are another route. See Authentication & access for the key itself.

Server-defined prompts don't do anything on their own​

EDITED's server-defined prompts (like mdmcp-market_data_query_guide) are offered to the client, but they aren't injected into your conversation automatically — so a fresh connection that "has" them can still behave as if they aren't there. Invoke them explicitly (in Claude Desktop, from the prompt/command picker) or fetch them with prompts/get. See How to query → Using the server-defined prompts.

Google Agent Development Kit (ADK): value2 schema validation error​

Connecting through Google's ADK, if every tool call fails — often on your first message — with an error like:

400 INVALID_ARGUMENT — Unable to submit request because
`ed_mdmcp-market_data_table` functionDeclaration `parameters.filters.value2`
schema didn't specify the schema type field

this is a known bug in the Gemini schema validation (google-genai), not an issue with EDITED's surface — the schemas EDITED serves are valid JSON Schema. ADK forwards every tool declaration to Google up front, and it's that validation, not ADK, that rejects the batch — so one declaration it won't accept blocks all your calls (which is why even a plain "hi" can fail naming a parameter).

Upstream tracked this at google/adk-python#3424, closed in December 2025 as a google-genai issue rather than an ADK one — so there's no ADK fix to wait for and no workaround in the thread. The one datapoint that holds: the reporter saw it disappear on ADK v1.17.0 with google-genai pinned to 1.44.0. Which backend and version combination breaks isn't settled upstream, so if this is blocking you, email support@edited.com and we'll dig in with you. (As of August 2026.)

Getting help​

If you hit a cross-client issue that isn't listed here, email support@edited.com with the client you're using, the full error message, and the tool name and arguments you called.