Dossier logo

Dossier

Discover, verify, and execute signed, versioned .ds.md agent skills through MCP.

Install Dossier

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": {
    "dossier": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-dossier/cli"
      ]
    }
  }
}

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

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @ai-dossier/cli

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 14d ago.

Overview

The dossier MCP server exposes Dossier automation to AI clients, letting agents discover, verify, and execute signed, version-pinned agent skills. Dossiers are portable Markdown files that can live in GitHub, on a private server, or in the Dossier registry, with checksums and Ed25519 signatures for integrity and authorship verification. Use it when an agent needs repeatable workflows whose instructions can be validated before execution. The package runs through npx and supports MCP client configuration through a standard stdio command.

Use cases

  • Discover available workflow dossiers from an MCP client
  • Verify a skill before allowing an agent to run it
  • Execute a version-pinned project workflow
  • Share signed agent skills across machines and teams

Key features

  • Dossier discovery through MCP
  • Checksum and Ed25519 signature verification
  • Execution of signed .ds.md skills
  • Version-pinned agent workflows
  • Support for GitHub, hosted, and registry-based dossiers
  • Agent Skills and SKILL.md interoperability

Security & health

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

ActiveLast checked 3d ago

Recent health check succeeded.

21/21 checks healthy over the last 91d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @ai-dossier/cli (npm)

Adoption & maintenance

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

GitHub stars10Stargazers on the source repository.
npm downloads20kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Dossier works

What dossier MCP server does

dossier MCP server brings the Dossier skill format into MCP-enabled AI clients. It lets an agent find available dossiers, check a dossier’s integrity and authenticity, and run a selected workflow. Dossiers use .ds.md files with metadata, instructions, a version, and a signature. The format is designed for skills that can be shared across tools while preserving the same pinned content.

Dossier is intended for model-driven orchestration. The model reads a skill and decides which steps and tool calls are needed, while Dossier provides a deterministic layer around the run. This differs from a hand-coded workflow engine: the instructions guide the model inside the skill, and verification happens before the skill is executed.

How it works

A signed dossier combines its skill instructions with a checksum and Ed25519 signature. Verification checks that the content has not changed and confirms the signer associated with the dossier. Version pinning helps different users or machines install and run the same skill version.

Skills can be hosted in a GitHub repository, on another server, or through the Dossier registry. Their location does not change the verification model because the version and signature travel with the skill. Dossier also works as a layer over Agent Skills and SKILL.md: skills can be moved into and out of the format with the Dossier CLI.

Once the MCP server is configured, an agent can request available dossiers, verify one, and execute it without manually copying a dossier URL into the conversation. The server is distributed as @ai-dossier/mcp-server and can be launched with npx.

Setup and configuration

For Claude Code, register the server with:

Terminal
claude mcp add dossier --scope user -- npx @ai-dossier/mcp-server

A generic MCP client can use the same stdio command. The equivalent configuration uses npx as the command and passes -y and @ai-dossier/mcp-server as arguments:

config.json
{
  "mcpServers": {
    "dossier": {
      "command": "npx",
      "args": ["-y", "@ai-dossier/mcp-server"]
    }
  }
}

After setup, prompts such as “List available dossiers” or a request to run a named dossier can invoke the server’s capabilities. The repository also provides a Claude Code plugin installation path.

Tools and capabilities

  • Discover available dossiers for an agent to inspect.
  • Verify dossier checksums and signatures before execution.
  • Execute a selected dossier through the MCP connection.
  • Work with signed, versioned .ds.md skills.
  • Support dossiers hosted in Git repositories, other servers, or the Dossier registry.
  • Use the Dossier workflow alongside Agent Skills and SKILL.md files.

The signatures establish integrity and origin; they do not make a dossier safe by themselves or block prompt injection. The skill’s instructions still need appropriate review before use.

Reviews

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

Frequently Asked Questions about Dossier

dossier is an MCP server that connects AI clients to signed, versioned Dossier skills. Its main tools let agents discover available dossiers, verify checksums and Ed25519 signatures, and execute selected `.ds.md` workflows. It provides MCP access to portable skills hosted in GitHub repositories, other servers, or the Dossier registry.

Install it by registering `npx @ai-dossier/mcp-server` as an MCP server in your client. Claude Code supports `claude mcp add dossier --scope user -- npx @ai-dossier/mcp-server`; other clients can use a configuration with `npx` and the `-y @ai-dossier/mcp-server` arguments.

Yes, dossier is intended to work with Cursor and other MCP-capable clients. The server runs as a standard stdio process, so configure the client to launch `npx @ai-dossier/mcp-server` and then ask the agent to discover, verify, or execute dossiers.

Yes, dossier verifies a skill before execution using its checksum and Ed25519 signature. Verification checks that the dossier content was not changed and provides evidence of its signed origin; signatures do not guarantee that the skill is free from prompt injection or safe to run.

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 PreviewDossier AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/dossier?style=directory)](https://allmcps.com/mcp/dossier)
HTML Embed
<a href="https://allmcps.com/mcp/dossier"><img src="https://allmcps.com/api/badge/dossier?style=directory" alt="Dossier on AllMCPs" /></a>