Rossum MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROSSUM_API_KEY | Yes | Your Rossum API key | |
| ROSSUM_API_BASE | No | The base URL for the Rossum API | https://api.elis.rossum.ai/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rossum_get_queuesB | Get all queues from the Rossum organization. |
| rossum_get_schemaC | Get a specific schema by its ID. Args: schema_id: The ID of the schema to retrieve |
| rossum_get_hooksB | Get all serverless function hooks from the Rossum organization. |
| rossum_get_hookA | Get a specific serverless function hook by its ID, including its source code. Args: hook_id: The ID of the hook to retrieve |
| rossum_get_workspacesB | Get all workspaces from the Rossum organization. |
| rossum_get_workspaceC | Get a specific workspace by its ID. Args: workspace_id: The ID of the workspace to retrieve |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose targeting different Rossum resources: hooks, queues, schemas, and workspaces. The singular vs. plural naming (e.g., get_hook vs. get_hooks) further clarifies whether the tool retrieves a specific item or all items, eliminating any ambiguity.
All tool names follow a consistent 'rossum_get_' prefix with snake_case, followed by the resource name (e.g., hook, hooks, queues, schema, workspace, workspaces). This predictable pattern makes it easy to understand what each tool does at a glance.
With 6 tools, the count is reasonable for a Rossum API server, covering key resources like hooks, queues, schemas, and workspaces. It's slightly lean but functional; adding a few more tools (e.g., for creating or updating resources) could enhance completeness without being excessive.
The toolset is severely incomplete as it only provides read operations (get) for resources. There are no tools for creating, updating, or deleting hooks, queues, schemas, or workspaces, which are essential for full CRUD coverage in a document processing platform like Rossum. This will cause significant agent failures when trying to modify data.