Tool definitions, re-sent every session.
Connect a dozen tools and every schema gets dumped into context on each run. Your agent pays to re-read the same catalog it already saw.
Your agent forgets between sessions, so it re-sends context, re-fetches data, and re-derives what it knew. Every repeat costs tokens. Tulimoa is one endpoint with a memory layer that holds the thread, so your agent repeats itself less.
Tool definitions, re-sent every session.
Connect a dozen tools and every schema gets dumped into context on each run. Your agent pays to re-read the same catalog it already saw.
The same data, fetched twice.
After a context reset the agent does not remember it already pulled that record, so it calls the tool again and pays for the round trip a second time.
Decisions, re-derived from scratch.
Goals, IDs, and the reasoning behind them fall out of context on a long run. The agent rebuilds what it already knew, one expensive step at a time.
remember, recall, checkpoint, set_goal. The gateway keeps goals, decisions, and IDs alive across sessions and context resets, then hands them back when they matter.
Less repeated context means fewer tokens billed. It is a beta, so we measure the real savings live instead of quoting a number.
Federate your MCP servers behind a single URL. Add or remove tools without touching the agent config. It picks them up on the next run.
GDPR by default, secrets encrypted, connections revocable. Built in Germany, hosted in the EU.
Connect once by OAuth over your Tulimoa account. Per-connection control, revoke any time, an audit trail for every call.
The live, hand-reviewed catalog of agent-ready tools. Free to browse on the web and over MCP. Wired into the gateway from day one.
MCP (Model Context Protocol) is the open standard for connecting agents to tools. One endpoint, one schema. Point your agent at Tulimoa and it reaches every tool you have connected, without re-reading the whole catalog each run.
The memory layer captures the goals, decisions, and IDs that flow through the gateway, and a one-time instruction seed survives context compaction. The agent recalls instead of re-fetching, so it repeats itself less. We are in beta and measuring the real token savings, not quoting a made-up figure.
One line: claude mcp add --transport http tulimoa https://mcp.tulimoa.com/mcp. Your agent can search the directory right away. No account needed for reads.
Magic link or sign in with Google. No credit card. This is also how you join the Gateway beta.
Get access to the memory layer and federation as the beta opens up. One endpoint in front of your whole stack.
In the beta you point your agent at one gateway URL, connect tools once by OAuth, and memory holds the thread across runs so it re-sends less.
Not a mockup story: the catalog is live on /discover and over MCP. These three cards show what a listing looks like. Every tool is hand-reviewed, MCP status included.
Mockup listing. Shows what a sales CRM with MCP server would look like in the catalog.
Mockup listing. Shows what cloud accounting with MCP endpoint would look like in the catalog.
Mockup listing. Shows what a helpdesk with MCP support would look like in the catalog.
List it in the curated directory, free, with a do-follow backlink, so agents and teams can find it. It is the supply side of the gateway.