TulimoaTulimoaDocs
Docs menu

Quickstart

Connect your agent to the Tulimoa gateway in two minutes: one endpoint, sign in once, then store and recall your first fact.

Last updated Sep 12, 2026

The gateway speaks MCP over streamable HTTP. Point your client at one URL and you are done setting up:

The endpoint
https://gateway.tulimoa.com/mcp

Only need a memory for your agent, without the gateway? Connect Tulimoa Memory directly, no account needed.

Connect your client

Claude Code
claude mcp add --transport http tulimoa https://gateway.tulimoa.com/mcp
Claude Desktop, Cursor, Windsurf, VS Code and any MCP client (mcp.json)
{
  "servers": {
    "tulimoa": { "type": "http", "url": "https://gateway.tulimoa.com/mcp" }
  }
}
OpenClaw
openclaw mcp add tulimoa --url https://gateway.tulimoa.com/mcp --transport streamable-http
ChatGPT: add the URL under Settings, Connectors
https://gateway.tulimoa.com/mcp

Sign in

There are two ways to authenticate, and you only need one of them:

  • OAuth, the default. On the first call your client opens a browser window and you sign in with your Tulimoa account once. After that the connection just works.
  • API key. Create a personal bearer key (prefix tlm_live_) under Settings, API keys, or one key per agent under Agents. Keys carry a scope, read or read+write, and can be revoked at any time.
Claude Code with an API key
claude mcp add --transport http tulimoa https://gateway.tulimoa.com/mcp --header "Authorization: Bearer tlm_live_..."

Over OAuth, all your sessions count as one agent. If you want to tell agents apart in usage and audit, give each one its own key on the Agents page.

Store your first fact

The memory tools are available immediately and never cost credits. Try the round trip:

Tell your agent
Today:      "Remember that our staging URL is https://staging.example.com"
              -> the agent calls tulimoa__remember

Next session: "What is our staging URL?"
              -> the agent calls tulimoa__recall and answers without searching

How scopes, retention and automatic ID capture work is covered in Memory in the gateway.

See it working

Every call shows up under Usage: calls per day, errors, credits, and an audit list of the last 200 calls. The Memories tab on the same page shows everything your agent has stored, editable and exportable as JSON.

Next: connect your tools under Connectors so your agent can actually do things, then read how the gateway works.