Elvance is an open MCP connector, it works with any MCP-compatible AI client. Claude is the primary supported client, and the setup below is for Claude.
Run your Elvance PreSales workflow directly from Claude. The Elvance Connector lets you find, view and update opportunity scorecards, manage risks and feature gaps, log and review activities, and ask questions about your pipeline – all from a Claude conversation, acting only as you and strictly within your Salesforce permissions.
It’s opt-in and off by default, uses per-user Salesforce sign-in, and only ever touches Elvance data and fields. Never the rest of your Salesforce.
What you can do
Opportunities & scorecards
- Find an opportunity by name and pull up its scorecard
- Create the first scorecard for an opportunity (with your create-defaults seeded)
- Update any scorecard field – always saved as a new version
- List your opportunities with scores and last-updated dates
- Set the Elvance (Technical) stage, limited to your configured stages
Risks & feature gaps
- Add or update risks (impact, likelihood, resolve) and feature gaps (impact, status)
- Find and use items from your library instead of creating duplicates
- Auto-push feature gaps to Linear or JIRA where your org has it configured
Activities
- Log an activity using your org’s own Activity Types and Categories
- Review and complete flagged activities in one step
- See your activity for any period, with time-by-category totals
- Leaders can view the team, or a single rep
Ask Elvance
- Ask analytical questions about your pipeline (at-risk deals, blanks by stage, win trends), scoped to your own opportunities
What it can’t do
- It can’t reach the rest of your Salesforce – it is Elvance data and fields only
- It can’t exceed your permissions, or see others’ data (unless you’re a Leader where you will be able to return all Scorecards – the same as you can through the Elvance UI)
- It can’t change the sales Stage, only the Elvance Technical stage
- It can’t delete scorecards, risks or opportunities
- It can’t write a malformed scorecard. Invalid values are rejected, and every change follows Elvance’s own rules (versioning, required fields, your configured picklists)
Setting it up
For your Salesforce admin (one-time)
- Have Elvance installed, with an active licence for each person who will use the connector.
- Turn on MCP Access: Elvance admin settings → Elvance AI Intelligence → enable MCP Access. It is off by default; nothing works until you switch it on.
- Assign the permission set – give each user the Elvance MCP Access permission set.
For each user (in Claude)
- Go to Settings → Connectors (on claude.ai or Claude Desktop).
- Choose Add custom connector, name it Elvance, and paste the URL: https://mcp.elvance.app/mcp
- Click Connect, sign in to your Salesforce, and approve Elvance. You’re live.
Requirements: a Claude plan that supports custom connectors (Pro, Max, Team or Enterprise), an Elvance licence, and the two admin steps above. Sandbox users: your admin will point you at the sandbox login host.
Try these
- “Show me the scorecard for [opportunity name]”
- “Which of my opportunities haven’t been updated in a while?”
- “Add a risk to that deal: security review may slip the timeline”
- “Log a one-hour client demo on [account] from this afternoon”
- “What activities do I have flagged for review?”
- “Move the Elvance stage on [opportunity] to Solution”
Claude finds the deal, shows you the scorecard, and confirms before it changes anything.
Security & privacy
- Acts only as you. Every action uses your own Salesforce session, so it can never exceed your permissions.
- Elvance data only. It has no path to update the rest of your Salesforce.
- Opt-in, off by default. An admin enables it, and can disable it or revoke access at any time.
- Nothing stored. The connector keeps only short-lived sign-in tokens and no customer business data at rest.
- How it runs. The connector is an Elvance-operated service hosted on Cloudflare; Anthropic (Claude) is the AI. See our Privacy Policy for details on data handling and sub-processors.
Troubleshooting
- Can’t connect / sign-in fails – check that MCP Access is on and you have the Elvance MCP Access permission set, and that you’re on a plan that allows custom connectors.
- “That’s not a valid value” – expected: the connector validates against your org’s picklists. Ask “what are the valid options?” and it will list them.
- Can’t see a deal – you only see opportunities you own or are the Elvance Owner of (Leaders see more).
- Something’s missing – ask Claude to send it to Elvance as feedback; it reaches the team directly.
Support
Questions or issues? Contact support@elvance.io.