MCP: An (Accidentally) Universal Plugin System
311–320 of 366 posts
Re: MCP: An (Accidentally) Universal Plugin System
#312Earlier quoted context omitted.
Yes I understand that, but how do I write these endpoints myself without using magic @mcp annotations? After like an hour of searching I finally found the Lifecycle page: https://modelcontextprotocol.io/specification/2025-06-18/bas... and I think it contains the answers I’m looking for. But I feel this should be roughly explained in the first introduction. Agree that most of the pages feel LLM generated, and borderli…
The reason why they do not expose the underlying server schema, is because you aren't supposed to write your own MCP server from zero, in the same way you aren't supposed to write your own GraphQL Server from zero. Yes, technically you could, but you are "supposed" to just use a library that builds the actual endpoints based on the schema for the version of MCP you are using. And only worry about building your tools,…
Re: MCP: An (Accidentally) Universal Plugin System
#313> "The author discovers API's/JSON RPC" I'm too young to be posting old_man_yells_at_cloud.jpg comments...
Re: MCP: An (Accidentally) Universal Plugin System
#314> emotional support portable fan I can't be the only person that non-ironically has this.
Re: MCP: An (Accidentally) Universal Plugin System
#315Anyone else feel like this article was written with ChatGPT
Here
> P.S. If you build an MCP server that makes your computer emit the smell of fresh bread, we need to talk.
Re: MCP: An (Accidentally) Universal Plugin System
#316MCP over SSE
MCP over streamable HTTP
Authorization? Hahaha nah just put a token in your config file
Actually never mind.
Let's add OAuth...
Oh wait why are 90% of the server still using studio
Oh no
Let's deprecate SSE now
Re: MCP: An (Accidentally) Universal Plugin System
#317Earlier quoted context omitted.
Regardless of how good a model gets, it can't do much if it doesn't have access to deterministic tools and information about the state of the world. And that's before you take into account security: you can't have a model running arbitrary requests against production, that's psychotic. I don't have a high opinion of MCP and the hype it's generating is ridicolous, but the problem it supposedly solves is real. If it ca…
> Regardless of how good a model gets I don't think this is true. My Claude Code can: - open a browser, debug a ui, or navigate to any website - write a script to interact with any type of accessible api All without MCP. Within a year I expect there to be legitimate "computer use" agents. I expect agent sdks to take over llm apis as defacto abstractions for models, and MCP will have limited use isolated to certain pl…
These are just tools Anthropic provides for you. Just like the tools a non-Anthropic service provides through their MCP server.
A community-led effort of tool creation via MCP will surely be faster and more powerful than waiting for in-house implementations.
Re: MCP: An (Accidentally) Universal Plugin System
#318Earlier quoted context omitted.
I wasn’t aware of this, it’s extremely shortsighted. My employees’ chats are my company’s data, and I should be able to use them as I see fit. Restricting API access to our own data moves them quickly in to the 'too difficult to continue doing business with' category. The reality is that Slack isn’t that sticky. The only reason I fended off the other business units who've demanded Microsoft Teams through the years is…
We migrated from Slack to Teams and while it does work, it’s also not very good (UI/UX wise). We also did try out Rocket.Chat and Mattermost and out of all of those Mattermost was the closest to Slack and the most familiar to us.
Super happy with it. No bullshit upgrades that break your way of working. Utilitarian approach to everything, the basics just work. Still has some rough edges, but in a workhorse kind of way.
Endorse.
Re: MCP: An (Accidentally) Universal Plugin System
#319Earlier quoted context omitted.
Unfortunately, I think we're equally likely to see shortsighted lock-in attempts like this [0] one from Slack. I tried to find a rebuttal to this article from Slack, but couldn't. I'm on a flight with slow wifi though. If someone from Slack wants to chime in that'd be swell, too. I've made the argument to CFOs multiple times over the years why we should continue to pay for Slack instead of just using Teams, but y'all…
If you are interested in scraping slack for personal use, I made a local-only slack scraper mcp: https://github.com/kimjune01/slunk-mcp
Re: MCP: An (Accidentally) Universal Plugin System
#320Earlier quoted context omitted.
Nobody remembers the semantic web anymore
It was supposed to be Web 3.0, but then Web3 happened. In all seriousness though, I think HN has a larger-than-average amount of readers who've worked or studied around semantic web stuff.
There's a shocking overlap of GPU-slinging tech-bros hyping both. Crypto-bros turned LLM-experts out of necessity when mining crypo on their rigs became unprofitable.