M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
R

Relaticle

Official
Open-source CRM your AI agents can write to via MCP
How to install ↓ Compare GitHub source repository ↗
Category
Collaboration #38 of 55
Stars
★ 1.8k Very popular
Transport
Streamable HTTP
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
AGPL-3.0
Last commit
49FMRS · D

Relaticle is a self-hosted open-source CRM whose standout feature is native MCP support with 37 MCP tools plus a REST API, enabling AI agents to read and write CRM data directly. It offers a customizable data model, multi-team isolation, a modern stack, and strong test coverage under AGPL-3.0, making it a good fit for development-oriented teams that value data sovereignty and AI integration.

Strongest · Maintenance 12/20 Weakest · Security and permissions 7/20

Reliability
8/20
Security and permissions
7/20
Maintenance
12/20
Documentation
11/20
Setup experience
11/20
Why each score
Reliability 8/20
Static review sees only the manifest and README; no runnable evidence is supplied - no committed CI workflow listing and no test sources covering the server's key paths. The README's '2,000+ automated tests' claim and the '37 MCP Tools' badge are self-reported and cannot be verified. The manifest uses an unresolved placeholder version (${VERSION}), which suggests the publish path relies on template substitution and may ship incomplete registration metadata; the description says 'deals' while the repository description says 'opportunity', an unresolved naming mismatch that makes declared-tool-to-behavior correspondence unverifiable. Only one remote (streamable-http) is declared, with no health check, timeout, rate-limit or error semantics, so failure diagnosability is unknown. Static calibration caps this at 12; deductions for absent execution evidence and the unresolved placeholder bring it to 8.
Security and permissions 7/20
Evidence is limited to README and manifest, both treated as untrusted. Positive signals: AGPL-3.0 open source, self-hosted emphasis with data staying on the user's server, README claims of 5-layer authorization, team isolation and per-field encryption, and an HTTPS remote at mcp.relaticle.com. However, no substantive security evidence is present: authentication method (OAuth/PAT/API key), token storage and rotation, per-tool permission granularity, and how multi-team boundaries are enforced are all undocumented; the manifest declares no required scopes or credentials and no confirmation flow for destructive actions such as bulk delete, export or outbound data flow. The placeholder version weakens provenance and supply-chain verifiability. Treating missing evidence as a deduction yields 7; no red line is evidenced, so it stays outside the 0-4 band.
Maintenance 12/20
Verifiable maintenance signals: a public GitHub repository, an explicit AGPL-3.0 license, 1628 stars, 30 open issues, not archived, plus README links to a public roadmap (GitHub Projects), Discussions, Discord and an issue tracker - indicating an actively operated project with feedback channels. Deductions: no release records, versioning policy or changelog evidence is provided, and the manifest still carries a ${VERSION} placeholder, indicating a publishing/versioning governance gap; no SECURITY.md or security-response policy is evidenced; the dependency-update cadence (Laravel 13, PHP 8.5, Filament 5) cannot be confirmed from static material. Read as 'active but with governance and versioning gaps', scored 12.
Documentation 11/20
Documentation has some layering: the README covers overview, requirements (PHP 8.5+, PostgreSQL 17+, Composer/Node, Redis), installation via composer app-install, development commands, a self-hosting pointer and an i18n override workflow, and links to the official docs and a dedicated MCP docs page; the manifest supplies title, description and the remote URL. Clear deductions: the 37-tool catalogue - purpose, parameters, return values, pagination and quotas - is absent from the supplied material; authentication and authorization flow, permission model details, rate limits, error codes, cost/pricing and troubleshooting are missing; a terminology mismatch (deals vs opportunity) invites misreading; install steps depend on external links not shown here. Usable but with hidden assumptions and troubleshooting gaps: 11.
Setup experience 11/20
Positives: a relatively short install path - clone then composer app-install - with runtime prerequisites listed, a single composer dev command to bring up server/queue/vite, and an external self-hosting guide pointer; client side needs only the streamable-http endpoint https://mcp.relaticle.com, though no auth configuration example is given. Deductions: no client config snippets for mainstream clients (Claude Desktop, Cursor, VS Code, etc.), no Docker or environment-variable steps, no PostgreSQL initialization, queue or Redis specifics, and all self-hosting detail is off-repo; the manifest's placeholder version also means self-builds need extra version injection. Assessed as 'works but manual and external-doc dependent'; with the static cap of 15 and these gaps, scored 11.

Static review · not runListed 2026-09-10

Read the FMRS scoring method →

Fit and risk

What it can accessChanges third-party account dataConnects to a database

Best for

  • Developer-led teams
  • AI-forward startups
  • SMBs wanting AI agent integration without vendor lock-in
  • Organizations needing self-hosted, data-sovereign CRM

Not for

  • Users who want a fully managed SaaS and do not want to run infrastructure
  • Environments that cannot meet PHP 8.5+ and PostgreSQL 17+ requirements
  • Users needing multi-language UI out of the box (the main repository ships English-only; a lang directory must be added)

Required permissions

  • Access to CRM data on the self-hosted server (companies, people, deals, tasks, notes, etc.)
  • Write operations on CRM records through the MCP server
  • Full CRUD and schema access through the REST API
  • Team-scoped data and workspace access under multi-team isolation

Risks and side effects

  • The MCP server can write to CRM data, so misconfiguration may cause unintended record changes or deletions
  • Exposed MCP endpoints (https://mcp.relaticle.com) require your own authentication and access controls
  • Self-hosting means patching, backups, and infrastructure maintenance are the deployer's responsibility
  • The AGPL-3.0 license imposes obligations for redistribution and network services

Setup

Before you start

Runtime：Hosted (no local runtime)

  1. Clone the repository: git clone https://github.com/Relaticle/relaticle.git
  2. Enter the directory and install: cd relaticle && composer app-install
  3. Ensure requirements are met: PHP 8.5+, PostgreSQL 17+, Composer 2, Node.js 22+; Redis is optional for queues in development.
  4. For self-hosting (Docker or manual), see the Self-Hosting Guide: https://relaticle.com/docs/self-hosting
  5. For MCP server setup and client integration, see: https://relaticle.com/docs/mcp

Check that it works

Connect the client to https://mcp.relaticle.com and confirm the 37 CRM tools appear in the tool list; then ask "list my companies" to prove the connection reads CRM data.

Troubleshooting

  1. Verify the environment meets PHP 8.5+, PostgreSQL 17+, Composer 2, and Node.js 22+
  2. Check MCP server connectivity and configuration via https://relaticle.com/docs/mcp
  3. If queued jobs fail, verify Redis availability (optional in development)
  4. Confirm team isolation and authorization are configured correctly to avoid tool call failures from insufficient permissions
  5. For upgrade or deployment issues, see the self-hosting guide at https://relaticle.com/docs/self-hosting

Things to try

Once connected, you can ask your AI assistant things like:

  • Create a new company called Acme and add a contact for it
  • List all deals in the negotiation stage of my pipeline
  • Add a note to the Acme deal and create a follow-up task
  • Analyze my pipeline this quarter and flag deals at risk

Use cases

Let AI agents query and update CRM records such as companies, people, deals, tasks, and notes
Perform full CRUD on self-hosted CRM data through MCP tools and the REST API
Analyze sales pipeline and activity history via agents
Provide a vendor-lock-in-free CRM for developer-led teams or AI-forward startups

Supported clients

Claude Desktop

Listed from the project's documentation, not tested by this site.

Overview

Relaticle is a self-hosted open-source CRM with a production-grade MCP server exposing 37 MCP tools, letting AI agents such as Claude, GPT, or open-source models perform CRM operations and analysis directly. Its data model supports 22 custom field types, including entity relationships, conditional visibility, and per-field encryption, with no migrations required. It offers multi-team isolation with 5-layer authorization, is built with Laravel 13, Filament 5, and PHP 8.5, includes 2,000+ automated tests, and is licensed under AGPL-3.0, keeping your data on your own server.

Similar servers

Compare with other MCP servers

Source revision 45d5fc07902e Data synced 2026-10-19 Read the FMRS scoring method