Why does Claude Desktop need the mcp-remote bridge?
1 min
Claude Desktop's JSON config supports stdio-transport servers only. mcp-remote is a tiny shim that adapts HTTP into stdio.
Claude Desktop's `claude_desktop_config.json` file was designed before remote HTTP MCP servers were common, and its parser only accepts the stdio shape (`{command, args, env}`). Cursor and VS Code both accept the direct HTTP form (`{url, headers}`). To get Avery into Claude Desktop, the snippet uses the community `mcp-remote` package — a ~40 KB shim that Claude Desktop spawns as a stdio child process; the shim itself opens an HTTP connection to Avery and forwards every MCP frame transparently. From Avery's perspective the connection looks exactly like Cursor / VS Code — bearer-authenticated HTTP. From Claude Desktop's perspective it's a normal stdio MCP server. Alternative: use Claude Desktop's in-app Settings → Connectors → Add custom connector UI, which DOES support direct HTTP. The JSON file vs. in-app paths are two independent ways to add the same server.
Live recipes need the desktop
This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.