Agents

Maximem Vity MCP

Your memory, in every agent.

Add one URL and Claude Code, Cursor or any MCP-ready agent can recall your context, gauge what you know and write in your voice.

Monday morning, explaining yourself again

Every LLM call is stateless, so every agent starts out knowing nothing about you, and whatever it remembers was engineered on top of that by somebody. Within a project, you engineer it yourself: a CLAUDE.md file, Cursor rules, a README the agent reads first. Those work well for what they are, which is context about the codebase.

They stop at the edge of the project. Open Cursor for a side project, start a fresh Claude Code session in a new repo, or try an agent of your own, and you are back to explaining who you are, what you are building, how much you already know and how you like things written. The context lives in your head, and you are the integration layer between your tools.

Vity MCP moves that context out of your head and into one place every agent can reach.

$ claude mcp list

vity: https://vity-mcp.maximem.ai/mcp (HTTP) ✓ Connected

> /mcp

vity · 9 tools · 3 prompts

· Recall context· Search memories· Get user context· Query knowledge· Summarize· Get voice card· Rewrite as me· Remember· Capture conversation

> /mcp__vity__brief_me_on vector databases

Illustration

What Vity MCP is

MCP (the Model Context Protocol) is the standard way AI agents plug into outside tools. Vity MCP is a hosted MCP server that gives any MCP-ready agent access to your Maximem Vity account: the memory built from your AI chats, the knowledge graph of what you know, and the voice card that describes how you write.

You add it once with one URL and one API key. From then on, the agent can recall your context when it is relevant, check how deeply you know a subject before it explains one, and draft in your voice when it writes for you.

One server between your agents and your memory

Your agents

  • Claude Code
  • Cursor
  • Your own agent
  • Any MCP client

Vity MCP

One hosted server at vity-mcp.maximem.ai/mcp, authorized with your Vity API key

Your Vity account

  • Your memories
  • Your knowledge graph
  • Your voice card
  • Summaries that skip what you know

What your agent can do

Nine tools, each one a different way for the agent to use what Vity knows about you.

Recall context
The agent gets the memories that fit what you just said.
Search memories
Finds specific facts: a preference, a task, a person, a topic.
Get user context
A grounded view of where you stand on a topic: what you told it, and what to avoid. Claims it cannot back up are dropped.
Query knowledge
How deeply you know a subject, so the agent pitches its response at your level.
Summarize
Summarizes a link or text, skipping what you already know, section by section.
Get voice card
Your writing-style guide, so anything the agent writes matches your voice.
Rewrite as me
Turns a draft into your voice, tuned for Slack, email or wherever it is going.
Remember
Suggests a new fact for your memory, and waits for your approval rather than saving it behind your back.
Capture conversation
Saves a whole session so you can pick it up later.
tools your agent can call
9tools your agent can call
ready-made prompts
3ready-made prompts
URL to add, in any MCP client
1URL to add, in any MCP client
memories saved without your approval
0memories saved without your approval

Ready-made prompts

Write as me

Draft anything in your voice.

Brief me on

A briefing on any topic, pitched at what you already know.

Catch me up on

Where you left off, what you decided, and what is still open.

Add Vity MCP

You need a Vity API key, which starts with mx_, from app.maximem.ai/api-keys.

Claude Code

Run this in your terminal, with your key in place of mx_...

claude mcp add --transport http vity https://vity-mcp.maximem.ai/mcp \
  --header "Authorization: Bearer mx_..."
  1. 01

    Check it

    Run claude mcp list from your terminal.

  2. 02

    See the tools

    Inside a session, run /mcp to see Vity's tools.

  3. 03

    Keep the name vity

    The slash commands are named after it, for example /mcp__vity__brief_me_on.

Memory you own, rather than memory each tool rents you

Most AI tools now ship some form of memory, and each one keeps it inside that tool. What Claude learns about you stays in Claude; what Cursor learns stays in Cursor. Switch tools, or use three of them in a day, and the memory fragments along the same lines.

Vity MCP inverts that arrangement. The memory lives in your Maximem Vity account, and every agent you connect reads from and contributes to the same place, with nothing saved unless you approve it. As more of your work moves to agents, that is the difference between re-introducing yourself to every new tool and having your context arrive with you.

Your Vity memorymemories · knowledge · voice
Claude CodeCursorYour agentAny MCP clientOpenClawHermes

Illustration

The same memory as every Vity app

Rewrite as me uses your Sound Like Me voice card, and Summarize uses the same personalization as Summarize For Me. What your agent learns lands in the memory every other Vity app reads.

Frequently Asked Questions

Add Vity MCP with one command: claude mcp add --transport http vity https://vity-mcp.maximem.ai/mcp with your Vity API key in the Authorization header. Claude Code can then recall your context, search your memories and write in your voice in any session or repo.

Those files carry context about a project, and they do it well. Vity MCP carries context about you (who you are, what you know, how you write) across every project and every MCP-ready tool, so it complements project files rather than replacing them.

Any MCP-ready client. Claude Code and Cursor have setup steps above; any other client can use the same JSON config with the Streamable HTTP transport.

No. The Remember tool suggests a new fact and waits for your approval. Capture conversation saves a whole session when you ask it to.

Yes. Get voice card gives it your writing-style guide, and Rewrite as me turns a draft into your voice for Slack, email or wherever it is going.

The ready-made slash commands are named after it, for example /mcp__vity__brief_me_on in Claude Code.

The plugins recall and capture automatically around every turn of those specific agents. Vity MCP is one connector for any MCP-ready agent, which calls Vity's tools when it needs them.