This article is for administrators rolling the Salesmotion connector out across a managed Claude deployment, and for the security teams who need to approve it.
For an individual connecting their own Claude account, use the five-minute quickstart instead. For the full tool reference, see MCP integration.
What you are deploying
The Salesmotion MCP server is a hosted service at mcp.salesmotion.io. There is nothing to
install, host, or run inside your network. Claude connects to it over HTTPS, authenticated with a
key you control.
Once connected, Claude can read your Salesmotion account intelligence: accounts, signals, contacts, company research, earnings calls, filings, and job postings, plus twelve guided sales workflows. Eighteen of the nineteen tools are read-only. The account card is interactive and requires approval the first time it renders.
Rollout in four steps
1. Create a workspace key. Rather than each person connecting with a personal key, an admin creates one key for the workspace. See MCP workspace keys for how these work and how access is scoped.
2. Get the connector approved. On Claude Enterprise plans, custom connectors typically require an administrator to enable them before users can add them. This is a Claude-side setting, and it is usually the step that takes longest, so start it early.
3. Add the connector at the workspace level. Configure it once with the workspace key so individual users do not each need to set it up or hold their own credentials.
4. Verify with a small group. Have two or three people confirm they can run a real query before announcing it. A good test is "show me [one of your accounts]", which exercises account lookup and the card together.
What your security team will ask
The questions that come up in review, with the answers.
What data leaves our environment? Queries you send to Claude, and the responses Salesmotion returns. Salesmotion returns your own account intelligence, the data already in your Salesmotion account. The connector does not read your CRM, email, files, or anything else on your network.
Is it read-only? Eighteen of nineteen tools are read-only. The account card renders an interactive view. There is also a feedback tool for reporting data issues. Nothing modifies your Salesmotion data destructively, and nothing writes to your other systems.
How is it authenticated? With a key you create and can revoke. Revoking it immediately ends access for everyone using it.
Where does it connect? Outbound HTTPS to mcp.salesmotion.io. No inbound connections to your
network, no VPN, no firewall exceptions for incoming traffic.
Can we limit who uses it? Yes, through your Claude workspace administration, which controls who can access the connector, and through Salesmotion seat management. See Managing users and seats.
Is our data used for AI training? Your signals and research remain private to your organization and are not shared or used for external AI training.
For a data processing agreement or security documentation, contact support@salesmotion.io.
Restricted network environments
Some organizations block outbound connections to services that have not been reviewed, and some prohibit external API connections from AI tools entirely.
If your environment blocks mcp.salesmotion.io, your network team needs to allow outbound HTTPS
to that host. This is a standard vendor allowlist entry.
If your organization does not permit AI assistants to connect to external services at all, the connector is not available to you, and that is a policy decision rather than a technical one. You still have two options: the Salesmotion web platform, which requires no connector, and the API for teams building their own integrations inside their own environment.
Driving adoption after rollout
Connecting the workspace is not the same as people using it. The pattern that works is giving people specific prompts rather than announcing a capability.
Three that consistently land:
- "Review my accounts and signals from the last 7 days. What should I action?"
- "Account plan for [account]"
- "Prep me for my meeting with [person] at [company]"
Reps do not need to learn tool names. Describing what they want is enough, and the twelve skills handle the sequencing. See Using Salesmotion skills in Claude for the full set.
Include these in your rollout message. A connector announced without example prompts typically sees a burst of curiosity and then very little use.
Frequently asked questions
Do users need their own Salesmotion seat?
Access follows your Salesmotion licensing. Discuss your rollout with us if you are unsure how your plan covers connector users.
What happens if we rotate the workspace key?
Everyone using it loses access until reconfigured with the new key. Plan rotations, and be aware that revoking is also the fastest way to cut off access in an incident.
Does it work with Copilot, ChatGPT, or Codex?
The server implements the Model Context Protocol and works with MCP-compatible clients. Setup differs per client. See MCP integration.
Users connected but Claude does not seem to see their accounts
Usually the key is scoped to a different organization than the accounts they expect, or the connector needs reconnecting after an update. Have one user disconnect and reconnect first.