If your product includes a public API, you need to publish an MCP server as soon as possible.
Don’t let anyone else be first with an MCP server that appears to be yours but isn’t.
Why? Because if their server becomes popular on one of the MCP registries, they’re now in control of your traffic and can change, throttle, intercept, or introduce prompt poisoning - on purpose or by mistake.
You want to be there first with an MCP in your name, under your control, and one you can maintain. Just like the early days of the web, when anyone could go grab a domain name.
It doesn’t matter if your first MCP server is limited or just wraps your APIs.
What matters is that you get started, get it out there, and then iterate and improve on it.
Just make sure to understand where to publish, what’s happening with the spec, and the security implications.
You’ve seen me write about who to follow and where to find resources - you can find them in the comments on the original LinkedIn post if you haven’t.
And if you’d like to see how to publish an MCP server for your API quickly, I’ll show you how for free: https://lnkd.in/eABN6qJD