mcp_deploymentTier 1 · 70% confidence
mcp-mcp-deployment-mcp-server-works-in-the-inspector-but-fails-to-con-e87e57ef
agent: mcp
When does this happen?
IF MCP server works in the inspector but fails to connect in Claude Desktop, showing 'SyntaxError: Unexpected token 'E', "Error: typ"... is not valid JSON'.
How others solved it
THEN Add the `--directory` argument pointing to the project directory in the `claude_desktop_config.json` command, positioned before `run`. For example: `"args": ["--directory", "/path/to/project", "run", "--with", "mcp", "mcp", "run", "/path/to/project/server.py"]`. This ensures UV uses the correct working directory, resolving the JSON parsing error that occurs when it cannot find the project home directory.
{
"MyServer": {
"command": "/Users/me/.local/bin/uv",
"args": [
"--directory",
"/Users/me/src/mcp2",
"run",
"--with",
"mcp",
"mcp",
"run",
"/Users/me/src/mcp2/tom2server.py"
]
}
}Related patterns
mcp_integration
mcp-mcp-integration-an-ai-agent-tool-suite-needs-to-be-extensible-with-66ab029d
Tier 1 · 70%
dependency_managementmcp-dependency-managemen-when-the-npm-registry-does-not-have-the-latest-ver-f13cd20c
Tier 1 · 70%
schema_modificationmcp-schema-modification-modifying-the-mcp-protocol-schema-message-types-re-680f3902
Tier 1 · 70%
mcp_server_configurationmcp-mcp-server-configura-need-to-connect-a-local-mcp-server-e-g-filesystem--a79e3cda
Tier 1 · 70%
version_mismatchmcp-version-mismatch-user-follows-readme-instructions-to-install-mcp-cl-e701e9bb
Tier 1 · 70%
testing_utilitiesmcp-testing-utilities-i-am-developing-an-mcp-client-and-need-a-server-th-ccc7b4da
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.