MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers
MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers. The dossier mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 13 defined tools rather than through you.
That's it. The LLM reads the dossier and follows its instructions — no tools needed.
The server ships on npm as @ai-dossier/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Everything the assistant can do here goes through one of these:
Multi-registry — Configure multiple registries (public, internal, mirrors) queried in parallelPer — registry credentials**: Each registry has isolated authentication — a compromised token cannot access other registriesProject — level config**: Add a .dossierrc.json to your project for team-shared registry settingsTrust — cryptographic signatures and checksums, verified before executionVersioning — semantic versions you can pin and upgrade deliberatelyDistribution — a registry that makes skills discoverable and installablePortability — any project, any workflow, any LLM — no vendor lock-inAdaptability — agents understand context and adjust behaviorValidation — NoneExample — Use CaseReference — Protocol · Specification · Schema · [JSONGuides — Authoring Guidelines · Dossier Guide · [CI/CDAmong the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Dossier's toolset — Multi-registry, Per, Project and 10 more — is a fair guide to whether it matches your workflow. It is maintained by ai.imboard; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Dossier's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Multi-registry | Configure multiple registries (public, internal, mirrors) queried in parallel |
| Per | registry credentials**: Each registry has isolated authentication — a compromised token cannot access other registries |
| Project | level config**: Add a .dossierrc.json to your project for team-shared registry settings |
| Trust | cryptographic signatures and checksums, verified before execution |
| Versioning | semantic versions you can pin and upgrade deliberately |
| Distribution | a registry that makes skills discoverable and installable |
| Portability | any project, any workflow, any LLM — no vendor lock-in |
| Adaptability | agents understand context and adjust behavior |
| Validation | None |
| Example | Use Case |
| Reference | [Protocol](docs/reference/protocol.md) · [Specification](docs/reference/specification.md) · [Schema](docs/reference/schema.md) · [JSON Schema](./dossier-schema.json) |
| Guides | [Authoring Guidelines](docs/guides/authoring-guidelines.md) · [Dossier Guide](docs/guides/dossier-guide.md) · [CI/CD Integration](docs/guides/ci-cd-integration.md) · [Execution Tracing](docs/guides/tracing.md) · [Adopter |
| Packages | [CLI](./cli/) · [MCP Server](./mcp-server/) · [Core Library](./packages/core/) · [Registry](./registry/) |
{
"mcpServers": {
"dossier": {
"command": "npx",
"args": ["-y", "@ai-dossier/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.