Smithery Shutdown: Official MCP URLs to Switch To (2026)

Smithery shut down its hosted MCP connections on October 31, 2026. Any server URL on server.smithery.ai or run.tools has stopped working. To fix it, replace each Smithery URL with the vendor's official MCP endpoint. The table below lists 20 of them, each tested on November 8, 2026.

Smithery was acquired by Arcade.dev on August 5, 2026. Its co-founder posted the shutdown notice on smithery.ai/future: smithery.ai stays online as a public directory, but it no longer proxies connections. If your Claude Code, Cursor or Claude Desktop setup still points at a Smithery URL, those tools have been failing since November 1.

What stopped working on October 31

According to Smithery's own notice, these ended on October 31, 2026:

Paid subscribers are being refunded for every charge since August 5, and subscriptions are cancelled.

What still works

• smithery.ai as a directory. You can still browse servers there. It is now "powered by Arcade.dev".
• Direct URLs on verified servers. For a curated set, registry pages now show the vendor's direct URL (Smithery's example: mcp.linear.app/mcp instead of linear.run.tools or server.smithery.ai/linear).
• Anything you run locally. Servers you started with npx, uvx or Docker never went through Smithery and are unaffected.

Official remote MCP URLs for 20 popular servers

We sent a standard MCP initialize request to each endpoint on November 8, 2026. A 401 means the server is online and wants you to sign in (OAuth or an API key), which is the normal response for services that act on your account. A 200 means it accepted an unauthenticated session.

Two services are left out on purpose. Zapier issues each user a personal MCP URL from its dashboard, and Firecrawl puts your API key in the URL path. For both, copy the URL from your own account rather than from a list.

Endpoints change. Before you paste one into a production config, check the vendor's documentation; the directory pages above link to each project's repository.

How to update your config

The fix is the same everywhere: delete the Smithery entry and add the official URL. Here is what that looks like in the three most common clients, using Linear as the example.

Claude Code

Remove the old server and add the new one over HTTP:

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

Then run /mcp inside Claude Code to sign in. Servers that return 401 will open a browser for OAuth.

Cursor

Edit ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

// Before: dead since October 31
{ "mcpServers": { "linear": { "url": "https://server.smithery.ai/linear/mcp?api_key=..." } } }

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

Delete the Smithery api_key from the file at the same time; it no longer does anything.

Claude Desktop

On a plan with custom connectors, open Settings → Connectors → Add custom connector and paste the official URL. Otherwise, bridge the remote server through mcp-remote in claude_desktop_config.json:

{
  "mcpServers": {
    "linear": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.linear.app/mcp"] }
  }
}

Restart Claude Desktop after editing the file.

What if the vendor has no hosted endpoint?

Many community servers were only ever reachable through Smithery's proxy. For those, run the server yourself:

1. Find it in the MCP server directory and open its GitHub repository.
2. Follow the README's local install, usually npx -y <package> or uvx <package>, and add it to your client as a stdio server.
3. Put any API keys in environment variables, not in the URL.

Local stdio servers run on your machine, so they also keep working if any hosting company changes its plans again.

When an official URL is not the answer

• You served MCP to your own users through Smithery Connect. Swapping URLs in a config file does not replace a connection broker. You need another hosted gateway or your own OAuth handling. Smithery's notice points to Arcade for this, and its co-founder offers to help pick a replacement "even if it isn't Arcade".
• The vendor's endpoint does less than the community server you used. Official servers often expose a narrower tool set. Compare the tool list before you migrate a workflow that depends on a specific tool.
• You need it to work offline or inside a locked-down network. Use a local stdio server instead of any remote URL.

FAQ

Is Smithery shutting down completely?

No. smithery.ai remains a public directory of MCP servers, now run by Arcade.dev. What ended on October 31, 2026 is the connection layer: hosted server URLs, the API, accounts, API keys, the CLI and the SDKs.

Why do my MCP tools fail with a connection error since November 1?

Your config most likely still points at a server.smithery.ai or run.tools URL. Those stopped responding on October 31. Replace them with the vendor's official URL from the table above.

What does a 401 from an official MCP URL mean?

It means the server is online and needs you to authenticate. Clients like Claude Code and Cursor handle this by opening an OAuth sign-in in your browser. Services that act on your data (Linear, Notion, GitHub, Stripe) all require it.

Where can I find MCP servers now that Smithery's hosting is gone?

Directories still list them; you just connect directly. mcpinstall.com indexes more than 23,000 MCP servers with links to each repository, and our guide on how to use MCP covers adding a server to your client.

Sources: Smithery shutdown notice, Arcade: Smithery Is Now Part of Arcade.dev (August 5, 2026). Endpoint tests run by mcpinstall on November 8, 2026.