ictcrm-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ICTCRM_BASE_URL | Yes | Server base URL, without the /rest suffix, e.g. https://your-ictcrm | |
| ICTCRM_PASSWORD | Yes | Password for that account | |
| ICTCRM_USERNAME | Yes | API account username | |
| ICTCRM_TIMEOUT_MS | No | Per-request timeout | 30000 |
| ICTCRM_TLS_INSECURE | No | Skip TLS verification — self-signed test servers only | false |
| ICTCRM_MCP_ALLOW_WRITE | No | Unlock the contact write tools (see Safety) | false |
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 |
|---|---|
| ictcrm_list_contact_groupsA | List the contact groups (contact lists) in the CRM, each with its id, name and description. Use a group id when creating a contact. |
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 1 tool
With only one tool exposed, there is no possibility of confusion or overlap between tools. The tool's purpose is clear and distinct as the sole entry point.
The single tool name follows a consistent prefix_verb_noun pattern (ictcrm_list_contact_groups), which is predictable and readable. There are no other tools to introduce inconsistent naming conventions.
A CRM server with only one tool is far too thin for its apparent scope. It only lists contact groups, leaving all other CRM operations unavailable, which feels like a token or stub rather than a functional server.
The tool surface is severely incomplete for a CRM server: there is no way to create, update, or delete contacts, manage contact groups beyond listing them, or perform any other CRM workflow. Agents using this server would hit dead ends immediately after retrieving a group list.