Skip to main content
Glama
rehanhaider

MCP Suite CRM

by rehanhaider

MCP Suite CRM

An open-source CRM built for humans and AI agents to operate together. The web application and every MCP client use the same typed operation catalog, with role checks, scoped agent keys, approval gates for risky agent actions, and a shared audit trail.

Pre-release: the source is public; container images and a stable release are not published yet. See INSTALL.md for Docker Compose installation with published images and PRODUCTION.md for installation from source.

What is included

Path

Purpose

apps/web

Login, the authenticated CRM under /app/*, and the HTTP operation API

apps/mcp

MCP over stdio and HTTP

packages/core

Domain types, authorization policy, and operation catalog

packages/db

SQLite persistence, schema, authentication, and bootstrap

The CRM covers companies, people, leads, deals, activities, tasks, pipelines, tags, contact lists, custom fields, saved views, offerings, approvals, users, agents, and audit events. The public marketing site, signup, billing, and managed-hosting controls are deliberately not part of this repository.

Related MCP server: Overdrive MCP Server

Run from source

The supported development platform is 64-bit Linux. Install mise; the repository pins Node 22 and pnpm 10.

mise trust
mise exec -- make setup
mise exec -- make dev

Open http://localhost:2222. / redirects to /login. The first setup creates the SQLite database at data/mcpsuite.db and prints the initial owner credentials; change the password after signing in.

Run with Docker

See INSTALL.md for installation, version pinning, updates, and owner recovery.

docker compose pull
docker compose up -d

One container, one process on :2222: the web app, the operation API, the MCP endpoint for agents (POST /mcp) and GET /healthz. Persistent state lives in ./data. Compose runs the published mcpsuite/crm image, the latest stable release by default. To pin an exact release, put MCPSUITE_VERSION=X.Y.Z in a .env file next to docker-compose.yml, then run both commands again; they also update an unpinned install. See PRODUCTION.md for the standalone-MCP command override and reverse-proxy guidance.

Connect an agent

In the CRM, open Admin → Agents, create an agent client, and copy the key shown once. The UI provides a ready-to-paste configuration. The full transport, scope, and trust-profile guide is in docs/mcp.md.

Example for Claude Code:

claude mcp add --transport http mcpsuite-crm http://localhost:2222/mcp \
  --header "Authorization: Bearer mcpsuite_YOUR_KEY"

Development checks

mise exec -- make typecheck
mise exec -- make test
mise exec -- make build
mise exec -- make smoke

See AGENTS.md for the code architecture and conventions, PRODUCTION.md for the current self-hosting runbook, and CONTRIBUTING.md before opening a pull request.

License

AGPL-3.0-only. See LICENSE.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to securely access and manage CRM pipeline, relationships, tasks, notes, files, and deal context through authenticated Streamable HTTP/OAuth, inheriting the signed-in user's permissions and business-unit isolation.
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to manage omnichannel CRM data (WhatsApp, Instagram, Facebook) via the official API, including leads, deals, pipelines, activities, tags, products, conversations, lists, attachments, and notes.
    MIT
  • F
    license
    Not graded
    quality
    A
    maintenance
    Enables AI assistants to access and manage CRM data by creating contacts and companies, retrieving activities and conversations, and performing semantic search over previously retrieved information with built-in vector storage and caching.
    -