Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Research synthesis with receipts: cited, critic-checked insights from interview transcripts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ANTHROPIC_API_KEY, MOTIF_RUNS_DIRValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"motif": {
"command": "uvx",
"args": [
"etot-motif"
],
"env": {
"ANTHROPIC_API_KEY": "your-value",
"MOTIF_RUNS_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add motif --env ANTHROPIC_API_KEY=your-value --env MOTIF_RUNS_DIR=your-value -- uvx etot-motifFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"motif": {
"command": "uvx",
"args": [
"etot-motif"
],
"env": {
"ANTHROPIC_API_KEY": "your-value",
"MOTIF_RUNS_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"motif": {
"type": "stdio",
"command": "uvx",
"args": [
"etot-motif"
],
"env": {
"ANTHROPIC_API_KEY": "your-value",
"MOTIF_RUNS_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MOTIF_RUNS_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account sleepycobalt, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ANTHROPIC_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
One server, usable from Claude Code, Cursor, Claude Desktop, and any MCP host. A designer or researcher working in an agent environment can say "synthesise these transcripts" and get the same cited, critic-checked result the CLI gives. Every tool is a thin call into synth/engine.py; the loop, prompts, and config are shared with the CLI and the FigJam plugin, never duplicated.
| Tool | In | Out |
|---|---|---|
motif_synthesize | transcripts_dir or files, question, condition (A/B/C), max_iterations | run id, insights JSON, report markdown, contested insight ids, cost |
motif_critique | insights (JSON) or document (markdown/prose); run_id or transcripts_dir; optional transcripts, question | verdict JSON (pass, failures, notes, skipped_rules), summary by rule and by insight, the structured insights, its own run id |
motif_receipts | turn_ids; run_id or transcripts_dir | verbatim turn text, speaker, whether the speaker was the interviewer; missing |
motif_board | run_id, columns, origin_x, origin_y | FigJam layout JSON + one use_figma script per insight for the host to execute through Figma's MCP server |
motif_runs_get | run_id, include | meta, notes, per-iteration verdicts; optionally insights, report, per-call token/timing |
Failure semantics: a missing verdict, an empty synthesis, an unparseable document, a run that does not exist, or turn ids none of which exist all return an MCP tool error. There is no empty success.
Progress: every engine progress line (each transcript ingested, each model call, each critic iteration) is sent twice: as an MCP log notification, which a host only receives if it has set a logging level, and as a progress notification, which a host receives if it passed a progress token (Claude Code does). stdout is the protocol; nothing else ever writes to it.
From PyPI, into any Python 3.10+ environment:
pip install "etot-motif[mcp]"
which motif-mcp # the server entry point; hosts need this absolute path
Or with no install step, if you have uv: the command is uvx --from "etot-motif[mcp]" motif-mcp. Installed this way the server uses the packaged config and writes run logs to ~/.motif/runs (override with MOTIF_RUNS_DIR).
From a Motif checkout:
git clone https://github.com/sleepycobalt/motif.git
cd motif python3 -m venv .venv && source .venv/bin/activate pip install -e ".[mcp]" echo "ANTHROPIC_API_KEY=your-key-here" > .env ls .venv/bin/motif-mcp # the server entry point
The server reads ANTHROPIC_API_KEY from the environment or the repo's .env, writes run logs to runs/ in the repo (override with MOTIF_RUNS_DIR), and uses config/synth.yaml, a symlink to the packaged synth/synth.yaml (override with MOTIF_CONFIG). Every host below needs the absolute path to .venv/bin/motif-mcp; hosts spawn servers without your shell's PATH.
claude mcp add motif -- /ABSOLUTE/PATH/TO/motif/.venv/bin/motif-mcp
Optionally install the skill so Claude Code knows the workflow (verify citations with receipts, mind contested insights, push to FigJam):
mkdir -p ~/.claude/skills/motif
cp /ABSOLUTE/PATH/TO/motif/surfaces/mcp/skills/motif/SKILL.md ~/.claude/skills/motif/SKILL.md
Then in a new Claude Code session:
/mcp # motif should show as connected
synthesise ./data/raw/Dataset-2 with motif and open the report
Claude Code calls motif_synthesize, streams the engine's progress, and can then call motif_receipts to verify any citation or motif_board to push the run onto a FigJam board via Figma's MCP server.
Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": { "motif": { "command": "/ABSOLUTE/PATH/TO/motif/.venv/bin/motif-mcp", "env": { "ANTHROPIC_API_KEY": "your-key-here" } } } }
Restart Cursor; the five motif_* tools appear under MCP tools.
Open the config file (Claude menu → Settings → Developer → Edit Config), or edit it directly:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": { "motif": { "command": "/ABSOLUTE/PATH/TO/motif/.venv/bin/motif-mcp", "env": { "ANTHROPIC_API_KEY": "your-key-here", "MOTIF_RUNS_DIR": "/ABSOLUTE/PATH/TO/motif/runs" } } } }
Quit and reopen Claude Desktop; the tools appear under the tools icon in the chat box. Claude Desktop cannot open files on your disk, so ask for the report markdown in the reply, or read it from the run directory.
Set MOTIF_REMOTE_URL and the same five tools forward to the hosted Motif service (surfaces/hosted/) instead of running the engine locally: no Python dependencies beyond the server itself, and the same results. Your ANTHROPIC_API_KEY is forwarded with each job and used for that job only. In remote mode a tool's run_id is the hosted job id, valid for an hour after the job finishes; motif_receipts, motif_board, and motif_runs_get take it. The hosted engine runs with the logger's redact=True: prompt and response bodies are stored as length + SHA-256, corpora are never snapshotted, and the job's uploads are deleted at expiry. MOTIF_REMOTE_TOKEN selects the paid tier, which is not switched on yet.
claude mcp add motif -e MOTIF_REMOTE_URL=https://motif-hosted.fly.dev -e ANTHROPIC_API_KEY=your-key-here -- motif-mcp
motif_board returns a layout and scripts; it does not touch Figma. The host (Claude Code with Figma's MCP server authenticated) runs each script with use_figma against a FigJam board URL and reads the result back with get_figjam. Verified on a real board on 2026-09-04 (docs/exhibits/step-zero/, docs/exhibits/board-r5/).
listing.md holds the descriptions for directories that index MCP servers; server.json is the manifest for the official MCP registry (publish after the package is on PyPI).
.venv/bin/python -m pytest -q tests # offline: stubbed model, spawns the server over stdio
.venv/bin/python scripts/critique_acceptance.py # spends API budget: critic vs eval2 human scoring