I can't wait for first-party remote MCP servers to become more common. Right now we're taking a strange detour of everyone trying to proxy everyone else's APIs and do manual API Key juggling because platforms aren't running their own MCP servers and clients don't support the latest OAuth changes.

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.

This is kind of what smithery does already. You can choose to install a local server, or connect to a remotely hosted server on smithery after authenticating through your GitHub OAuth.

I’ve been seeing MCP compared to extensions in web browsers. Which I find telling, since I wouldn’t exactly say web extensions have been a great success - it’s a pretty niche dev market, and the security posture remains pretty anxiety inducing

There's some movement on https://github.com/modelcontextprotocol/registry

> 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.

@ VS Code we've been collaborating on this and plan to ship initial support for registries in our next release.

Is this like 10 years ago when you could find a Directory of GraphQL Servers?

Seems silly in retrospect no?

I agree. There’s no need to centralize this list.

Here are a few more:

- https://smithery.ai/

- https://github.com/wong2/awesome-mcp-servers

- http://mcp.so/servers

- https://cursor.directory/mcp

But as mentioned above, there is an ongoing discussion for the Anthropic registry https://github.com/modelcontextprotocol/registry

FYI https://mcp.so/ is the exact same thing as was posted. Not sure why they directed to the github instead of the actual site..

We've built a version of this on steroids - not only a registry, but also one-click mcp hosting. Would love you eyeballs if you're into mcp: https://supermachine.ai

I wonder if there's a market for someone figuring out how to build monetization into MCP or something similar.

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.

I reckon the target market would have to be non-developers (because MCP servers are easily reproducible with LLMs, they even encourage it in the docs), and you wouldn't even mention MCP. Just have a list of tools which you can optionally enable in the chat client

Community MCP servers available as Docker images are also being listed here https://hub.docker.com/catalogs/mcp

Also interesting was mintlify's decision to start one and then shut it down.

https://mintlify.com/blog/why-we-sunsetted-mcpt

Nice story of startup focus.

> Messages flooded in from developers both within and outside our customer base, all eager to submit their servers to get listed. The validation was clear – there was significant demand for what we'd built.

I know Han and he's a smart guy but this is very very wrong lol. there's significant SUPPLY for what he built. because everyone is just trying to self promote by putting mcp wrappers of their stuff out. the hard part is the demand.

(and also the fact that anthropic is putting up an official registry so it'll be steamrolled)

There's a huge gap in this market for someone who can take these and make them trustworthy. Maybe the OpenRouter of MCP.

The underlying issue is always relying on a third party, on openrouter you're trusting the end model provider to not do funny business

can't really fix this

If you're paying said third party it's a decent mitigation.

maybe said third party could just run / veto most basic mcp servers so youcan run them on their server with some peace of mind

interesting

I don't see how they could ever be trust worthy without kneecaping the claimed benefits.

[Noob doubt]

Am I getting this right? Based on the architecture/flow diagram of MCP, every SaaS app out there can build an MCP server. But you'll need a "MCP host" to make it work, right? Right now, I'm only seeing a handful of hosts — Claude Desktop and Windsurf. Who will be building these "hosts"? I'm only seeing use cases revolving around these hosts. Is there any real-life production use-cases? How will this pan out?

Today there are a handful of client-side options, cline, Claude desktop, windsurf, Google’s ADK, etc. keep in mind though, we’re talking about a spec that was released around last Thanksgiving. It’s been like 7 months, and the pace of development has been blistering.

Once the authN/authZ stuff is fully codified and baked, we’ll see first part MCP gateways and the ability to connect to those tools with the Chatbot of your choice.

Consider what we see now as a developer preview…

What is a useful agent build with MCP?

I have an agent that creates new tools here: https://github.com/kordless/gnosis-evolve. I use it with Claude Desktop for a lot of different things, including browsing or searching for content, with the various crawlers that are out now. There's a crawl4ai tool that is pretty useful.

Super cool, Thanks

You don't need MCP you just need function calling

Yeah, but there is a distinct advantage to using a standard.

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.

Are we still writing code?

Yes because we should all be building function calling implementations for the same 10 SaaS services rather than using 10 standard MCP servers.

But the standard servers should be hosted by the service provider, like mcp.slack.com as a counterpart to api.slack.com

Why should I be self-hosting ANY local MCP server for accessing an external service?

That is being done as a stop gap until official servers are released. Ideally you are writing a server for your own product/service, or custom local work.

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.

Is there a better “universal” or standard framework to do itv

you don't need any universal standard, you just need functions specific to your app's use case

you can leverage MCPs without building any app at all.