Smithery's MCP proxy shuts down on 31 October: how to move each server to its official URL

Smithery shuts down its MCP proxy and managed identity on 31 October 2026. After that date, server URLs on run.tools and server.smithery.ai stop working, and so do Smithery accounts, API keys, Connect and Toolbox. If any MCP server in your setup came from Smithery, it needs a new URL before the end of the month. For most servers the fix is one line: point the client at the vendor's own endpoint.

What stops working on 31 October

The notice at smithery.ai/future is signed by cofounder Anirudh Kamath. Smithery is now part of Arcade. The list of what stops is short and specific:

• Server URLs on run.tools and server.smithery.ai.
• The Smithery API, Smithery Connect and Smithery Toolbox.
• Smithery accounts and API keys.
• The Smithery CLI and SDKs. The current versions are marked deprecated, and connecting through Smithery is no longer possible.

What stays is the directory. smithery.ai continues as a public, non-proxied MCP registry, now powered by Arcade.dev. Pages for verified servers show the vendor's direct URL instead of a Smithery one: mcp.linear.app/mcp in place of linear.run.tools or server.smithery.ai/linear. If a server you use is not in the list below, its Smithery page is the quickest place to find the official URL.

Paid plans are refunded for every charge since 5 August, and subscriptions are cancelled. Smithery says refunds usually arrive within 5 to 10 business days. Kamath offers help with migrations at ani [at] smithery [dot] ai.

Who is affected

• Individual developers. Anyone who added a server to Claude Desktop, Claude Code, Cursor, VS Code, Windsurf or Codex by copying a Smithery URL or a @smithery/cli command. Those tools disappear from your agent on 31 October.
• Teams with shared configs. A .mcp.json or .cursor/mcp.json committed to a repository breaks for every teammate at once. One fix in the repo covers everyone.
• Products built on Smithery. If you used Connect, the API or managed identity to run OAuth and tool calls for your own users, there is no one-line swap. Smithery's note says these setups need a replacement before 31 October.

How to find Smithery entries in your configs

Search your MCP config files for three strings: run.tools, server.smithery.ai and @smithery/cli. The first two appear in remote server URLs. The third appears in the args of servers installed through the Smithery CLI. On macOS or Linux, this checks the usual places in one pass:

grep -nE 'run\.tools|server\.smithery\.ai|@smithery/cli' \
  ~/.cursor/mcp.json .cursor/mcp.json \
  ~/.claude.json .mcp.json .vscode/mcp.json \
  ~/.codex/config.toml \
  "$HOME/Library/Application Support/Claude/claude_desktop_config.json" 2>/dev/null

Where each client keeps its config:

• Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows, under mcpServers.
• Claude Code: ~/.claude.json for your own servers, .mcp.json at the repository root for shared ones.
• Cursor: ~/.cursor/mcp.json globally, .cursor/mcp.json per project.
• VS Code: .vscode/mcp.json per workspace. The top-level key is servers, not mcpServers.
• Codex: ~/.codex/config.toml, one [mcp_servers.<name>] table per server.

Swapping one server: Linear as the example

A Smithery entry usually takes one of two shapes. The remote form points at a Smithery URL:

{
  "mcpServers": {
    "linear": {
      "url": "https://linear.run.tools"
    }
  }
}

The CLI form runs Smithery's package locally. The server name and flags vary, but @smithery/cli in args is the tell:

{
  "mcpServers": {
    "linear": {
      "command": "npx",
      "args": ["-y", "@smithery/cli@latest", "run", "<server>", "--key", "<smithery-key>"]
    }
  }
}

Replace either one with the vendor's endpoint. In Cursor:

{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/mcp"
    }
  }
}

In a shared Claude Code .mcp.json, add the transport type:

{
  "mcpServers": {
    "linear": {
      "type": "http",
      "url": "https://mcp.linear.app/mcp"
    }
  }
}

From the Claude Code command line, it is two commands:

claude mcp remove linear
claude mcp add --transport http linear https://mcp.linear.app/mcp

Claude Desktop is the exception. Remote servers are added in the app's settings as custom connectors, not in the JSON file. Delete the Smithery entry from claude_desktop_config.json, restart the app, and add the vendor URL as a connector.

Official endpoints for 12 common servers

Each endpoint below appears on the vendor's own documentation, checked on 21 October 2026. Most use Streamable HTTP and sign you in with OAuth the first time you connect.

• Linear: https://mcp.linear.app/mcp, or https://mcp.linear.app/mcp/readonly for read-only access. OAuth. Linear MCP docs.
• GitHub: https://api.githubcopilot.com/mcp/, with OAuth or a personal access token. For a local server, GitHub publishes the Docker image ghcr.io/github/github-mcp-server. The old @modelcontextprotocol/server-github package is deprecated on npm. GitHub MCP Server.
• Notion: https://mcp.notion.com/mcp, with https://mcp.notion.com/sse for clients that need SSE. OAuth. Notion MCP guide.
• Slack: https://mcp.slack.com/mcp. OAuth. Slack MCP server docs.
• Sentry: https://mcp.sentry.dev/mcp. OAuth. Add /<organization> or /<organization>/<project> to the URL to limit the session to one org or project. Sentry MCP.
• Stripe: https://mcp.stripe.com, with OAuth or an API key sent as a bearer token. Stripe MCP docs.
• Supabase: https://mcp.supabase.com/mcp, or http://localhost:54321/mcp against a local Supabase CLI stack. Supabase MCP guide.
• Context7: https://mcp.context7.com/mcp, with an API key, or https://mcp.context7.com/mcp/oauth for OAuth. npx ctx7 setup configures supported clients for you. Context7 client setup.
• Cloudflare: https://mcp.cloudflare.com/mcp covers the whole Cloudflare API and its developer docs. Product-specific servers sit at *.mcp.cloudflare.com/mcp, such as https://docs.mcp.cloudflare.com/mcp for documentation. Cloudflare's MCP servers.
• Neon: https://mcp.neon.tech/mcp, with OAuth or a Neon API key as a bearer token. Add ?readonly=true to block writes, or ?category= to limit which tools are active. Neon MCP Server docs.
• PostHog: https://mcp.posthog.com/mcp, or run npx @posthog/wizard mcp add to configure it. PostHog MCP docs.
• Brave Search: no hosted endpoint. Run npx -y @brave/brave-search-mcp-server locally with a BRAVE_API_KEY environment variable. Brave's own Claude Desktop guide still shows @modelcontextprotocol/server-brave-search, which is deprecated on npm. Brave Search MCP Server.

What to check after switching

Smithery sat in the middle, holding credentials and passing calls through. Going direct removes that layer, so four things are worth a look.

• Sign in again. OAuth sessions held by Smithery do not carry over. Each client asks you to authorise the vendor directly the first time it connects. In Claude Code, run /mcp to finish sign-in. Servers that take a key, such as Brave Search, need it in your config or environment.
• Tool names. A vendor's server may name tools differently from the Smithery-hosted version. If prompts, skills or subagent definitions call tools by name, check them against what the new server lists.
• Transport. Remote endpoints need a client that supports HTTP servers. For a stdio-only client, npx -y mcp-remote <url> bridges the gap, as Linear's docs show.
• Restart and confirm. Restart the editor or agent session after editing a config file, then confirm the server shows as connected and its tools are listed. In Claude Code, /mcp shows the status of every server.

What this says about MCP

Hosted proxies made sense when few vendors ran their own MCP servers. Now that Linear, GitHub, Notion, Slack, Stripe, Cloudflare and most of the servers above host official endpoints, a middle layer adds a dependency without adding much. The open question is managed identity: the job of handling OAuth for many users across many servers. Smithery has stepped out of it, and Arcade is one of the companies building for it. If your product depends on that layer, choosing its replacement is the decision to make this month.

Kapyn's MCP directory lists servers with their official endpoints. For the wider picture, see what MCP is and the best MCP servers for Claude.