41–50 of 68 posts
So far, I’ve catalogued over 6,000 MCP servers. 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 thi…
Is this like 10 years ago when you could find a Directory of GraphQL Servers? Seems silly in retrospect no?
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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?
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.
The market for MCP servers is the same as the market for rest endpoints: its a delivery mechanism for the underlying service. I don't think you can make money on them, they are too simple to clone, but you can make money charging for the API. If you have a per usage license making an MCP is a very obvious choice - if you charge per seat it is mostly a question of how how sticky you are versus the competition.
With some kind of MCP tip jar, they could extract the data they need and pay $0.02 for the service.
It would remove a lot of friction in the system, and could generate revenues for content & data creators.
Earlier quoted context omitted.
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?
Remote MCP servers can do prompt injection that instruct your local agent to do something else other than only the expected tool call. https://embracethered.com/blog/posts/2025/model-context-prot...
[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…
Earlier quoted context omitted.
The market for MCP servers is the same as the market for rest endpoints: its a delivery mechanism for the underlying service. I don't think you can make money on them, they are too simple to clone, but you can make money charging for the API. If you have a per usage license making an MCP is a very obvious choice - if you charge per seat it is mostly a question of how how sticky you are versus the competition.
I see value in a pay-per-execution model. I run a service which has a lot of proprietary data. Right now, if Anthropic/OpenAI wanted to use that data in their responses, they need to find me, setup an account, plug it into their chatbot, and return the data to an end user. With some kind of MCP tip jar, they could extract the data they need and pay $0.02 for the service. It would remove a lot of friction in the syste…