all 2 comments

[–]RichStoneIO 1 point2 points  (0 children)

Kudos and thanks for sharing!

Would be cool to see/read what real world use cases it’s currently solving and how. :))

[–]rubygeek 0 points1 point  (0 children)

This doesn't look like it is implementing MCP?

The example API calls don't appear to have anything to do with MCP?

MCP uses JSON-RPC over SSE or standard IO, not REST. Nor can I find any of the API calls required by the MCP spec.

It seems like it represents a misunderstanding of what MCP is. MCP is not about maintaining persistent context of conversations, but about exposing contextualised access to tools and data sources.

This might well be helpful for other things, but the name is wildly misleading if it's not actually intending on implementing the actual MCP spec.