MCP Server
Connect AI coding tools to your team's memories via the Model Context Protocol.
Mneme exposes a Model Context Protocol (MCP) server over Streamable HTTP. This lets AI coding tools — Claude Code, Cursor, Windsurf, and others — query your team's memories directly during development.
Setup
1. Create an API key
Go to Settings → Integrations in the dashboard and create a new API key. Copy it immediately — the plaintext is only shown once.
2. Run the setup command
From the integrations page, copy the one-liner setup command:
curl -fsSL https://mnem.dev/setup | bashThis detects your installed tools (Claude Code, Cursor, Windsurf, Codex) and configures the MCP connection automatically.
3. Verify
In Claude Code, type /mcp — you should see mneme listed with tools available. Try asking Claude to search your team's memories.
In Cursor or Windsurf, open the MCP panel in settings to confirm the connection is active.
Available tools
search_memories
Semantic search across team memories using embedding similarity and multi-factor scoring (relevance, recency, confidence, corroboration).
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | yes | Freeform search query |
repo | string | no | Filter to a specific repo (owner/repo) |
limit | number | no | Max results (default: 5, max: 20) |
Example prompt: "Search for decisions about state management in acme/web-app"
get_memory
Retrieve a single memory by ID, including its full content, entity references, and evidence chain showing how the memory was formed and corroborated.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string (UUID) | yes | Memory ID |
list_memories
Browse memories for a repository with optional type filtering and pagination.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | yes | Repository full name (owner/repo) |
type | string | no | Filter: decision, pattern, convention, issue, preference, fact |
limit | number | no | Max per page (default: 50, max: 200) |
offset | number | no | Pagination offset (default: 0) |
create_memory
Persist a new memory from the current session — a decision made, a pattern discovered, a convention established.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | yes | The memory content (max 500 chars) |
repo | string | yes | Repository full name (owner/repo) |
type | string | no | Memory type: decision, pattern, convention, issue, preference, fact |
reasoning | string | no | Why this memory matters — evidence and context |
keywords | string[] | no | 3-5 searchable terms |
Access control
API keys are scoped to a GitHub App installation. Each key can only access memories for repos belonging to that installation. Requests for repos outside the key's scope return empty results (for search) or 403 errors (for list/get), without leaking whether the repo exists.
Troubleshooting
"mneme" not showing in /mcp
- Run the setup command again — it may not have detected your tool
- Check that
~/.claude.json(or equivalent) has the mneme entry undermcpServers
Connection errors
- Verify the API key is correct in your tool's config
- Check the connection status on Settings → Integrations — green means active, amber means idle, gray means the key hasn't been used
Empty search results
- Mneme needs signals to build memories — check the signals page to see if activity is flowing
- New installations may take a few minutes to process the first batch of signals