Metadata-Version: 2.4
Name: dirigent-mcp
Version: 0.28.0
Summary: An MCP server that lets an agent operate a dirigent instance through its API.
License-Expression: LicenseRef-Proprietary
License-File: LICENSE
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.13
Requires-Dist: dirigent-client==0.28.0
Requires-Dist: dirigent-common==0.28.0
Requires-Dist: mcp>=2.3.0
Requires-Dist: pyyaml>=6.0.3
Requires-Python: >=3.13
Description-Content-Type: text/markdown

# dirigent-mcp

An MCP server that lets an agent operate a dirigent instance through its API: write and apply
pipeline documents, start runs and read them, and pause or resume sources and schedules. Its
tools are calls the API already answers, so the agent may do what its token's role may do. No
tool is a delete, but `apply_document` retires what a document stops declaring: a source, with
its input journal and its token, and a schedule the document managed. `plan_document` lists them
under `sources.removed` and `triggers.schedules_removed` first. An agent that may apply and run a document runs it with every
connection the instance holds: give a `viewer` token and set `DG_MCP_READ_ONLY=1` when it should
only read.

```bash
claude mcp add dirigent -e DG_URL=https://dirigent.example.org -e DG_TOKEN=... -- uvx dirigent-mcp
```

Any MCP client starts it the same way: `uvx dirigent-mcp` over stdio, with `DG_URL` and
`DG_TOKEN` in its environment. See [Working with a coding agent](https://winterop-com.github.io/dirigent/agents/)
for the tools it offers.
