After Smithery - move your MCP servers

If a tool in your editor or agent reaches an MCP server through a Smithery address, plan to replace that address. Smithery announced that its connection services end on 31 October 2026. The notice still read as an upcoming shutdown when this page was checked on 2 November, so test your own servers to see whether the old addresses still answer.

What was checked: On 31 October and again on 2 November 2026 we read Smithery's notice, Cloudflare's remote MCP server guide and the MCP Registry quickstart. The commands below come from those pages and were not run for this guide.

What ends and what staysCopy Anchor Link

Ends, per Smithery's notice:

• Server URLs on run.tools and server.smithery.ai
• The Smithery API, Connect and Toolbox
• Smithery accounts and API keys
• The Smithery CLI and SDKs. Current versions get marked deprecated.

Stays:

• smithery.ai as a public directory of MCP servers, now powered by Arcade.dev. It lists servers and no longer proxies them.

If you use MCP serversCopy Anchor Link

1. Open your client's MCP config (Claude Code, Cursor, Codex or another client) and search it for smithery, run.tools and server.smithery.ai. Each hit is a server that needs a new address.
2. Open that server's page on smithery.ai. Smithery says verified servers show the vendor's direct MCP URL there.
3. Replace the Smithery address with the direct URL. Keep the server name the same so your prompts and allow-lists still match.
4. Sign in again with the vendor. Smithery accounts and API keys end with the service, so a key you issued through Smithery stops working.
5. If a config launches a server through the Smithery CLI, replace that launcher with the server's own run command from its repository README.
6. Restart the client and call one tool from each server before you rely on it.

If the page shows no direct URL, the server may have relied on Smithery to host it. Look in the server's repository for a hosted endpoint or a self-host guide. Do not guess an address.

For ready-made integrations such as Gmail or Slack, Smithery points to Arcade.

If you publish an MCP server or manage connections for your usersCopy Anchor Link

Smithery's notice gives authors no steps beyond needing a replacement. This is one route that works from the docs of the two vendors involved. It is not the only route, and porting a server that ran over stdio is your work.

Host it yourself on Cloudflare WorkersCopy Anchor Link

1. Create a project from Cloudflare's template: npm create cloudflare@latest -- remote-mcp-server-authless --template=cloudflare/ai/demos/remote-mcp-authless. Answer No to the AGENTS.md and git prompts, and No to deploying.
2. Enter the project directory (cd remote-mcp-server-authless) and run npm start. The endpoint is http://localhost:8788/mcp. Opening it in a browser shows nothing useful, because it expects MCP client messages.
3. Test with npx @modelcontextprotocol/inspector@latest: enter the /mcp URL, choose Connect, then List Tools.
4. Deploy with npx wrangler@latest deploy. The server answers at https://<name>.<your-account>.workers.dev/mcp.
5. Give your users the new address to put where the Smithery one was.

The transport is Streamable HTTP and the template keeps no state between requests. It has no sign-in, so anyone can call it. If your server needs accounts, put it behind an OAuth authorization server built with Workers OAuth Provider and read the signed-in user inside your tools. Cloudflare's Authorization docs cover that.

List it in the official MCP RegistryCopy Anchor Link

The registry is in preview, so breaking changes or data resets can happen.

1. Add mcpName to the package's package.json, for example io.github.<your-username>/<server>. With GitHub sign-in the name must start with io.github.<your-username>/. A custom domain prefix needs DNS authentication.
2. Publish the package to npm first. The registry stores metadata only.
3. Install mcp-publisher, run mcp-publisher init to create server.json, and make its name match mcpName.
4. Run mcp-publisher login github, then mcp-publisher publish.
5. Check with curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=<your-name>".

The server.json above is the npm package example. Remote servers have their own registry page, remote servers. Read it before you list a server hosted on Workers.

Paid Smithery plansCopy Anchor Link

Smithery says it refunds every charge since 5 August and cancels subscriptions. Refunds usually take 5 to 10 business days.

Starlight MCP endpointsCopy Anchor Link

Starlight's public MCP servers already run over direct Streamable HTTP and never required a Smithery proxy:

• Substrate & Department Lab: https://starlightintelligence.ai/mcp
• Estate Documentation: https://docs.starlightintelligence.ai/api/mcp

See MCP tools reference for schemas and JSON-RPC 2.0 examples, and Harnesses for client setup.