
marmelab/atomic-crm-mcp
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
An MCP (Model Context Protocol) server for Atomic CRM
Обзор
An MCP (Model Context Protocol) server for Atomic CRM. It enables an agent (e.g. ChatGPT, Claude, etc.) to read and write data to your Atomic CRM instance securely. - OAuth 2.1 authentication with Supabase - Adds a query tool for executing SQL against CRM database - Row Level Security (RLS) automatically enforced - ChatGPT - Claude.ai - Visual Studio Code - Claude Desktop - Claude Code - Cursor - Goose - Codex CLI - Gemini CLI - ~~Gemini Mobile~~ - ~~ChatGPT Desktop~~ - ~~ChatGPT Mobile~~ 1. Open the Supabase Dashboard - Go to https://supabase.com/dashboard and select your project (or create a new one) 2. Enable OAuth 2.1 Server - Go to → - Click on - Set the to /#/oauth/consent - Enable the option - and save changes 3.
README
Показан фрагмент оригинального README. Открыть оригинал.
Atomic CRM MCP Server
An MCP (Model Context Protocol) server for Atomic CRM. It enables an agent (e.g. ChatGPT, Claude, etc.) to read and write data to your Atomic CRM instance securely.
- OAuth 2.1 authentication with Supabase
- Adds a
querytool for executing SQL against CRM database - Row Level Security (RLS) automatically enforced
Supported MCP Clients
- ChatGPT
- Claude.ai
- Visual Studio Code
- Claude Desktop
- Claude Code
- Cursor
- Goose
- Codex CLI
- Gemini CLI
Gemini MobileChatGPT DesktopChatGPT Mobile
Installation
MCP Server Setup
-
Clone the repository:
git clone https://github.com/marmelab/atomic-crm-mcp cd your-repo -
Install dependencies:
npm install -
Add a config file
cp .env.example .env
Supabase Setup
-
Open the Supabase Dashboard
- Go to https://supabase.com/dashboard and select your project (or create a new one)
-
Enable OAuth 2.1 Server
- Go to Authentication → OAuth Server
- Click on Enable the Supabase OAuth Server
- Set the Authorization Path to
/#/oauth/consent - Enable the Allow Dynamic OAuth Apps option
- and save changes
-
Configure asymmetric JWT signing
- Go to Project Settings → JWT Keys
- On the JWT Signing Keys tab, if you see an invite to Start using JWT signing keys, this means you’re currently using Legacy JWT secret, so click on the Migrate JWT secret button
- If the current key is of type “Legacy HS256 (Shared Secret)”, click on the Rotate keys to use the new key of type “ECC (P256)” or similar
-
Get your Supabase URL
- Go to Project Settings → Data API
- Find your Project URL (e.g.,
https://mrubnlemopavyqvjjwmw.supabase.co) - Add it to your
.envfile asSUPABASE_URL
-
Get your database connection string
- Go to Project Settings → Database
- On the top app bar, click on the Connect button
- Copy the Direct Connection string (it will have
[YOUR-PASSWORD]placeholder) - Add it to your
.envfile asDATABASE_URL - Replace
[YOUR-PASSWORD]with your database password. If you don’t know it, go to Database → Settings and reset the password.
Local MCP Server
You can run the MCP server locally if you use a service like ngrok. You will need to choose a publicly accessible HTTPS URL for the MCP server, e.g., https://atomiccrmmcp.ngrok.dev. We’ll name this URL MCP_URL in the instructions below.
Run the server with the custom URL:
npm run dev -- --url=MCP_URL
Then, start ngrok in a separate terminal with the same URL:
Установка
This server does not publish a one-line install command.
Open the repository installation guide Новичок в MCP? Начните с руководства на mcpskill.org →