Creatio Case Toolkit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREATIO_LOGIN | No | Forms-auth login (Mode 1) | |
| CREATIO_BPMCSRF | No | SSO session cookie BPMCSRF (Mode 2) | |
| CREATIO_MAX_TOP | No | Max rows per query (default 50) | 50 |
| CREATIO_ASPXAUTH | No | SSO session cookie .ASPXAUTH (Mode 2) | |
| CREATIO_BASE_URL | Yes | Your Creatio URL, e.g. https://<your-tenant>.creatio.com | |
| CREATIO_PASSWORD | No | Forms-auth password (Mode 1) | |
| CREATIO_BPMLOADER | No | SSO session cookie BPMLOADER (Mode 2) | |
| CREATIO_ALLOWED_ENTITIES | Yes | Comma-separated entity allowlist (e.g. Case,Activity,Contact,Account,SocialMessage) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| creatio_list_allowed_entitiesA | List the Creatio OData entity sets this server is permitted to read. If the allowlist is empty, all entities are readable. |
| creatio_query_recordsA | Query records from a Creatio entity via OData (read-only GET). Use OData syntax for filter/orderby, e.g. filter: "Number eq 'SR00042038'". |
| creatio_get_recordA | Fetch a single Creatio record by its GUID Id (read-only GET). |
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 3 tools
Each tool has a clearly distinct purpose: listing allowed entities, querying records, and fetching a single record. There is no overlap or ambiguity between them.
All tools follow the same verb_noun pattern with the consistent 'creatio_' prefix: list_allowed_entities, query_records, get_record. The naming is uniform and predictable.
With 3 tools, the set is within the typical well-scoped range. Each tool serves a necessary role in the read-only OData use case, with no redundant or missing infrastructure.
For a read-only OData server, the tool surface is complete: it covers entity discovery, record querying, and single-record retrieval. No obvious gaps exist for the stated purpose.