I'm the creator of the protocol. First of all this protocol is made as a completely open-source and community driven alternative to MCP. We're actively looking for contributors and general discussion to make this better.
We take a fundamentally different approach to MCP. Tool calling should be lightweight and stateless by default, and instead of using a middleman MCP server between the agent and the tool, UTCP proposes offering a manual at the beginning of the transaction and then getting out of the way, so the agent can communicate directly to existing endpoints.
This approach fixes a lot of problems with MCP and most significantly makes UTCP much easier to update and adopt as changes don't break the entire ecosystem (tool providers usually don't have to do almost anything).
Very happy to hear feedback and reach out on discord for discussions and contributions!
Obv biased since I'm part of the team building it, but we think its super elegant. It uses a simple JSON manifest to connect to native APIs, so no need to build wrappers. Would love if you give it a try, and share your experience.
We're also implementing a UTCP-MCP bridge, as the last MCP server you'll ever need. (https://github.com/universal-tool-calling-protocol/utcp-mcp)
Hi thanks for sharing this!
I'm the creator of the protocol. First of all this protocol is made as a completely open-source and community driven alternative to MCP. We're actively looking for contributors and general discussion to make this better.
We take a fundamentally different approach to MCP. Tool calling should be lightweight and stateless by default, and instead of using a middleman MCP server between the agent and the tool, UTCP proposes offering a manual at the beginning of the transaction and then getting out of the way, so the agent can communicate directly to existing endpoints.
This approach fixes a lot of problems with MCP and most significantly makes UTCP much easier to update and adopt as changes don't break the entire ecosystem (tool providers usually don't have to do almost anything).
Very happy to hear feedback and reach out on discord for discussions and contributions!
I've just found out about this today, has anyone tried it?
Obv biased since I'm part of the team building it, but we think its super elegant. It uses a simple JSON manifest to connect to native APIs, so no need to build wrappers. Would love if you give it a try, and share your experience. We're also implementing a UTCP-MCP bridge, as the last MCP server you'll ever need. (https://github.com/universal-tool-calling-protocol/utcp-mcp)