How the gateway works

One MCP endpoint that federates all your connected tools and adds memory tools, an encrypted credential vault, per-tool controls and an audit trail.

Last updated Sep 12, 2026

The gateway is one MCP endpoint with all your tools behind it. Your agent talks to gateway.tulimoa.com/mcp and sees the tools of every connected service, each namespaced as service__tool (for example github__create_pull_request). Which services sit behind the endpoint is managed in the dashboard, without ever reconfiguring the agent.

One endpoint, many tools#

Add or remove a service in Connected tools and the agent sees the change on its next tool list, mid-session. If one downstream service is temporarily down, the gateway serves the last known good tool list for it instead of dropping everything. On top of plain routing, the gateway adds four things:

• Memory. The gateway watches what flows through, keeps important facts and IDs, and hands them back at the right moment. Details in Memory in the gateway.
• An encrypted credential vault. Per-service sign-ins are stored encrypted and only decrypted for the moment of a call. See the vault.
• Per-tool switches. You can turn individual downstream tools off without disconnecting the service. See Connectors.
• An audit trail. Every call writes one metadata event (tool, success or error, latency, sizes), no content. The last 200 calls are listed under Usage.

What happens on a call#

1. Your agent sends tools/call with its OAuth token or bearer key. The gateway checks rate limits and resolves who is calling.
2. If it is one of the native memory tools, the gateway answers itself. That is why memory never costs credits.
3. Otherwise the namespace picks the connector. For write tools the token must carry the write scope, checked before any credential is even read.
4. The gateway opens a fresh connection to the service, decrypts your stored sign-in only for this moment, makes the call and closes the connection again.
5. The memory layer captures IDs from the structured result and, only when something notable changed, appends one compact reminder block.
6. One metadata event is written for your usage view. The answer goes back to your agent.

The credential vault#

Every per-service sign-in (API key or OAuth tokens) is envelope-encrypted with AES-256-GCM: each credential gets its own random key, which is itself encrypted with a master key that never leaves the gateway. Ciphertexts are bound to your user and connection, so they cannot be moved to another account. Credentials are decrypted only in the moment of a call, never logged, never cached across requests. OAuth tokens refresh automatically, and you can revoke any connection at any time under Connected tools.

Tool catalog and slimming#

Lots of connected services means lots of tool definitions, and tool definitions cost your agent context. With a large catalog the gateway serves a slim list of the most relevant tools and adds two meta tools so nothing is lost:

Your dashboard, mapped#

EU hosting and GDPR#

Hosting, storage and processing run in the EU, and session state is pinned to EU jurisdiction. Usage events are metadata only, never tool contents. Security-relevant actions (a credential decrypted, a token revoked) additionally land in a hash-chained audit log. Under Settings you can export your data (GDPR Art. 20) and erase your gateway memory or your whole account (Art. 17) at any time.