UltraMemory MCP Server

Cross-tool memory for your AI that recalls first every turn and admits when it doesn't know.

Remote serverstreamable-http

What is the UltraMemory MCP server?

Cross-tool memory for your AI that recalls first every turn and admits when it doesn't know. Exposed over MCP by the ultramemory mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

One memory across Claude Code, Claude Desktop, claude.ai, Cursor, ChatGPT, Perplexity, Gemini CLI, OpenClaw, and Hermes. Recalls first every turn — and is honest enough to say "I don't know" instead of making things up.

Its toolset

Everything the assistant can do here goes through one of these:

  • memory_recall — read
  • recall_gated — read
  • recall_verified — read
  • search — read
  • fetch — read
  • playbook_recall — read
  • memory_write — write
  • memory_feedback — write
  • playbook_write — write

Configuration

You will need one environment variable: ULTRAMEMORY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. UltraMemory's toolset — memory_recall, recall_gated, recall_verified and 6 more — is a fair guide to whether it matches your workflow. It is maintained by LogicLabsAI; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch UltraMemory.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the ultramemory mcp server does with a few real requests.

Available tools

ToolWhat it does
memory_recallread
recall_gatedread
recall_verifiedread
searchread
fetchread
playbook_recallread
memory_writewrite
memory_feedbackwrite
playbook_writewrite

Configuration

VariableDescriptionRequired
ULTRAMEMORY_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use UltraMemory to memory recall.
  • Use UltraMemory to recall gated.
  • Use UltraMemory to recall verified.

Frequently asked questions

It connects UltraMemory to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (memory_recall, recall_gated, recall_verified, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with UltraMemory directly.