Do I need Claude Pro to use MCP?

Claude Desktop MCP support requires a current Claude desktop app. Check Anthropic's plan docs for your region — MCP availability has expanded but features evolve; verify in app settings under Connectors or MCP.

Is Claude Desktop better than Cursor for CRM MCP?

Different jobs. Claude Desktop suits quick summaries, mail drafts, and ad hoc research. Cursor suits builders editing code beside CRM tools. Many teams use both with separate named keys.

Where do I get a Salestrics MCP API key?

Organization Admin → MCP → Create key. Keys use the smcp_live_ prefix, are org-scoped, and appear in audit logs. See /mcp for the admin path and discovery URLs.

What should I ask Claude first?

A read-only pipeline summary — commit deals closing this month with missing next steps. Then explore mail and support read tools before enabling any write or send capability.

← Back to Salestrics Today

August 8, 2026 4 min read Salestrics Team

Connect Claude Desktop to Salestrics MCP (Step-by-Step) [2026]

Claude Desktop supports Model Context Protocol out of the box — a natural fit for founders who want pipeline and mail context without living in an IDE. This guide walks through org API key → config file → first read-only query on Salestrics MCP, plus troubleshooting and governance so the connection stays auditable. If you already use Cursor, the same key policy applies; only the config location changes.

Before you connect

Organization Admin access on Salestrics
Claude Desktop installed (latest stable)
Five minutes to paste config and restart
Read MCP governance — one named key for Claude, not shared

Platform status is Live; MCP expanded to 163 tools across CRM, mail, Resolve, Ledger, Workspace, and more. Tool names appear at connect time via discovery — do not hard-code a static list in Claude instructions.

Step 1: Create an org-scoped MCP key

Sign in to your organization as Admin
Open MCP settings (linked from salestrics.com/mcp and in-app Admin)
Create key — name it claude-desktop-[owner]-ro for read-first rollout
Copy the key once; store in a password manager — not Slack, not a screenshot
Note the MCP server URL shown in Admin (hosted endpoint for your org)

Keys are hashed at rest and revocable instantly. Rotate if the config file was committed to Git.

Step 2: Add Salestrics to Claude Desktop config

Claude Desktop reads MCP servers from a JSON config file. Location varies by OS — open Claude Desktop → Settings → Developer → Edit Config (or see Anthropic docs for the current path). Add a server block using the URL and headers from Admin setup snippets on /mcp.

Example shape (replace placeholders with your Admin values):

{
  "mcpServers": {
    "salestrics": {
      "url": "https://[YOUR_MCP_HOST]/mcp",
      "headers": {
        "Authorization": "Bearer smcp_live_[YOUR_KEY]"
      }
    }
  }
}

Save the file and restart Claude Desktop completely. A partial restart sometimes leaves MCP disconnected — quit the app and reopen.

Step 3: Verify connection

Open a new Claude conversation
Confirm the MCP connector icon shows Salestrics connected (wording varies by app version)
Ask: “List MCP tools available from Salestrics” — you should see categorized CRM, mail, and workspace tools
If empty, re-check URL, key prefix, and that the key was not revoked

Compare with CRM MCP overview if you expect tools that require a higher plan or Admin toggle.

Step 4: First read-only workflow

Using Salestrics MCP tools only, list open opportunities in Commit stage closing this month. Show amount, owner, close date, and next step. Flag any with blank next step or no activity in 14 days. Do not create, update, or send anything.

Validate numbers against Momentum before trusting automation in standup. Claude may summarize aggressively — spot-check one deal.

Step 5: Expand use cases gradually

Phase	Allowed tools	Example ask
Week 1	CRM search, read mail threads	Pipeline and inbound summaries
Week 2	Support case read, account context	Renewal risk with open tickets
Week 3+	Draft tasks or mail with human send	Follow-up draft after demo
Later	Write tools with explicit approval	Stage updates only after rep confirms

Copy vetted prompts from MCP workflow prompts.

Claude Desktop vs Cursor vs in-app Assistant

Surface	Best for	Avoid for
Claude Desktop	Quick research, mail drafts, founder ad hoc Q&A	Bulk CRM edits, production cron jobs
Cursor	Builders, custom scripts, code + CRM side by side	Non-technical rep daily workflow
Salestrics Assistant	Reps in-app — calls, mail, records	External automation outside the product

MCP-native CRM means all three attach to the same record graph — pick the surface for the job.

Troubleshooting

401 / unauthorized — key revoked, typo in Bearer header, or wrong org key
No tools listed — server URL must match Admin; restart Claude after config edit
Timeout — large mail searches; narrow date range in the prompt
Tool call failed — check Admin MCP audit log for rate limits; retry with smaller scope
Stale data suspicion — agents read live API; compare one field in CRM UI

For Cursor-specific paths, see Connect Cursor playbook.

Security habits

One key per person or use case — revoke on offboarding same day
Never commit claude_desktop_config.json with live keys to Git
Prefer read-only keys until write workflows are documented
Review Admin audit monthly — retire keys with no connections in 30 days