Azathoth MCP
Azathoth MCP serves promoted Azathoth workflows as Model Context Protocol tools, so an AI client such as Claude Desktop, an IDE or your own agent can call them.
Only the workflows an operator lists are offered, each as one tool with the name and description the operator wrote. Every call runs the workflow's active production revision as a recorded, idempotent invocation, and returns the invocation's ID with its result, so what an agent did can be traced to its runs and evidence.
It runs over stdio for a local client, or over Streamable HTTP for a team, as an OAuth 2.1 resource server in front of your organization's identity provider.
Serving Workflows Over MCP shows how to expose a workflow, connect Claude Desktop, and serve a team behind your identity provider.
Azathoth MCP is released with Azathoth, at the same version, and requires
the same minor release of azathoth-ai. The design is recorded in
ADR 0111.
License
MIT. See LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for azathoth-mcp 1.3.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 |
|---|---|---|---|---|
| azathoth_mcp-1.3.0.tar.gz | 27.9 kB | With provenance | Details for azathoth_mcp-1.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| azathoth_mcp-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for azathoth_mcp-1.3.0-py3-none-any.whl |
Total release size: 61.0 kB
Release files / azathoth_mcp-1.3.0.tar.gz
| Download URL | azathoth_mcp-1.3.0.tar.gz |
|---|---|
| Size | 27.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07126c2c539c1ac23a6a248c944d61ca1f731bd5fc374bdb892813508b58c455
|
|
BLAKE2b-256 checksum How to use checksums |
e0b9deeea55ecf0f77e9afec9b825b8027ccc97125e2c70bb01e92e72453f1ea
|
| 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 8, 2026.
Transparency logRelease files / azathoth_mcp-1.3.0-py3-none-any.whl
| Download URL | azathoth_mcp-1.3.0-py3-none-any.whl |
|---|---|
| Size | 33.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2349bf05bdb013f4712063924a94d6a310cfc63c34f2a948bc864609b2666812
|
|
BLAKE2b-256 checksum How to use checksums |
d3870b374325ef88feb3ea24fb9b1cf9b6af029881f823380fc948e3b47a072d
|
| 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 8, 2026.
Transparency logSecurity for azathoth-mcp 1.3.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
Both files in this release have been uploaded with provenance metadata.
Attestation for azathoth_mcp-1.3.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 8, 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.
