@ai-spec-room/mcp-adapter
v0.1.3
Published
MCP adapter — wires an MCP-capable AI runtime (Claude Code, Cursor, Codex) to the provider-neutral AI Spec Room core API.
Maintainers
Readme
@ai-spec-room/mcp-adapter
MCP adapter that connects any MCP-capable AI runtime (Claude Code, Cursor, Codex) to an AI Spec Room.
Quick start
cd into the folder whose notes you want this session to see, then:
# per room: create .mcp.json from the web UI's curl one-liner
curl -fsSL "https://ai-spec-room.vercel.app/api/rooms/<ROOM_ID>/mcp?token=<TOKEN>" > .mcp.json
# then open your runtime of choice
claude # or cursor, or codexThe .mcp.json tells the runtime to launch this adapter via npx -y @ai-spec-room/mcp-adapter on demand — no global install required. The adapter treats its current working directory as the private-memory root, so the folder you ran the command in is the folder the AI can search. No path configuration needed.
Private memory scope
The search_my_context MCP tool reads markdown files recursively under the adapter's context root. That root is resolved in this order:
MY_CONTEXT_DIRenv var — per-room explicit overrideASR_MY_CONTEXT_DIRenv var — shell-level default (e.g. exported in~/.zshrc)process.cwd()— fallback, the directory where the runtime launched the adapter
If you want to pin the notes folder regardless of cwd, set ASR_MY_CONTEXT_DIR once:
echo 'export ASR_MY_CONTEXT_DIR=~/notes' >> ~/.zshrc && exec $SHELLEnvironment variables
| Var | Required | Purpose |
|---|---|---|
| CORE_URL | yes | The spec-room core API, usually https://ai-spec-room.vercel.app |
| ROOM_ID | yes | Room UUID |
| PARTICIPANT_TOKEN | yes | Your A or B token for that room |
| MY_CONTEXT_DIR | no | Absolute path to private notes for this room |
| ASR_MY_CONTEXT_DIR | no | Shell-level default used when MY_CONTEXT_DIR is not set |
