21–30 of 68 posts
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?
You don't need MCP you just need function calling
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.
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!
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.
You don't need MCP you just need function calling
Yes because we should all be building function calling implementations for the same 10 SaaS services rather than using 10 standard MCP servers.
Why should I be self-hosting ANY local MCP server for accessing an external service?
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
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?
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.