Dossier

MCP server for dossier automation standard - enables LLMs to discover, verify, and execute dossiers

Dossier is an MCP server published by ai.imboard that implements the dossier automation standard. It is available as the npm package @ai-dossier/mcp-server at version 1.0.4 and communicates over the stdio transport. The server is designed to let language models interact with dossiers as structured automation units: discovering what dossiers are available, verifying them before use, and executing them as part of an agent workflow. The dossier automation standard is the core concept here — dossiers are treated as discrete, composable automation artifacts that an LLM can reason about and act on, rather than free-form scripts or ad-hoc instructions. Because no tool definitions are currently exposed in the registry record, the specific operations the server surfaces to a calling agent are not documented at the catalogue level. Developers should consult the repository at github.com/imboard-ai/ai-dossier for current tool definitions, protocol details, and any configuration requirements. No environment variables are declared in the registry record. The server runs locally via stdio, so it fits into any MCP-compatible agent runtime that spawns a child process and communicates over standard streams. It does not require a network-accessible endpoint to operate.

Use cases

  • Integrating the dossier automation standard into an MCP-compatible LLM agent
  • Discovering available dossiers from within an agent workflow
  • Verifying a dossier's integrity or structure before execution
  • Executing a dossier as an automated task unit from an LLM agent
  • Embedding dossier-based automation into a local stdio MCP pipeline

When to use it

  • When building an agent that needs to work with the dossier automation standard
  • When the agent runtime supports stdio-based MCP servers
  • When automation tasks are already packaged as dossiers

When not to use it

  • When the agent runtime requires a network transport rather than stdio
  • When no dossiers exist in the target environment, as there is nothing to discover or execute
  • When specific tool-level API documentation is required before integration, since tools are not listed in the registry record