aditum-mcp
An MCP server for Aditum, the industrial data platform. Your AI assistant (Claude, GitHub Copilot, Cursor, ...) can read your Aditum workspace:
| Tool | What it answers |
|---|---|
list_sources |
the data sources (OPC UA, MQTT, Modbus, PI, databases, ...) you can read |
source_health |
one source: online, data flowing, data rate |
list_pipelines |
your pipelines: source, destination, records received and inserted |
pipeline_runs |
a pipeline's latest runs, with errors |
list_incidents |
data-health incidents: stale data, failed runs, schema drift, offline extractors |
list_datasets |
tables and measurements, with their freshness |
query |
a governed read of one table or measurement |
Read only: nothing can be changed through it.
Set up
- In Aditum, open Settings > API tokens, create a token and tick Read only (a token that can make changes is refused). It is shown once.
- Add the server to your assistant, for example Claude Code:
claude mcp add aditum --env ADITUM_TOKEN=adp_... --env ADITUM_URL=https://app.aditumdata.com -- uvx aditum-mcp
or in a JSON config (Claude Desktop, VS Code, Cursor):
{
"mcpServers": {
"aditum": {
"command": "uvx",
"args": ["aditum-mcp"],
"env": { "ADITUM_TOKEN": "adp_...", "ADITUM_URL": "https://app.aditumdata.com" }
}
}
}
ADITUM_URL is your workspace's https:// address (a dedicated workspace has its own). The token works only there, is never sent over plain http (except to localhost) and never follows a redirect.
What your assistant sees
The token acts as you: your workspace, your role and access rules, your plan's read limits (a query counts
as query units). Aditum decides what each answer holds, by your organisation's AI data policy: by default
(metadata_only) names, types, counts and column statistics, never row values; with samples, at most 5
rows per answer. Passwords and keys are never included. Every answer is marked as data from your systems,
so a tag or asset name can't instruct the assistant.
Python 3.9+, no dependencies. An npm package with the same behaviour: npx aditum-mcp.
Metadata
Release files for aditum-mcp 0.1.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 |
|---|---|---|---|---|
| aditum_mcp-0.1.0.tar.gz | 11.0 kB | Without provenance | Details for aditum_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aditum_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for aditum_mcp-0.1.0-py3-none-any.whl |
Total release size: 22.4 kB
Release files / aditum_mcp-0.1.0.tar.gz
| Download URL | aditum_mcp-0.1.0.tar.gz |
|---|---|
| Size | 11.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05a018b9fcab52061b5864cd1a69e3e4a8af7304ca8a0cb92740d9183217cfd5
|
|
BLAKE2b-256 checksum How to use checksums |
65fe5e939f5e21eba45e5746c83df8adf1f21b5e1705369e557b102ce6bc3c41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / aditum_mcp-0.1.0-py3-none-any.whl
| Download URL | aditum_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da64ed2131b5edc2c00390ff02bc6f438112f314e5c2f20a3ab45800555ba61c
|
|
BLAKE2b-256 checksum How to use checksums |
679fc2b759f5661c1ac6c3e3e510ca033c734a1b6d2bf5afa38425229648aff9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for aditum-mcp 0.1.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.