mcp-context-card
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_agents_mdA | 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_mdA | 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_sectionsA | List the headings in this project's AGENTS.md, so a client can pull one section instead of spending context on the whole file. |
| rememberA | 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. |
| recallA | Retrieve a fact stored in a previous session by id. Exact lookup — not fuzzy or substring. |
| forgetA | Remove a fact by id — to correct or drop something stale. A missing id is reported, not an error. |
| whoamiA | This server's own identity — name, vendor, version, status, license — from its .fafa card. |
| list_context_sourcesA | 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_cardA | Render the whole card — identity, AGENTS.md, memory, discovery — as one self-contained HTML page a person can read or screenshot. AGENTS.md sections collapse by default; pass expanded:true for the full render. Also served at GET /card (?expand=all) over the HTTP transport. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Card | This server's identity + the _meta context block. |
TDQS
Scored across 9 tools
Most tools are clearly separated by domain: fact memory, AGENTS.md, and context discovery/identity. A few pairs like recall vs read_agents_md and list_agents_md_sections vs list_context_sources could be momentarily confused, but their descriptions clarify distinct scopes.
Names are all lowercase snake_case and mostly follow a verb-object pattern, which is readable and predictable. The memory verbs remember/recall/forget drop the object, and whoami is a special case, creating minor but not confusing inconsistencies.
Nine tools is an appropriate size for this server's scope, covering fact memory, AGENTS.md operations, and context discovery without redundant helpers or bloat. Each tool earns its place.
The set covers the main workflows: fact create/read/delete, AGENTS.md read/section listing/drafting, and context discovery/identity. It lacks direct fact enumeration and a way to persist authored AGENTS.md, but render_context_card can surface memory and file writing may be intentionally outside the server's scope.