2 posts tagged with "Production"

If you've set up an MCP server before, you know the drill. Clone a repo. Install dependencies. Add your API key to a JSON config file. Start the process. Configure your AI client to connect to localhost:3000. Repeat for every service you want to use.

It works. Until it doesn't. The process crashes silently. Your laptop sleeps and the server dies. You upgrade Node and the dependencies break. A teammate wants access and you're sharing API keys over Slack. You add a third service and now you're managing three server processes, three config files, and three sets of credentials in plaintext on your machine.

Local MCP servers are fine for trying things out. For daily use across a team, you need hosting.

Our bundle search tool was taking 12 seconds at P95. Users would ask Claude to "find the Slack integration," watch nothing happen, then ask again. Claude would make the same call twice, wait 24 seconds total, and users would close the tab thinking our service was down.

The tool worked perfectly. It just worked slowly. And in the world of AI assistants, slow might as well be broken.