Best for
- Developer-led teams
- AI-forward startups
- SMBs wanting AI agent integration without vendor lock-in
- Organizations needing self-hosted, data-sovereign CRM
R
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.
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.
Setup
- Clone the repository: git clone https://github.com/Relaticle/relaticle.git
- Enter the directory and install: cd relaticle && composer app-install
- Ensure requirements are met: PHP 8.5+, PostgreSQL 17+, Composer 2, Node.js 22+; Redis is optional for queues in development.
- For self-hosting (Docker or manual), see the Self-Hosting Guide: https://relaticle.com/docs/self-hosting
- For MCP server setup and client integration, see: https://relaticle.com/docs/mcp
Fit and risk
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
Troubleshooting
- Verify the environment meets PHP 8.5+, PostgreSQL 17+, Composer 2, and Node.js 22+
- Check MCP server connectivity and configuration via https://relaticle.com/docs/mcp
- If queued jobs fail, verify Redis availability (optional in development)
- Confirm team isolation and authorization are configured correctly to avoid tool call failures from insufficient permissions
- For upgrade or deployment issues, see the self-hosting guide at https://relaticle.com/docs/self-hosting
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 DesktopFull support