| ▲ | notatoad an hour ago | |||||||||||||||||||
it's not easier for agents to work with. it's easier for organizations to work with. for agents, they're essentially the same thing - remote endpoints, and instructions on how to call those endpoints. what MCP brings is centralized updating and distribution of the instructions, and a promise that the skill and the REST api won't be out of sync with each other. the one thing that skill.md+REST doesn't solve is how you get that skill.md to somebody else's computer, and how you ship an update to somebody else's computer once they've got a copy of the skill. if that's a problem you need to solve, you can either start inventing skill.md distribution protocols, or you can just use MCP. | ||||||||||||||||||||
| ▲ | skybrian 6 minutes ago | parent | next [-] | |||||||||||||||||||
It seems like organizations will mostly want remote access via http and the other flavors of MCP aren’t so useful? Although, I suppose if you install an app locally, it might have an MCP interface. | ||||||||||||||||||||
| ▲ | AznHisoka 12 minutes ago | parent | prev | next [-] | |||||||||||||||||||
Maybe I just need more patience, but I took a look at some tools that have MCPs, and their "setup guide" on how to start using the MCP server really gave me brain damage. Is this really easier to work with? | ||||||||||||||||||||
| ▲ | boredumb an hour ago | parent | prev [-] | |||||||||||||||||||
How is distributing a markdown file the bottleneck? | ||||||||||||||||||||
| ||||||||||||||||||||