Context Card MCP Server

Get one. Or add it to yours. The essential MCP server for a project's context, memory, and identity - discoverable to any MCP client, and rendered as one card you can read. Its 9 documented tools cover agents, context. It runs locally over stdio via the published package.

People who work with agents and context and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-09-09 · ★ 2 · #128 OF 304 MAINTAINED MEMORY · VERIFIED 2026-09-18

MIT · TypeScript servers · how we verify → /methodology

01 · Install Context Card

before you install - you'll need

Set MCP_CONTEXT_CARD_ROOT before connecting.

Claude Code

claude mcp add wolfe-jam-mcp-context-card -- npx -y mcp-context-card

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "wolfe-jam-mcp-context-card": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-context-card"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

repo age created 2026-08-12 - young repo, little track record yet

license MIT - declared in the repository

npm package mcp-context-card - unscoped; check the name against the project README before installing

registry namespace io.github.Wolfe-Jam is GitHub-verified and matches the repo owner

03 · What Context Card can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can read the project's AGENTS.md - whole, or one section by heading, write a fact that will still be there next session, and read a fact stored in a previous session.

Capability map

Tools grouped from the project's README - what Context Card lets an agent do.

read & search

3 tools - e.g. return the project's AGENTS.md - whole, or one section by heading; the headings, so a client pulls one section instead of the whole file; what this project publishes, in what media types, via which surface

read_agents_md · list_agents_md_sections · list_context_sources

auth & access

1 tool - e.g. draft an AGENTS.md - BETTER from the repo's facts (via agents-md-facts), BEST when a project.faf exists - ready to drop in

author_agents_md

Remember

1 tool - e.g. write a fact that will still be there next session

remember

Recall

1 tool - e.g. read a fact stored in a previous session

recall

Forget

1 tool - e.g. drop or correct a stale fact

forget

Whoami

1 tool - e.g. this server's name, vendor, version, status, license

whoami

Render

1 tool - e.g. the whole card as one self‑contained HTML page (also GET /card)

render_context_card

Latest releases

v1.1.0 · 2026-09-08

The card scans in one screen - AGENTS.md sections collapse by default. · Every section is its own <details>, closed on load: the card opens as identity → section list → memory count → discovery. Click a section to read…

v1.0.1 · 2026-09-07

npx mcp-context-card now runs - it silently no-op'd when launched through npx or a global install (the bin main-guard compared an unresolved process.argv[1]). Plus: card opens your context in a browser at a terminal…

v1.0.0 · 2026-09-05

Stable surface. No functional change from 0.6.2 - this release declares the API settled and is the reference point everything downstream pins to. · The shape that's now stable: nine tools (read_agents_md…

04 · Who maintains Context Card

mcp-context-card is maintained by wolfe-jam. We track 2 MCP servers from wolfe-jam - 2 actively maintained, 3 combined GitHub stars, oldest repo from Jul 2026.

05 · Facts

category
memory - ranked #128 of 304 actively-maintained memory servers as of 2026-09-18.
release cadence
6 releases in the last 90 days (latest 2026-09-08)
registry
io.github.Wolfe-Jam/mcp-context-card (active, first published 2026-09-05 · 5 versions)
packages
npm:mcp-context-card

06 · Context Card FAQ

Is Context Card still maintained?

Yes - as of 2026-09-18, its last commit was 2026-09-09 and it shipped 6 releases in the last 90 days. We re-verify nightly.

What can Context Card do?

With this server connected, an agent can read the project's AGENTS.md - whole, or one section by heading, write a fact that will still be there next session, and read a fact stored in a previous session.

How do I install Context Card?

Run `npx -y mcp-context-card`. The README documents one environment variable (MCP_CONTEXT_CARD_ROOT) to set first. Set MCP_CONTEXT_CARD_ROOT before connecting. You can also paste the ready-made client config above.

Does Context Card run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Context Card

Pairs well with

Servers that cover what Context Card doesn't - only shown when the pairing reason fits the companion.

  1. Server Filesystem → filesystem companion filesystem · ★ 39,038
  2. Pdf MCP → filesystem companion filesystem · ★ 135