servicex-mcp
MCP Server for ServiceX, the IRIS-HEP
on-demand data-delivery service for ATLAS/CMS. Wraps the
servicex Python client as MCP tools.
Install
pip install servicex-mcp
Usage (stdio)
servicex-mcp serve --backend <name-from-your-.servicex-file>
See docs/plans/ for the design and implementation plan.
Available tools
| Tool | Does | Read/write |
|---|---|---|
servicex_list_datasets |
List datasets cached on this ServiceX instance | read-only |
servicex_get_dataset |
Get the full detail of one cached dataset by its dataset ID | read-only |
servicex_info |
Return the ServiceX server version and its advertised capabilities | read-only |
servicex_list_code_generators |
List the code generators deployed on this ServiceX instance | read-only |
servicex_list_transforms |
List transforms you have submitted, with status and completion counts | read-only |
servicex_get_transform_status |
Get the full status of one transform by its request ID | read-only |
servicex_submit_query |
Submit a new transform (query) request against a dataset | write |
servicex_cancel_transform |
Cancel a running transform by its request ID | destructive |
servicex_delete_transform |
Delete a transform record (and its cache entry) by request ID | destructive |
servicex_delete_dataset |
Delete a cached dataset record by its dataset ID | destructive |
The six read-only tools query the external ServiceX server
(read_only_hint=true, open_world_hint=true in their MCP tool annotations).
servicex_submit_query mutates ServiceX state but never deletes anything
(read_only_hint=false). The three destructive tools
(servicex_cancel_transform, servicex_delete_transform,
servicex_delete_dataset) act on real running/finished transforms and cached
dataset records and cannot be undone (read_only_hint=false,
destructive_hint=true). All four write/destructive tools are disabled when the
server is started with --read-only.
Release files for servicex-mcp 0.2.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 | |
|---|---|---|---|
| servicex_mcp-0.2.0.tar.gz | 179.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| servicex_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 224.1 kB
Release files / servicex_mcp-0.2.0.tar.gz
| Download URL | servicex_mcp-0.2.0.tar.gz |
|---|---|
| Size | 179.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ae99ceb0eed37a5d9955d2cbb85a3268e17a1c03a576c19a48b1120d17612e2
|
|
BLAKE2b-256 checksum How to use checksums |
feb58c4388b452e162ab336115d4bd723c925ff94fbdb02afb75c608294d4447
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logRelease files / servicex_mcp-0.2.0-py3-none-any.whl
| Download URL | servicex_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 45.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5cbe8c9e90ca55ff7a804bb7fea6332469492859889c08c04e3aa1bb67519396
|
|
BLAKE2b-256 checksum How to use checksums |
aed709727620c3c11399f4fe4929a49be468ba6df1472662228e420f12cdd6a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency log