Why Claude can't reach a server on your machine#
An MCP server reaches a client in one of two ways. Over stdio, the client starts your server as a local process and talks to it through standard input and output. Over HTTP, the client calls a URL. Tools that run on your machine, such as Claude Code, Cursor and VS Code, can do both.
Claude on the web and on your phone can only do the second, through a custom connector, and the call does not come from your browser. It comes from Anthropic's servers, so the URL has to be public and served over HTTPS on the standard port. http://localhost:3000/mcp means nothing to a server in a data centre, and a stdio server has no URL at all.
| Client | stdio server on your machine | localhost URL | Public HTTPS URL |
|---|---|---|---|
| Claude Code | Yes | Yes | Yes |
| Cursor | Yes | Yes | Yes |
| VS Code | Yes | Yes | Yes |
| Claude desktop app | Yes, through its local config | No | Yes |
| Claude on the web and phone | No | No | Yes |
| ChatGPT on the web | No | No | Yes |
So to try your server in Claude before you have deployed it anywhere, you need a public URL that leads back to your machine.
First, check that the server works locally#
Rule out bugs in the server before adding a network to the picture. The MCP Inspector starts your server and lets you list and call its tools from a browser tab:
npx @modelcontextprotocol/inspector node ./server.jsIf the tools show up and return what you expect, the server is fine and the remaining work is getting a client to it.
Give the server a public URL#
otterkit mcp publish starts your server, wraps it as an HTTP MCP server and opens a public link to it. The server keeps running on your machine and nothing is deployed. Log in once, then publish:
npx otterkit login
npx otterkit mcp publish ./server.js ✓ Started schema-scout · stdio
✓ 3 tools found, 2 published
drop_table is marked destructive, so it stays private (--all-tools to include it)
✓ Live · tunnel-a1b2c3d4
Server https://tunnel-a1b2c3d4.otterkit.app/mcp/k7Qf3xZ9mB2nR8tLw4YpVc
Page open the same link in a browser
Tools list_tables describe_table
Rate 1 credit/hr · never more than 300/monthThe target can be a script, a command or a server that already listens locally:
# A script: .js, .ts and .py are started with the right runner
npx otterkit mcp publish ./server.py
# Any command that starts a stdio MCP server
npx otterkit mcp publish npx -y @modelcontextprotocol/server-everything
# A server that already speaks HTTP on a local port
npx otterkit mcp publish http://localhost:3000/mcpPublishing costs the same as a tunnel: 1 credit ($0.01) per connected hour. New accounts get 10 free credits. Every option is in the Publish an MCP Server reference.
Add the link to your client#
Claude (web, desktop and phone)#
- Open Customize, then Connectors.
- Choose Add, then Add custom connector.
- Give it a name and paste the link as the server URL.
- Under Authentication choose No sign in, then add it.
On Team and Enterprise plans an owner adds custom connectors in the organization settings, and members then connect to them.
ChatGPT#
- Open chatgpt.com/plugins.
- Select the plus button, then Add custom MCP server.
- Enter a name and paste the link as the Server URL.
- For authentication choose No authentication.
- Accept the warning, select Create as a plugin, then install it. In a chat, type @ and pick the server.
This needs ChatGPT on the web, and your workspace has to allow custom servers.
Claude Code#
claude mcp add --transport http schema-scout https://tunnel-a1b2c3d4.otterkit.app/mcp/k7Qf3xZ9mB2nR8tLw4YpVcCursor and VS Code#
Open the link in a browser. The page that loads lists the server's tools and has an install button for each editor, next to the same steps for the other clients. To add it to Cursor by hand, put the link in .cursor/mcp.json:
{
"mcpServers": {
"schema-scout": { "url": "https://tunnel-a1b2c3d4.otterkit.app/mcp/k7Qf3xZ9mB2nR8tLw4YpVc" }
}
}In VS Code, run MCP: Add Server from the Command Palette, choose HTTP and paste the link.
Watch the calls arrive#
Ask the client to use one of your tools. Each request prints in the terminal as it arrives, with the tool name, the client and how long your server took:
14:02:11 initialize claude-code 200 12ms
14:02:11 tools/list claude-code 200 8ms
14:02:19 tools/call list_tables claude-code 200 41msYour server's own log output appears in the same terminal, so a failing call and the stack trace behind it sit next to each other. Edit the server, restart the command and the client picks up the new version on its next call.
Keep it safe#
There is no sign-in on the link. Its last 22 characters are random, and anyone who has the whole link can call the published tools, so treat it like a password.
- Destructive tools stay private. A tool your server marks with
destructiveHint: trueis not published unless you pass--all-tools. - Publish only what you are testing.
--only list_tablespublishes one tool, and--exclude run_queryholds one back. - Replace a leaked link. Press
rin the terminal for a new link. The old one stops working at once. - Stop when you are done. Press
q. The link then leads nowhere.
When it doesn't work#
| What you see | Likely cause | Fix |
|---|---|---|
| Claude says it cannot connect | The link is incomplete, or the command is no longer running. | Copy the whole link including the part after /mcp/, and check the terminal is still live. |
| The connector worked yesterday | Each run gets a new link unless you ask for a stable one. | Run with --subdomain my-tools to keep the same link across restarts. |
| A tool is missing in the client | The server marks it as destructive, or a filter excluded it. | The command lists what it held back. Pass --all-tools if you want it public. |
| A slow tool fails | A call must finish within 28 seconds. | Return sooner, or split the work into a start call and a status call. |
| Could not start the MCP server | The command printed an error before speaking MCP. | Run the same command by itself, fix the error it prints, then publish again. |