Sigma CRM MCP server

The CRM MCP server for Claude and every MCP client.

Sigma CRM exposes its full feature set through one MCP server. Connect Claude Code with an API key, or the Claude app as a custom connector, and work with records, signals, pipelines and sequences in plain language, under scoped permissions with an audit trail.

Connect Claude to Sigma CRMConnect in 3 steps

How it connects

From a prompt to a change in your CRM.

Claude sends a tool call to the MCP server. The server checks the key or connection, applies the scopes, records the call and runs the Sigma CRM tool. The result goes back to Claude, and every write is visible in Sigma CRM.

How Claude connects to Sigma CRMClaude Code or Claude Desktop sends a tool call to the Sigma CRM MCP server. The server checks the API key or connection, applies the scoped permissions and writes an audit log entry. It then runs the matching Sigma CRM tool on records, signals, pipelines or sequences, and the result flows back to Claude. tool callresult ClaudeCode or Desktop MCP serverAPI keyScoped accessAudit log Sigma CRMRecordsSignalsPipelinesSequences
Claude Code or Claude Desktop sends a tool call to the Sigma CRM MCP server. The server checks the API key or connection, applies the scoped permissions and writes an audit log entry. It then runs the matching Sigma CRM tool on records, signals, pipelines or sequences, and the result flows back to Claude.

Use cases

What teams do with an MCP server for their CRM.

Each use case shows the prompt, what happens in Sigma CRM with the real tool names, and the result. Writes that change many records or enroll contacts ask for confirmation first.

Sales and outreach

Draft a follow-up sequence from meeting notes

Read my notes from today's call with Acme and build a follow-up sequence for the two people who joined. Enroll them, but show me first.

What happens in Sigma CRM
notes_get reads the meeting note. sequences_create and sequence_steps_add build the sequence, which starts inactive and sends nothing. sequences_enroll asks for confirmation, skips addresses on the do-not-contact list and blocks contacts that already run in another sequence.
Result
A ready sequence with enrolled contacts that you review and activate in Sigma CRM.
See sequences driven by Claude

Turn an observer signal into outreach

Which accounts got a new funding signal from the observers this week? For the three with the highest score, draft a first message and save it on the account.

What happens in Sigma CRM
signals_feed lists the new signals. scores_top and scores_get rank the accounts with their score breakdown. Claude writes the drafts and saves each one with notes_create, linked to the account and the contact.
Result
Drafts on the right accounts, based on a real signal, ready for a person to review and send.
See signal-based outreach in a demo

Research

Research a target account and log the signals

Research acme.example. What do they do, and what changed in the last weeks? Log anything that looks like a buying signal.

What happens in Sigma CRM
resolve_subject finds the account by domain or creates it. Claude researches on its own model access and saves what it found with records_store_research. Each buying signal goes in through signals_create with a stable external ID, so a rerun never duplicates it.
Result
An account record with saved research and dated signals on its timeline, ranked by your signal score.
See account research in a demo

Find the warm path into an account

Who on our team knows people at acme.example best, and who should introduce us?

What happens in Sigma CRM
relationships_best_connectors ranks who knows the account best from email and calendar interactions. network_graph returns the neighbourhood of the account with its connections.
Result
A short list of teammates and contacts with the strongest relationship, and the path to ask for an introduction.
See relationship intelligence in a demo

Data hygiene

Import, dedupe and enrich a lead list

Import this CSV of event leads. Dedupe on email, show me what would change first, then enrich the new contacts.

What happens in Sigma CRM
records_import runs a dry run that previews the counts without writing. The real import asks for approval. contacts_merge folds remaining duplicates into the contact you keep, and enrichment_trigger enriches the new records.
Result
Clean new contacts linked to their companies, without duplicates, and a preview before anything was written.
See import and enrichment in a demo

Add the people who already email you

Who from acme.example has emailed us but is not a contact yet? Add them, but skip shared inboxes like support@.

What happens in Sigma CRM
organization_inbox_people_list lists the senders from the company domain that are not contacts, with shared role mailboxes marked. organization_inbox_people_add creates them, links them to the company and links their messages, after confirmation.
Result
Every real person from that company in the CRM, with their email history attached.
See inbox capture in a demo

Pipeline

Daily pipeline review with next steps

Review my open deals. Which ones have no recent activity or no next step? Suggest the next step for each.

What happens in Sigma CRM
deals_for_pipeline lists the live deals with their accounts. activities_list and tasks_board show recent activity and open tasks. Claude logs agreed next steps with activities_log or notes_create.
Result
A short review of deals at risk, with a proposed next step on each record.
See a pipeline review in a demo

Clean up stale deals

Find deals that have not moved for a long time and have no open task. Move the dead ones to Lost after I confirm.

What happens in Sigma CRM
deals_for_pipeline and activities_list find deals without movement. deals_move_stage moves a deal exactly like dragging it on the board: status and close date follow the stage, the move lands on the timeline and the team is notified of a lost deal.
Result
A pipeline that shows only live deals, with every change on the timeline.
See pipeline cleanup in a demo

Signals and observers

Run signal observers on your own Claude Code

Run my Sigma CRM observers and report what you find.

What happens in Sigma CRM
signal_observers_list returns the observers that are set to run externally, and observer_list_items the records each one watches. Claude Code runs them on its own model access and reports through signal_observer_runs_report.
Result
Signals in the same feed and on the same timelines as platform runs, without using platform AI credits for the model.
See observers on Claude Code

Check what you watch for

Which signal types do we track, and which accounts got signals of each type this month?

What happens in Sigma CRM
signal_definitions_list reads the signal catalogue. signals_feed and signals_for_subject return the signals per type and per account.
Result
A clear view of which signals arrive and which accounts they concern.
See signals in a demo

Reporting

Weekly pipeline summary

Summarise this week: deals that moved, won or lost, and the deals that need attention next week. Save it as a note.

What happens in Sigma CRM
pipelines_list and deals_for_pipeline read the pipelines and deals. activities_list shows the moves of the week. Claude writes the summary and saves it with notes_create.
Result
A weekly summary in Sigma CRM that the team can read and comment on.
See weekly reporting in a demo

Export a segment for a report

Which accounts match our ICP segment right now? Export them with their scores.

What happens in Sigma CRM
segments_evaluate returns the records that match the saved segment. scores_get adds the score breakdowns, and records_export returns CSV for the segment.
Result
A CSV of the matching accounts, built from a saved segment instead of a manual filter.
See segments and export in a demo

Want us to connect it with you and run the first use cases?

Connect Claude to Sigma CRMSee pricing and licenses

Setup

Connect in 3 steps.

  1. Get your endpoint and a key

    Your MCP endpoint is your Sigma CRM address followed by /api/mcp. A workspace admin creates an API key under Settings, API keys, and picks its scopes: read, or read and write. The key is shown once and belongs to one workspace.

    https://YOUR-SIGMA-CRM-DOMAIN/api/mcp

  2. Connect Claude Code

    Add the server with one command. The key dialog in Sigma CRM also offers this command ready to copy.

    claude mcp add sigma-crm --transport http https://YOUR-SIGMA-CRM-DOMAIN/api/mcp \
  --header "Authorization: Bearer sigma_sk_..."

  3. Or connect the Claude app

    In Claude Desktop or claude.ai, open Settings, Connectors, choose Add custom connector, name it Sigma CRM and paste the endpoint address. Sigma CRM opens, an admin picks the workspace and the scopes and presses Allow. No key is pasted. The endpoint must be reachable over https.

Tools

MCP tool groups.

The registry has more than 130 tools. The same registry backs the interface, the REST API and the built-in agent Sammy, so the MCP server never falls behind the product. These are the main groups with examples.

Records

Read, create, update, archive and restore records of every type, with custom fields.

records_list, records_get, records_create, records_update, records_upsert, records_archive, records_restore, resolve_subject

Lists, segments and tags

Static lists with their own columns, saved segments and workspace tags.

lists_create, lists_members, list_members_add, list_fields_create, segments_create, segments_evaluate, tags_attach

Signals and observers

The signal catalogue, writing signals and running observers from outside.

signal_definitions_list, signals_create, signals_feed, signals_for_subject, signal_observers_list, observer_list_items, signal_observer_runs_report

Pipelines and deals

Pipelines with stages, moving deals and the people on a deal.

pipelines_list, stage_templates_list, deals_for_pipeline, deals_move_stage, deal_contacts_add, deal_contacts_update_role

Outreach and sequences

Campaigns, sequences, enrollment and the do-not-contact list.

campaigns_create, sequences_create, sequence_steps_add, sequences_enroll, sequence_enrollments_set_status, suppressions_add

Intelligence

Scores with breakdowns, enrichment and relationship intelligence.

scores_get, scores_top, enrichment_trigger, relationships_best_connectors, network_graph

Notes, tasks and timeline

Notes linked to many records, comments with mentions, tasks and activities.

notes_create, notes_link, comments_create, tasks_board, activities_list, activities_log

Import, export and hygiene

CSV import with dry run and dedupe key, export, merge and bulk archive.

records_import, import_rollback, records_export, contacts_merge, records_bulk_archive, organization_inbox_people_add

Workspace configuration

Workflows, score formulas, signal definitions and observers. Admins only, API keys are refused.

workflows_create, score_definitions_update, signal_definitions_create, observers_create, workspace_flavor_get

Security

Scoped keys, approvals and an audit trail.

An MCP server for a CRM touches customer data. Sigma CRM keeps every caller inside clear limits.

  • API keys belong to one workspace, with read or read and write scopes
  • Keys reach shared lists and segments only, never personal ones
  • Claude app connections need a workspace admin and can be disconnected at once
  • Bulk changes, merges, imports and enrollments ask for confirmation
  • Every write is tagged as UI, MCP, agent or observer
  • Per-key rate limits, and provider keys are never exposed to MCP clients
  • Workspace configuration tools are admin-only and refused for API keys

Explore Sigma CRM

Features

Custom fields, a flexible data model, views, workflows and roles.

Features

AI & MCP

How AI works in Sigma CRM: agents, observers, Sammy and model choice.

AI & MCP

Deployment

Run it on your own servers or in our cloud.

Deployment

Pricing

Cloud subscription or Enterprise perpetual license.

Pricing

Guides

MCP servers, Claude, AI sales agents, implementation, migration and cost.

Guides

Related pages

Frequently asked questions

What is a CRM MCP server?

A CRM MCP server exposes CRM functions through the Model Context Protocol, so AI clients such as Claude can read and change CRM data with defined tools. Sigma CRM offers its full feature set this way.

Which MCP clients work with Sigma CRM?

Claude Code connects with an API key. Claude Desktop and claude.ai connect as a custom connector with a sign-in. Other MCP clients that support Streamable HTTP and a bearer token can connect with an API key.

What is the MCP endpoint URL?

It is your Sigma CRM address followed by /api/mcp. For on-premise installations it is your own domain.

Can Claude delete or change data without asking?

Bulk changes, merges, imports and enrollments ask for confirmation first. Every write is tagged with its source and shows up in the history.

Does the MCP server work on-premise?

Yes. It is part of Sigma CRM in the cloud and on-premise. The Claude app needs to reach the endpoint over https; Claude Code needs network access to it.

Does using the MCP server cost extra?

Model usage in Claude is billed by your model provider. Sigma CRM licensing is on the pricing page.

Connect your Claude to Sigma CRM.

We set up the MCP server with you and walk through the use cases on your own pipeline.

Connect Claude to Sigma CRMSee pricing and licenses