Use it from wherever your agent runs.

A REST API and a hosted MCP server today: 13 ways in that work now, and 15 more on the way, each marked. Every row opens its docs page.

Claude Code, one command

claude mcp add --transport http twin-memory \
  https://api.twinmemory.dev/v1/mcp \
  --header "Authorization: Bearer $TWIN_MEMORY_API_KEY" \
  --header "X-Twin-Account: user_42"

The key names your project; X-Twin-Account names the end user whose memory the agent reads.

API

Every other way in is built on these routes. A bearer key names your project; one header names your end user.

API2 of 2 live

MCP clients

One hosted URL. The model gets the read tools, and a write key adds memory_add.

MCP clients7 of 8 live

SDKs and CLI

Typed clients over the same routes, so a call is one line in your own language.

SDKs and CLIplanned

Agent frameworks

Memory adapters that plug into each framework's own memory or tool interface.

Agent frameworksplanned

Coding-agent plugins

Plugins that save each session and bring back what a past session learned.

Coding-agent pluginsplanned

Connectors

Your users' work tools, synced into their memory with their permission.

Connectors4 of 4 live

Marketplaces

Buy through the cloud account you already pay.

Marketplacesplanned

Missing the one you use?

Tell us what your agent runs on. The REST API works from anything that speaks HTTP.

Ask for an integration Quickstart