Skip to main content
Your AI tools each start from zero. This connects them all to the same memory. The Vity MCP server exposes your memory over the Model Context Protocol, so any MCP-capable agent can recall what you have told it before, look up what you already know, put forward new facts for your review, and write in your voice. You paste a URL and an API key; the agent discovers the tools and decides when to call them on its own. Unlike the OpenClaw and Hermes plugins, nothing is recalled or saved automatically before or after each turn: your agent calls a tool only when it decides to, or when you ask it to.
This is the Vity MCP server: memory for you, in the AI tools you personally use, with an mx_ key. Building a product whose users need memory? That is a different product with its own MCP server and synap_ keys; see Vity or Synap?.

​
Connection details

​
What your agent can do

Ten tools, in four groups. See Tools & prompts for arguments and per-tool guidance.

Recall

recall_context for a ready-to-use context block, get_user_context for a structured profile on a topic, search_memories for specific remembered facts, get_profile_card for who you are at a glance: name, work, location, skills, interests and goals.

Knowledge

query_knowledge returns what you know about a subject and how deeply, so the agent can pitch its answer at the right level.

Voice

get_voice_card returns how you write; rewrite_as_me restyles a draft in your voice; summarize gives you a summary that skips what you already know.

Capture

capture_conversation saves a whole session so it survives into later ones. remember puts one durable fact forward for your review; it is not saved to your memory, and recall can’t find it until it is approved.
Also available: three prompts (write_as_me, brief_me_on, catch_me_up) and two resources (vity://voice-card, vity://knowledge/topics).

​
Get your API key

Generate it in the Vity dashboard at app.maximem.ai, not the Synap dashboard at synap.maximem.ai. They are separate products with separate keys: Vity keys start with mx_, Synap keys start with synap_. A synap_ key will be rejected here.
  1. Sign up or log in at app.maximem.ai.
  2. Open API Keys in the sidebar.
  3. Click Generate API Key, enter a name, and click Generate Key.
  4. Copy your key (starts with mx_...). Vity shows it only once.
Configuration covers keys in more detail, including how to revoke one.
Keep this key secure. Anyone who has it can read, add to and delete from your memory; treat it like a password. Use a separate key per tool so you can revoke one without breaking the others. Every key on your account reaches the same memory, so a second key does not give you a separate one.

​
Connect your client

Confirm it connected:
vity should appear as connected. Inside a session, /mcp shows the same thing along with the available tools.

​
Check it works

Ask your agent something that can only come from memory:
It should call get_profile_card, recall_context or get_user_context and answer from your memory. If it answers “I don’t have any information about you”, the connection is fine but your memory is empty; see Troubleshooting.

​
Client compatibility

This server authenticates with an API key in a request header, so it works with any client that lets you set custom headers: Claude Code, Cursor, and most CLI and desktop MCP clients.
Clients that only support OAuth connectors and give you nowhere to put a header (currently the Claude.ai and ChatGPT connector UIs) cannot connect to this server yet. Use a client that accepts headers, or the OpenClaw and Hermes plugins.

​
Your data stays yours

Your API key decides whose memory the agent reaches. None of the tools takes a user or account argument, so your key reaches only your own account. What that means in practice:
  • A key only ever reaches its own account. Sharing a key shares your memory; revoke it in the dashboard to cut access immediately.
  • Only some tools write. capture_conversation saves the messages you give it, and Vity then picks out memories from them. summarize also saves a short note about what you read to your memory. remember does not save to memory: it puts the fact forward for your review. The other tools only read.
  • Your content is processed by outside AI model providers. Vity and those providers process what your agent sends and recalls, as described in Privacy and data. Vity is not end-to-end encrypted.
  • Deletion is not exposed over MCP. Deleting memories is a dashboard action, so no agent can remove your memory on its own initiative. See Deleting memories.

​
Rate limits and credits

Limits apply per Vity account, per minute, not per key: all of your keys share them. Most retrieval tools allow 60 calls per minute; the LLM-backed ones are lower. rewrite_as_me also has a limit of 1,000 rewrites per day, shared with get_voice_card, and remember is limited to 200 per day. Credits are charged to the account, whichever key makes the call. Currently, recall_context, search_memories, query_knowledge and capture_conversation cost 1 credit per call, and summarize costs 20. The other tools are free. Your balance is shown in the dashboard; see Credits. See the per-tool table for exact figures. When a limit is hit, the tool returns a plain-language message the agent can act on, rather than a protocol error. For a rate limit the agent should wait and retry. For credits, retrying won’t help until your balance is above zero: the credit-charging tools stop working at zero, and the dashboard has no screen for adding credits today, so email [email protected].

​
Troubleshooting

The header did not reach the server. Check that your config uses the exact header name Authorization and the value Bearer mx_..., including the word Bearer and the space after it. In Claude Code, re-add the server with --header quoted as a single argument.
The key is wrong, was revoked, or belongs to the wrong product. Confirm it starts with mx_ (a synap_ key belongs to a different product and will not work here), then generate a fresh one at app.maximem.ai and update your client config.
Confirm the URL includes the /mcp path and that the transport is set to Streamable HTTP rather than SSE. Restart the client after editing its config; most read MCP config only at startup.
Your memory may genuinely have nothing on that subject yet. Memory builds up as you use Vity, so a new account starts empty. Use the browser extension, OpenClaw or Hermes for a while, or ask your agent to run capture_conversation, then search again. Don’t rely on remember for this: it puts a fact forward for review instead of saving it.If you expect a match, the minimum relevance score may be too high. Ask the agent to retry search_memories with min_score around 0.15.Just captured a conversation? Vity processes it in the background; give it a few seconds before searching.
get_voice_card and rewrite_as_me need a voice profile built from your writing. Build one with Sound Like Me, then retry.
recall_context, search_memories, query_knowledge, capture_conversation and summarize need a positive credit balance. Retrying won’t help until you have credits again. The agent’s message may suggest topping up at app.maximem.ai, but the dashboard has no screen for that today; check your balance there and email [email protected].
Still stuck? Email [email protected].