MCP Context Card logo

MCP Context Card

Serves project instructions, persistent memory, identity, discovery data, and a rendered context card through MCP.

Install MCP Context Card

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-context-card": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-context-card"
      ],
      "env": {
        "MCP_CONTEXT_CARD_ROOT": "YOUR_VALUE_HERE",
        "PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 10 tools correctly (3d ago).

Overview

The mcp-context-card MCP server exposes project context, persistent memory, identity, discovery metadata, and a rendered context card through MCP. It reads and writes project-local files including AGENTS.md, project.fafm, and identity files, while avoiding general filesystem, shell, or search access. Use it as a standalone base server or alongside another MCP server when agents need repository instructions and cross-session facts. It supports stdio and HTTP operation, with optional browser and inline MCP Apps views for the context card.

Use cases

  • Serve repository instructions to coding agents
  • Persist project facts between agent sessions
  • Draft or inspect AGENTS.md sections
  • Render a shareable project context card

Key features

  • Reads and authors AGENTS.md
  • Stores persistent project memory
  • Reports server identity
  • Publishes context-source metadata
  • Renders and saves HTML context cards

Tools10

What MCP Context Card lets your agent do. Expand a tool for its parameters.

Verified live~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

10/10 checks healthy over the last 49d

What it can do

From the 10 tools this server returned when we ran it; 10 declare their own safety hints.

Can delete or modify data · 3Makes network requests · 1Read-only tools · 7
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age54 days
Maintainers1

Observed 2026-10-28 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · mcp-context-card (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads1kPackage downloads in the last 30 days.
Last commit16d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed10Callable tools this server registers over MCP.

How MCP Context Card works

What mcp-context-card MCP server does

The mcp-context-card MCP server gives an MCP host a structured view of a project’s instructions, memory, and identity. It can read AGENTS.md as a whole or by heading, list available sections before retrieving them, and draft a new AGENTS.md from repository facts. When project.faf is present, the authoring flow can include its structured goal, audience, and rationale.

Memory is stored across sessions in the project’s memory file. Agents can add facts with remember, retrieve them with recall, or remove and correct outdated entries with forget. Identity information comes from the server’s supported fafa files and is exposed through whoami, including details such as name, vendor, version, status, and license.

The server can also describe its published context sources and render the complete card as a self-contained HTML document. This makes it suitable for a base MCP that supplies common project context or as a companion process next to an existing filesystem, Git, database, or custom MCP server.

How it works

The server first determines which project to serve. An MCP root supplied by the host takes precedence; otherwise it can use its startup directory when that directory contains AGENTS.md. MCP_CONTEXT_CARD_ROOT can pin a specific project path and takes priority over automatic selection. The list_context_sources tool reports the selected project and the available publication surfaces.

For interactive clients, render_context_card returns the complete card and can be displayed inline by hosts that support MCP Apps. On HTTP transport, the same content is available at GET /card, with options for expansion, theme, and accent color. save_context_card writes context-card.html to the project, opens it in a local browser, and returns a Markdown summary plus a link to the full page.

The card combines identity, AGENTS.md sections, memory, and discovery information. Sections are collapsed by default, while an expanded mode is available for screenshots or fully open output. Memory summaries normally include a small set of facts; full detail can be requested when needed.

Setup and configuration

Node.js 20 or newer is required. To preview a project card without configuring an MCP host, run:

Terminal
npx mcp-context-card card

The command writes context-card.html and opens it in a browser when run interactively. Redirected output produces raw HTML, and --expanded opens every section. A host can launch the stdio server with npx, for example:

config.json
{
  "mcpServers": {
    "context-card": {
      "command": "npx",
      "args": ["-y", "mcp-context-card"]
    }
  }
}

For HTTP operation, set PORT before starting the package. If a host cannot find npx, configure it to invoke Node with the installed distribution entry point instead. The server does not require a project path when MCP roots are available, but MCP_CONTEXT_CARD_ROOT provides an explicit override.

Tools and capabilities

The mcp-context-card MCP server exposes tools for:

  • Authoring, reading, and section-listing for AGENTS.md.
  • Persisting, retrieving, and deleting project facts.
  • Reporting server identity and context-source metadata.
  • Rendering or saving a self-contained HTML context card.

It reads and writes only its supported project files: AGENTS.md, project.fafm, the supported identity file, and a saved context-card.html. It does not provide general file access, shell execution, or search.

Limitations and notes

The quality of an authored AGENTS.md depends on facts available from the repository and on whether project.faf exists. Identity is optional and is read from agent.fafa or .well-known/fafa according to the project’s available files. The server’s memory and identity formats are described as replaceable examples, while AGENTS.md remains plain Markdown.

The mcp-context-card MCP server is licensed under MIT. Its inline card behavior depends on MCP Apps support in the host; other clients receive Markdown or can use the saved HTML page. Running it alongside another MCP requires a host that accepts multiple server entries.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Context Card

mcp-context-card is an MCP server that exposes a project's AGENTS.md context, persistent memory, and identity through MCP. It connects to the project directory and provides author_agents_md, read_agents_md, list_agents_md_sections, remember, recall, forget, whoami, discovery, and card rendering tools.

Run it with npx, so a separate installation is not required: `npx -y mcp-context-card`. Configure that command in an MCP host, or run `npx mcp-context-card card` from a project directory to create and open a context card.

Set `MCP_CONTEXT_CARD_ROOT` to an absolute project path to pin the server to that directory. Otherwise, the server uses an MCP root supplied by the host, then falls back to its startup directory when that directory contains AGENTS.md.

Yes, it can run with Cursor through the standard MCP configuration. If Cursor cannot spawn `npx` because its process PATH is incomplete, configure the host to invoke Node with the installed `dist/bin.js` entry point instead.

Call `render_context_card` for the card content or `save_context_card` to write `context-card.html` and open it locally. The command `npx mcp-context-card card` provides the same standalone preview, with `--expanded` available for fully open sections.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Context Card AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-context-card?style=directory)](https://allmcps.com/mcp/mcp-context-card)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-context-card"><img src="https://allmcps.com/api/badge/mcp-context-card?style=directory" alt="MCP Context Card on AllMCPs" /></a>