← Back to Blog
July 28, 2026 · 3 min read

Tulimoa runs MCP v2 from day one

The final MCP v2 specification was published today, July 28, 2026. Our public MCP server at mcp.tulimoa.com has been speaking it since this afternoon.

If you want the background on what MCP v2 actually changes, we wrote a plain-language explainer: [What is MCP v2?](/blog/what-is-mcp-v2). This post is about what we shipped.

What changed on our side

  • mcp.tulimoa.com now serves both protocol generations on the same endpoint. New clients get the stateless v2 protocol, including server discovery without a handshake. Older clients keep the classic 2025 handshake. Nothing to reconfigure on either side.
  • Tool lists ship with caching hints (public, one hour). Clients that understand v2 stop re-fetching the same catalog, which saves tokens in every session.
  • All five directory tools now declare structured output schemas, so agents get machine-readable results they can validate.
  • Our login infrastructure picked up v2's security hardening: the authorization server confirms its identity on every OAuth response, client registrations are bound to the server that issued them, and desktop or command-line apps register cleanly.

We tested both paths against production before publishing this post: a v2 client doing stateless discovery and calls, and a legacy client doing the old handshake. Both work.

What about the gateway?

The gateway at gateway.tulimoa.com moves in stages, on purpose. Its OAuth layer already carries today's security hardening. The MCP endpoint itself still serves the 2025 protocol, which every current client speaks, and it will keep doing so while we rebuild the stateless internals behind a test route. Connections from the gateway to your SaaS tools migrate first, the endpoint follows once the new code has proven itself. The gateway is the piece people depend on, so it gets the slow, careful treatment.

Why day one

Tulimoa's whole approach is efficiency: the memory layer that shrinks your token bill. MCP v2 pushes in the same direction at the protocol level, with requests that stand alone and catalogs that cache. A same-day upgrade was the obvious move, and running v2 in production early means the gateway migration will be built on experience instead of theory.

Try it

Add the server to any MCP client:

`claude mcp add --transport http tulimoa https://mcp.tulimoa.com/mcp`

Reading the directory needs no account. Submitting or editing a listing uses a Tulimoa login.

Tulimoa runs MCP v2 from day one · Tulimoa