Log inSubmit server
Ictcrm MCP logo

Ictcrm MCP

Connects AI assistants to ICTCRM for reading contact groups and conditionally managing contacts and campaigns.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Ictcrm MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ictcrm-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ictcrm-mcp"
      ],
      "env": {
        "ICTCRM_BASE_URL": "YOUR_VALUE_HERE",
        "ICTCRM_USERNAME": "YOUR_VALUE_HERE",
        "ICTCRM_PASSWORD": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

ictcrm-mcp connects an MCP-compatible AI assistant to ICTCRM, which uses the ICTContact backend. It exposes contact-group lookup by default, while contact creation, deletion, and campaign attachment require an explicit write setting. The server communicates with ICTCRM's form-encoded RPC API using account credentials, with no separate token. Use it when an agent needs controlled CRM contact operations and group access.

Use cases

  • Read ICTCRM contact groups for agent-driven workflows
  • Create contacts in selected CRM groups
  • Delete contacts by known ID
  • Add new contacts to campaigns

Key features

  • Lists contact groups with IDs, names, and descriptions
  • Creates contacts in groups
  • Deletes contacts by ID
  • Attaches created contacts to campaigns
  • Keeps write tools disabled by default
  • Uses ICTCRM account credentials over its RPC API

Tools4

What Ictcrm MCP lets your agent do. Expand a tool for its parameters.

Self-reported~65 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · ictcrm-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads298Package downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed4Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Ictcrm MCP works

What ictcrm-mcp does

ictcrm-mcp exposes selected ICTCRM operations through the Model Context Protocol. Because ICTCRM runs on the ICTContact backend, requests use that platform's RPC interface rather than a separate ICTCRM-specific API surface.

The server always provides ictcrm_list_contact_groups, which returns contact-group IDs, names, and descriptions. It can also expose three write operations: creating a contact in a group, deleting a contact by ID, and creating a contact while attaching it to a campaign.

Individual contact listing is not available. The backend's contact-list method returns a server-side error, so the MCP toolset focuses on group lookup and contact management instead of contact search or browsing.

How it works

Requests are sent to {base}/rest/<Method> as form-encoded RPC calls. Each call includes the configured ICTCRM account username and password. Authentication therefore uses the account credentials directly; there is no separate token-provisioning step.

The server is read-only by default. ictcrm_list_contact_groups remains available without enabling writes, while the create, delete, and campaign tools are only registered when ICTCRM_MCP_ALLOW_WRITE=true. This provides a configuration-level safeguard against accidental contact changes.

Setup and configuration

Node.js 18 or newer is required. The package can be run without a local installation through npx -y ictcrm-mcp, or installed globally with npm install -g ictcrm-mcp.

Set these required variables before starting the server:

  • ICTCRM_BASE_URL: ICTCRM server address without the /rest suffix, such as https://your-ictcrm.
  • ICTCRM_USERNAME: API account username.
  • ICTCRM_PASSWORD: Password for the account.

Optional settings control write access and request behavior:

  • ICTCRM_MCP_ALLOW_WRITE: Set to true to expose contact-writing tools; defaults to false.
  • ICTCRM_TIMEOUT_MS: Per-request timeout in milliseconds; defaults to 30000.
  • ICTCRM_TLS_INSECURE: Set to true to bypass TLS certificate verification. This is intended for self-signed test servers.

For Claude Desktop, add an MCP server entry that runs npx with -y ictcrm-mcp, then provide the ICTCRM variables in the entry's env object. Leave write access unset or false when the assistant should only read contact groups.

Tools and capabilities

  • ictcrm_list_contact_groups reads available contact groups and returns each group's ID, name, and description.
  • ictcrm_create_contact creates a contact within a selected group and returns the new contact ID. It is available only with writes enabled.
  • ictcrm_delete_contact removes a contact by ID. It is available only with writes enabled.
  • ictcrm_add_contact_to_campaign creates a contact and associates it with a campaign. It is available only with writes enabled.

Limitations and notes

The toolset cannot list individual contacts because the underlying ICTContact method fails server-side. Contact creation and deletion are potentially destructive operations and remain disabled unless ICTCRM_MCP_ALLOW_WRITE=true is configured. TLS verification should only be bypassed for suitable self-signed test environments. The server uses the permissions and access available to the configured ICTCRM account.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ictcrm MCP

ictcrm-mcp is an MCP server that connects AI assistants to ICTCRM and its ICTContact backend. Its tools list contact groups, create contacts in groups, delete contacts by ID, and add contacts to campaigns. Write tools remain disabled unless explicitly enabled with an environment variable.

Run `npx -y ictcrm-mcp` to start it without a local installation, or install it globally with `npm install -g ictcrm-mcp`. Node.js 18 or newer is required.

Set `ICTCRM_BASE_URL`, `ICTCRM_USERNAME`, and `ICTCRM_PASSWORD` in the MCP client's environment configuration. The base URL must omit the `/rest` suffix, and authentication uses the configured account username and password.

Set `ICTCRM_MCP_ALLOW_WRITE=true` before starting the server. This exposes contact creation, deletion, and campaign-attachment tools; contact-group listing remains available without the setting.

No, ictcrm-mcp cannot list individual contacts through the available API. It can read contact groups and, when writes are enabled, create or delete contacts and add created contacts to campaigns.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIctcrm MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ictcrm-mcp?style=directory)](https://allmcps.com/mcp/ictcrm-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/ictcrm-mcp"><img src="https://allmcps.com/api/badge/ictcrm-mcp?style=directory" alt="Ictcrm MCP on AllMCPs" /></a>