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.
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
for the tools it offers.
1 maintainer
Metadata
1 maintainer
Release files for dirigent-mcp 0.29.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dirigent_mcp-0.29.0.tar.gz | 6.4 kB | With provenance | Details for dirigent_mcp-0.29.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirigent_mcp-0.29.0-py3-none-any.whl | Python 3 | none | any | Details for dirigent_mcp-0.29.0-py3-none-any.whl |
Total release size: 14.1 kB
Release files / dirigent_mcp-0.29.0.tar.gz
| Download URL | dirigent_mcp-0.29.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7148dca80d8bb72a1291a851a5adbb5f2122f0dda1431f5497cba96d606e01b
|
|
BLAKE2b-256 checksum How to use checksums |
164d9ccd29d3147e971799348134991efa17f2a25a26bb46af8bab27bb94f913
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logRelease files / dirigent_mcp-0.29.0-py3-none-any.whl
| Download URL | dirigent_mcp-0.29.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0025efe46100f7e568e857d02b5e5483f2df2cf976896cf5dcf6a1a41cdb2801
|
|
BLAKE2b-256 checksum How to use checksums |
407452e3f6826e071ef3c5fe0c4f2025778913eba2669457241f7cfb6da6e754
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logSecurity for dirigent-mcp 0.29.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dirigent_mcp-0.29.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
