I still prefer MCP over skills

Re:I still prefer MCP over skills by nostrebored on Friday April 10, 2026 @12:34AM (#47713702)

This is obviously not what it is. If I give you APIGW would you be able to implement an MCP server with full functionality without a large amount of middleware?

[ Parent | on HN ]

Re:I still prefer MCP over skills by victorbjorklund on Friday April 10, 2026 @04:03AM (#47715002)

If I gave you that could you implement Graphql from scratch without a large amount of middleware? Or are we now saying graphql api:s are not api:s?

[ Parent | on HN ]

Re:I still prefer MCP over skills by notpushkin on Friday April 10, 2026 @03:01AM (#47714553)

Sorry, could you rephrase that?

[ Parent | on HN ]

Re:I still prefer MCP over skills by ok_dad on Friday April 10, 2026 @05:06AM (#47715421)

I’ve implemented an MCP tool calling client for my application, alongside OAuth for it. It was hard but no harder than anything else similar. I implemented a client for interference with the OpenAI API spec for general inference providers, and it was similarly as hard. MCP. SDKs help make it easy; MCP servers are dead simple. Clients are the hard part, IMO.

MCP is basically just an RPC API that uses HTTP and JSON, with some other features useful for AI agents today.

[ Parent | on HN ]