Customermates

What the Customermates MCP server does

The Customermates MCP server exposes core CRM data to AI agents through the Model Context Protocol. Its documented scope includes contacts, organizations, deals, and tasks. This gives an agent a structured way to work with customer and sales records instead of relying on unstructured exports or manual copying.

Access is subject to the user's permissions. That matters for teams where agents should operate within existing CRM roles rather than receive unrestricted access to every record. The repository describes Customermates as a CRM for contacts, organizations, deals, services, and tasks, with APIs, webhooks, automation support, and MCP-based tooling.

How it works

The server works as part of the Customermates platform and provides native MCP access to CRM resources. An MCP-compatible AI client can use the exposed CRM tools in an agent workflow, while Customermates applies the permissions associated with the user making the request.

The available material does not document the MCP transport, endpoint format, authentication fields, or the exact tool names and argument schemas. Developers should consult the project documentation before implementing a client-specific configuration. The repository does provide a Claude connection guide as an entry point for connecting AI tooling.

Customermates supports two deployment models. The managed cloud version is operated by Customermates. Alternatively, the application can be deployed on your own infrastructure with Docker Compose and PostgreSQL, allowing the MCP integration to run alongside a self-hosted CRM installation.

Setup and configuration

For self-hosting, the repository documents a Docker Compose deployment rather than a separate MCP-only installation. The basic setup downloads docker-compose.yml and an environment template, requires Docker Compose v2, and starts the application with docker compose up -d. A public domain is optional for local use but is needed for a TLS setup.

Required application settings include BETTER_AUTH_SECRET, POSTGRES_PASSWORD, BASE_URL, RESEND_API_KEY, and RESEND_OPERATOR_EMAIL. The email settings support signup verification, password resets, and invitations. Google or Microsoft sign-in can be enabled with the corresponding optional OAuth variables.

After startup, Prisma applies migrations. If the application is placed behind a reverse proxy, the proxy should preserve the original Host header, and BASE_URL should use the public HTTPS address. These are application deployment requirements; the supplied material does not identify additional MCP-specific environment variables.

Tools and capabilities

The Customermates MCP server is documented as providing access to:

• Contacts
• Organizations
• Deals
• Tasks
• User-permission-aware CRM operations

Customermates also documents API access with OpenAPI, webhooks, n8n workflows, audit logging, role-based access control, and self-hosting. Those platform features may support broader integrations, but the provided material does not establish that each one is exposed as an MCP tool.

Limitations and notes

The repository does not list the complete MCP tool catalog, read/write behavior for each resource, pagination rules, or error responses. It also does not describe support for specific MCP clients beyond providing a Claude connection guide. Cursor, Windsurf, and other clients should be treated as unconfirmed until their configurations are documented.

The Community Edition is licensed under AGPL-3.0-only. The repository also contains source-available commercial software under the Customermates Commercial License, and some enterprise capabilities require a commercial agreement. Cloud and self-hosted editions do not have identical features: for example, the unified inbox and calendar sync are identified as cloud features, while self-hosting requires you to manage infrastructure, backups, and updates.