# mcp-context-card [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/Wolfe-Jam/mcp-context-card  
**GitHub Stars:** 3  
**npm Downloads (last month):** 1957  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/mcp-context-card

## Description
MCP server for a project's context (AGENTS.md), memory, and identity — base or drop-in extension.

## Tools
Capabilities this server exposes over MCP:

- **read_agents_md** — Return this project's AGENTS.md — the whole file, or one section by heading. The instructions a client would otherwise have to know to look for and read wholesale.
- **author_agents_md** — Author an AGENTS.md for this project and return the draft — BETTER from repo facts alone (via agents-md-facts: real build/test commands, entry points, toolchain conventions, nothing invented), or BEST when a project.faf exists (facts plus its structured goal/who/why as a second managed block ahead of them). Does not write a file.
- **list_agents_md_sections** — List the headings in this project's AGENTS.md, so a client can pull one section instead of spending context on the whole file.
- **remember** — Persist a fact past the session boundary — written to a .fafm file, not held in memory. Reusing an existing id replaces that fact's text in place (no duplicate); a new id appends. Facts are written verification_status: unverified.
- **recall** — Retrieve a fact stored in a previous session by id. Exact lookup — not fuzzy or substring.
- **forget** — Remove a fact by id — to correct or drop something stale. A missing id is reported, not an error.
- **whoami** — This server's own identity — name, vendor, version, status, license — from its .fafa card.
- **list_context_sources** — What context does this project publish (AGENTS.md, memory, identity), in what media types, and through which discovery surface. For a client connecting cold.
- **render_context_card** — Render the project's business card as one self-contained HTML page a person can read or screenshot. Front: name, title, one-liner. Flip it for the back: About, Skills (when the .fafa lists any), Context (AGENTS.md), Memory, Discovery. layout:"portrait" for the tall view; expanded:true renders both faces flat with every section open. Also served at GET /card (?expand=all) over the HTTP transport.
- **save_context_card** — Write the context card to context-card.html in the project and, when this server runs locally, open it in the person's browser. Returns the card as Markdown (identity, AGENTS.md sections, memory, discovery) plus a clickable link to the saved file. Use this instead of pasting render_context_card's HTML into a chat that can't display it. Replaces any earlier context-card.html.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-context-card": {
    "command": "npx",
    "args": ["-y","mcp-context-card"],
    "env": {
      "MCP_CONTEXT_CARD_ROOT": "",
      "PORT": ""
    }
  }
}
```

**Requires environment variables:** `MCP_CONTEXT_CARD_ROOT`, `PORT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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:

```bash
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:

```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.

_Full upstream README: https://allmcps.com/mcp/mcp-context-card/readme_