Summary

Deletes have no undo.

The tools that matter most in daily use are the boring ones — batch upload a folder, check per-document progress, export finished annotations in the format your parser wants. The one thing to be careful about is stated plainly in the README: `delete_project`, `delete_document`, `delete_annotations` and `delete_curation` are irreversible in INCEpTION, so verify the IDs before an agent calls them, and prefer a project ZIP export as a backup first.

What it is

A wrapper around INCEpTION's AERO v1 REST API. It exposes corpus management as MCP tools and as a CLI: projects, documents, annotations and curation. Annotation itself stays with human annotators in the INCEpTION interface — this automates everything around it.

What you get

Project management — list, create, delete, full ZIP export and import, and per-document progress — `list_projects`, `create_project`, `delete_project`, `export_project_zip`, `import_project_zip`, `project_status`
Document handling including bulk work — `list_documents`, `upload_document`, `batch_upload` over a folder with a glob, `export_document_source`, `delete_document`
Annotations per user: list, export one document or a whole project, import, delete — `list_annotations`, `export_annotations`, `export_all_annotations`, `import_annotations`, `delete_annotations`
The curation layer separately — `export_curation`, `delete_curation`
13 export formats, including `ctsv3`, `xmi`, `conllu`, `conll2003`, `conll2012`, `text` and `jsoncas`
The same operations as terminal commands — `inception-cli batch-upload --project 1 --folder ./texts --glob "*.txt"` — for pipelines with no agent in them

Requirements

Python ≥ 3.10 and a running INCEpTION instance with the AERO v1 REST API enabled; the README notes it is tested with INCEpTION 33+. The API lives at `http://<host>:<port>/api/aero/v1` and authenticates with HTTP Basic using your INCEpTION credentials, supplied as `INCEPTION_URL`, `INCEPTION_USER` and `INCEPTION_PASSWORD` in the environment or a `.env`. Install with `uv sync` or `pip install -e .` from a clone; the documented client entry runs `uv run --directory /absolute/path/to/inception-mcp inception-mcp`.