MCP is just fancy SOAP
It seemed like everyone went wild over MCP when it first came out. There was lots of videos on YouTube that glorified the FOMO of not using an MCP.
I couldn't understand what everyone was excited about. It sounded like an API. After doing some digging, I realized it was alot like an API. Then I read more and I realized it's more like fancy SOAP, but it uses JSON. I do like JSON and I don't like XML. Also, I do not like SOAP; and my dislike it based on experience writing a client for a SOAP Service.
But, an MCP is for a LLM. That alone makes it easier to build a client. You just tell your thing that you have an MCP server at an address, and how to authenticate. Then your thing asks the MCP server "what can you do?" and your MCP server tells it. The MCP server exposes some functions the thing can call. Your thing reads the descriptions so it knows when to call those functions. It's pretty nice.
taskd has a MCP available for your thing to use. It's helped me reduce the amount of context I need to keep available to my thing. I'm also afraid to ask my thing questions, because we'll end up on a tangent, but now I just tell it to create a task to revisit a topic, and we can come back to it later.