● Online

1CRM MCP Server

Connects AI assistants (e.g. Claude) to 1CRM via the Model Context Protocol. This is an API endpoint for MCP clients — not an interactive web UI.

Central rollout: connector with 1CRM sign-in

The recommended route for organizations on the Team or Enterprise plan: an organization owner adds this server once as a custom connector. Every member then connects with a single click and signs in with their own 1CRM login (silently when SSO is in place) — no local installation, no password hand-outs. The connector is then available in Claude Desktop, on the web, on mobile and in Claude Code.

In Organization settings → Connectors → Add → Custom, enter https://visionday.mcp.1crm.de/mcp as the MCP server URL (character for character).
Under Advanced settings, add the OAuth client ID of the API client created in 1CRM; a client secret only if that client is not a public client.
Each member clicks Connect once under Customize → Connectors and approves the access in 1CRM.

Prerequisites on the 1CRM side: Professional or Enterprise edition with the API enabled, plus the CRM Entra ID extension, which turns the 1CRM instance into the authorization server. Every user only ever sees the data their own 1CRM user is allowed to see.

This server's discovery document: /.well-known/oauth-protected-resource/mcp

Single user: one-click extension for Claude Desktop

The easiest way for a single user without admin rights (or without a Team/Enterprise plan) — an extension that bundles everything it needs (including the Node runtime). No config-file editing, no Node/npx setup. Sign-in here uses a 1CRM username and password.

⬇ Download extension (.mcpb)

In Claude Desktop, install the downloaded .mcpb file under Settings → Extensions (if needed via the Advanced/Developer “Install from file” option).
Enter your 1CRM address, username and password in the form (optionally enable read-only).
Install — 1CRM shows up right away with its tools.

Your credentials stay local on your machine and only go to your 1CRM instance.

MCP endpoint

POST https://visionday.mcp.1crm.de/mcp

Authenticate with Authorization: Basic <base64(user:password)> using your own 1CRM login — or an OAuth2 Bearer token, which interactive clients obtain themselves through the connector sign-in. Server status: /health.

Active guardrails

Fixed instance: https://visionday.1crm.de

Available tools (10)

`list_modules`	List the available 1CRM modules.
`describe_model`	Show a module's fields, filters and links.
`list_records`	Search and filter records (field selection optional).
`get_record`	Read a record incl. related data.
`create_record`	Create a new record.
`update_record`	Update an existing record.
`delete_record`	Delete a record.
`list_related`	List a record's related records.
`link_records`	Link records together.
`unlink_records`	Remove a link again.

Set up a connection

The endpoint speaks MCP over Streamable HTTP and works with any compatible MCP client. Each user signs in with their own 1CRM login — the server stores no credentials.

Endpoint	`POST https://visionday.mcp.1crm.de/mcp`
Transport	Streamable HTTP (SSE)
`Authorization`	`Basic <base64(user:password)>` or `Bearer <token>` — required
`X-OneCRM-Base-Url`	your own 1CRM instance (optional, the server has a default)
Guardrail-Header	`X-OneCRM-Read-Only`, `X-OneCRM-Allow-Delete`, `X-OneCRM-Allowed-Modules` — optional, tightening only

Generate the Basic value: printf 'user:password' | base64.

Manual: stdio clients (e.g. Claude Desktop without the extension)

For Claude, the central connector or the extension is the recommended route. Other clients that only speak stdio connect through the mcp-remote bridge. Example entry (adjust the headers accordingly):

{
  "mcpServers": {
    "1crm": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://visionday.mcp.1crm.de/mcp",
        "--header",
        "Authorization:${ONECRM_AUTH}",
        "--header",
        "X-OneCRM-Base-Url: https://your-company.1crm.de"
      ],
      "env": {
        "ONECRM_AUTH": "Basic <BASE64_OF_USER:PASSWORD>"
      }
    }
  }
}