> The MCP Registry service provides a centralized repository for MCP server entries. It allows discovery and management of various MCP implementations with their associated metadata, configurations, and capabilities.
https://mintlify.com/blog/why-we-sunsetted-mcpt
Nice story of startup focus.
Suppose you want your agent to use postgres or git or even file modification. You write your code to use MCP and your backend is already available. It's code you don't have to write.
Why should I be self-hosting ANY local MCP server for accessing an external service?
i.e. I wrote a server for water.gov to pull the river height prediction nearby for the next 24hr. This helps the campground welcome message writing tool craft a better welcome message.
Sure that could be a plain tool call, but why not make it portable into any AI service.
- https://github.com/wong2/awesome-mcp-servers
- https://cursor.directory/mcp
But as mentioned above, there is an ongoing discussion for the Anthropic registry https://github.com/modelcontextprotocol/registry
can't really fix this
Being able to offer a helpful API to the world and just getting paid whenever someone uses it would be really nice.
At the moment you have to process the payment "yourself" (even if you use a third party for that), issue an API key, etc.
Seems silly in retrospect no?
If you’re interested in the next layer beyond just discovering MCP servers, I’ve been working on https://ninja.ai — an app store for AI assistants to connect to tools via MCP, without needing to touch the command line. Think one-click installs for pipes that let agents actually do things like triage email or book Ubers.
Would love feedback if you’re experimenting in this space too!
In a year from now, Github will run a single public Github MCP server that you will connect to via OAuth - you won't need to install it locally or faff around with tokens or environment variables at all.
coderstartup•6h ago