cd /news/ai-agents/smithery-s-mcp-server-urls-stopped-w… · home › topics › ai-agents › article
[ARTICLE · art-170922] src=stork.ai ↗ pub= topic=ai-agents verified=true sentiment=↓ negative

Smithery's MCP Server URLs Stopped Working: How to Fix Your Config

Smithery will shut down its connection management services on October 31, 2026, disabling server URLs on run.tools and server.smithery.ai, the Smithery API, Connect, Toolbox, accounts and API keys, and deprecating its CLI and SDKs, according to the company's notice at smithery.ai/future. Smithery said smithery.ai will remain as a public directory of MCP servers, now powered by Arcade.dev, and that paid customers will be refunded every charge since August 5. Developers must replace affected entries in configs such as Cursor's ~/.cursor/mcp.json and Claude Desktop's claude_desktop_config.json with vendors' own MCP endpoints, including https://mcp.linear.app/mcp, https://mcp.notion.com/mcp and https://mcp.stripe.com.

read5 min views5 publishedNov 16, 2026
Smithery's MCP Server URLs Stopped Working: How to Fix Your Config
Image: Stork (auto-discovered)

What stopped, in Smithery's words# #

Smithery's notice reads: "On October 31, 2026, we're shutting down Smithery's connection management services." It lists what stops working:

  • "Server URLs on run.tools and server.smithery.ai"
  • "Smithery API, Connect, and Toolbox"
  • "Smithery accounts and API keys"
  • "The Smithery CLI and SDKs. We'll mark the current versions as deprecated."

What stays: smithery.ai itself, "as a public directory of MCP servers, now powered by Arcade.dev". The notice also says paid customers are refunded "every charge since August 5". So the directory is still there. The part that carried your traffic is not.

[Make one free](https://www.stork.ai/tools/talking-photo?utm_source=house_ad&utm_medium=inline&utm_campaign=talk-photo-dev)

[Developers: there is an API](https://www.stork.ai/developers/talking-head-api?utm_source=house_ad&utm_medium=inline&utm_campaign=talk-photo-dev-second)

## Step 1: find the dead entries[#](#step-1-find-the-dead-entries)

Open every MCP config you use and search for three strings. Any entry containing one of them is affected.

The two address forms are the examples Smithery's own notice gives.
Search for What it is Example
--- --- ---
run.tools Smithery's hosted server address https://linear.run.tools
server.smithery.ai Smithery's older hosted address https://server.smithery.ai/linear
@smithery/cli A server started through the Smithery CLI npx -y @smithery/cli run ...

Where the config files live:

  • Cursor:~/.cursor/mcp.json , or.cursor/mcp.json inside a project.
  • Claude Desktop (macOS):~/Library/Application Support/Claude/claude_desktop_config.json .
  • Claude Code: runclaude mcp list . It prints every server and its address.
  • VS Code:.vscode/mcp.json in the workspace, or the MCP section of your user settings.

Step 2: replace each one with the server's own address# #

Most well-known services now run their own MCP endpoint. These are the addresses each vendor publishes under its own name in the official MCP registry, as we read them on November 16, 2026:

From the official MCP registry, each entry published under the vendor's own domain. Check the vendor's documentation before you rely on one.
Service Its own MCP address
--- ---
Linear https://mcp.linear.app/mcp
Notion https://mcp.notion.com/mcp
Supabase https://mcp.supabase.com/mcp
Stripe https://mcp.stripe.com
Figma https://mcp.figma.com/mcp
Vercel https://mcp.vercel.com
Neon https://mcp.neon.tech/mcp
Atlassian (Jira, Confluence) https://mcp.atlassian.com/v2/mcp
PayPal https://mcp.paypal.com/mcp
Exa https://mcp.exa.ai/mcp
Hugging Face https://huggingface.co/mcp

In clients that speak remote MCP directly (Cursor, Claude Code, VS Code) the entry becomes a single url. In Claude Code, for example: claude mcp add --transport http linear https://mcp.linear.app/mcp. Most of these endpoints ask you to sign in with your own account the first time. That is expected: Smithery used to hold that sign-in for you, and now your client does.

Step 3: for anything not in the table# #

  • Look at the server's page on smithery.ai. Smithery says the official address is shown there.
  • Ask your agent. Stork's free MCP server has a tool for exactly this. Addhttps://mcp.stork.ai/mcp to your client and ask it to find the replacement for the old address. The tool isstork_smithery_replacement : give it the old URL and it returns the listing published by the same vendor, with the address and what our last check of that address found.
  • Search the directory.Stork's MCP directory lists each server's address and when we last reached it.

Enjoying this? Get one like it in your inbox each morning.

one email a day · unsubscribe in two clicks · no third-party tracking

If the server was only ever hosted on Smithery# #

Some community servers had no address of their own. Smithery ran them. For those there are two routes. If the project publishes an npm or PyPI package, run it locally over stdio, using the command in the project's README. If it does not, the server is gone until its author hosts it somewhere, and the honest move is to look for another server that does the same job.

What we see when we connect to MCP servers ourselves# #

Stork connects to every MCP endpoint it has on file about once a week: one handshake and one request for the tool list, with no account. In the first several thousand endpoints of the run that began on November 16, 2026:

  • 55% completed the handshake with no account.
  • 36% answered and asked for a sign-in.
  • 9% did not answer.

Among the servers that listed their tools, the tool definitions alone add about 1,500 tokens to a model's context at the median, and more than 10,000 for the heaviest tenth. That number is on each listing, so you can see what a server costs before you install it. A check like this does not call any tool, so it cannot tell you that a server does its job or that it is safe. It tells you the address is alive today.

## Frequently asked questions[#](#frequently-asked-questions)

### Is Smithery shut down?[#](#is-smithery-shut-down)

Not entirely. The hosted connections, API, accounts, CLI and SDKs stopped on October 31, 2026. The website remains as a directory of MCP servers, and Smithery says it is now part of Arcade.

### Why did my MCP server stop working on November 1?[#](#why-did-my-mcp-server-stop-working-on-november-1)

If its address contains run.tools or server.smithery.ai, or it starts through the Smithery CLI, it depended on the hosted service that Smithery switched off. Point the entry at the server's own address.

### Do I need a new account for the official address?[#](#do-i-need-a-new-account-for-the-official-address)

You use your existing account with the service itself, for example your Linear or Notion login. Your MCP client opens the sign-in the first time it connects.

── more in #ai-agents 4 stories · sorted by recency
── more on @smithery 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/smithery-s-mcp-serve…] indexed:0 read:5min 2026-11-16 · —