getLABSCO SUMMARY
Read-only mode is a real mode, not a suggestion.
With the write half enabled this server can create queues, rewrite schemas, install hooks and delete entities in a live document pipeline — so the fact that read-only removes those tools from the list entirely, rather than refusing them at call time, is the design decision that makes it deployable. The annotation workflow has an order that is easy to get wrong: start the annotation before patching fields, use the numeric datapoint id rather than the schema_id, and confirm afterwards.
What it is
A community MCP server for Rossum, the intelligent document processing platform. It goes well past reading extracted data: queues, schemas, engines, hooks and rules can all be created and changed through it, which turns organisation setup from a click-through into a conversation. A unified read layer means one get and one search cover every entity type instead of a tool per object. The public repository is archived while the project moves to a private GitLab for an overhaul.
What you get
- One typed accessor for every entity, by id or by filtered search, with batch retrieval skipping failed items rather than erroring the call —
get,search - The document lifecycle end to end: upload for AI extraction, fetch the extracted content to a local JSON file, move the annotation into review, patch field values, and confirm —
upload_document,get_annotation_content,start_annotation,bulk_update_annotation_fields,confirm_annotation - Annotations copied to another queue, optionally re-extracting in the target —
copy_annotations - Queues created from regional templates with a matching schema and optional engine, and their automation thresholds updated —
create_queue_from_template,update_queue - Schemas patched, viewed as a lightweight tree, and pruned of unused fields —
patch_schema,get_schema_tree_structure,prune_schema_fields - Extraction engines and their fields created and updated —
create_engine,update_engine,create_engine_field,get_engine_fields - Hooks and rules created from scratch or from templates, and tested before they go live —
create_hook,update_hook,create_hook_from_template,test_hook,create_rule - Anything deletable removed by id, in read-write mode only —
delete - Tool discovery and a mode check, so the agent can find out what it is allowed to do —
list_tool_categories,get_mcp_mode
Requirements
A Rossum API token in ROSSUM_API_TOKEN and your endpoint in ROSSUM_API_BASE_URL, for example https://api.elis.rossum.ai/v1 — both required. ROSSUM_MCP_MODE is the safety switch: read-write is the default, and read-only cuts the tool list to get, search, get_annotation_content, get_schema_tree_structure, get_engine_fields, list_tool_categories and get_mcp_mode, disabling every create, update, upload and delete. Switching modes means restarting the server. Run it with uvx rossum-mcp over stdio. This is a community integration built on the Rossum API, not an official Rossum product.
Setup effort
One command plus a key — uvx rossum-mcp, then supply credentials
USE CASES
01
Getting data out of a document you just received
Upload it for extraction, find the annotation it produced, and fetch the extracted content as a local JSON file.
02
Fixing what the extraction got wrong
Move the annotation into reviewing status, patch the field values, and confirm — in that order, because the update requires the reviewing state.
03
Setting up a new document type
Create the queue from a regional template so the schema and engine come with it, then patch the schema to the fields you actually need.
04
Adding business logic without deploying blind
Create the hook from a template and run the test tool against it before it starts firing on real documents.
05
Letting an assistant look but not touch
Start the server in read-only mode; the write tools are not in the list at all, so there is nothing to refuse.
30 tools
Listed in project docs. Your client may show a different list.
searchdeleteupload_documentget_annotation_contentstart_annotationbulk_update_annotation_fieldsconfirm_annotationcopy_annotationscreate_queue_from_templateupdate_queuepatch_schemaget_schema_tree_structureprune_schema_fieldscreate_engineupdate_enginecreate_engine_fieldget_engine_fieldscreate_hookupdate_hookcreate_hook_from_templatetest_hookcreate_rulepatch_rulecreate_workspacecreate_userupdate_usercreate_email_templatelist_tool_categoriesget_mcp_modeBEFORE YOU INSTALL
What to know first
Tools you get
30 tools named in the project's documentation.
Requires
- uvx on PATH
- ROSSUM_API_TOKEN in your environment
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"rossum": {
"command": "uvx",
"args": [
"rossum-mcp"
],
"env": {
"ROSSUM_API_TOKEN": "${ROSSUM_API_TOKEN}",
"ROSSUM_API_BASE_URL": "${ROSSUM_API_BASE_URL}",
"ROSSUM_MCP_MODE": "read-write"
}
}
}
}uvx
TERMINAL
uvx rossum-mcp
