Salesforce MCP Server
This server provides AI-powered tools to interact with Salesforce, enabling natural-language querying, opportunity intelligence, pipeline analytics, and standard CRM operations.
Core Salesforce Operations
Execute SOQL queries: Run any SOQL query against your Salesforce org with pagination support
Describe objects: Get full metadata and field schemas for any Salesforce object, with optional intent-based filtering (pipeline, engagement, forecasting, etc.)
Search fields: Discover field API names by searching across labels, names, and help text
Create, update, delete records: Manage records in any Salesforce object, including custom fields
List objects: Browse all available standard and custom Salesforce objects
Get user info: Retrieve information about the currently authenticated user
Download files: Download files by ContentVersionId or ContentDocumentId
Batch operations: Execute multiple operations in a single call, with result chaining between steps
Opportunity Management
Search opportunities: Find opportunities by name, account, or stage with pagination
Get opportunity details: Retrieve full details of a specific opportunity with intent-based field selection
Opportunity Intelligence & Analytics
Analyze conversations: Analyze engagement patterns from calls, emails, and activities tied to an opportunity
Enrich opportunities: Add market intelligence, industry insights, and strategic recommendations
Find similar opportunities: Discover deals similar to a reference opportunity or matching specific criteria, with pattern analysis and similarity scoring
Opportunity insights: Generate pipeline health reports, stage conversion rates, owner performance metrics, and industry trends
Generate business case: Automatically produce a professional markdown business case report for an opportunity, pulling in contacts, conversation insights, and comparable won deals
Run analytics: Perform group-by and aggregation analytics on any Salesforce object with custom computed expressions
Provides tools for interacting with Salesforce, including opportunity intelligence, conversation analysis, business case generation, and standard CRUD operations, enabling AI agents to search, analyze, and manage Salesforce records.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Salesforce MCP Server Show me all opportunities over $100K in proposal stage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
đŠī¸ Salesforce MCP Server
This MCP (Model Context Protocol) server provides AI-powered tools for interacting with Salesforce, featuring opportunity intelligence, conversation analysis, business case generation, and standard CRUD operations. Built with pagination support and optimized response structures for AI workflows.
đ¯ What This Means for You
Imagine having a sales expert that instantly knows everything about your deals and can give you winning strategies. That's what this AI does with your Salesforce data.
đŦ Just Chat Naturally - No Technical Skills Needed
You say: "Show me all Microsoft deals over $100K in the proposal stage"
AI does: Searches your entire Salesforce database and returns matching opportunities
You say: "How's the engagement on the Acme deal? Are we talking to the right people?"
AI does: Analyzes all your calls, emails, and activities to give engagement insights
You say: "Find me deals similar to this opportunity that we won"
AI does: Scans your database for similar successful deals and success patterns
You say: "Create a business case document for this opportunity"
AI does: Generates a professional PDF ready for executives
đ Real Conversation Examples
Scenario: "I'm struggling with the Acme Corp deal. It's been stuck in negotiation for 2 months."
AI Response: "Let me analyze the Acme opportunity... I see limited engagement in the past 3 weeks. You've had 2 calls with procurement but haven't connected with the decision maker yet. Similar deals that got unstuck had executive sponsor engagement. I found 3 comparable deals where scheduling an executive briefing moved things forward. Here's a business case document you can use..."
Scenario: "My manager wants to know why our cloud migration deals are taking so long to close."
AI Response: "Analyzing your cloud migration opportunities... The average sales cycle is 40% longer than industry standard. The pattern shows deals stall in the technical evaluation stage. Successful cloud deals had solution architects engaged 2 weeks earlier on average. I recommend involving technical resources sooner..."
⨠What You Get
đ Smart Search: Find any opportunity with natural language
đŦ Engagement Analysis: Know who you're talking to and who you're missing
đ§ Strategic Insights: Get recommendations based on similar successful deals
đ Pipeline Intelligence: Understand your pipeline health and conversion patterns
đ Professional Documents: Generate business cases and executive summaries
đ Performance Analytics: See what's working and what needs attention
The Magic: You just chat naturally. The AI automatically connects to your Salesforce, analyzes millions of data points, finds patterns, and gives you actionable recommendations. It's like having a sales intelligence team, data analyst, and business consultant all rolled into one AI that knows your Salesforce inside and out.
đŦ Live Chat Example
đ¤ You | Can you look for any open salesforce opportunities where the solution engineer includes Aaron Rochelle? |
đ¤ AI Assistant | Let me help you search for Salesforce opportunities where Aaron Rochelle is involved as a Solution Engineer. I'll run a query in your Salesforce database to find opportunities matching that criteria...đ Found 3 opportunities:âĸ Cloud Migration - Acme Corp ($250K, Proposal)âĸ Digital Transformation - TechFlow ($180K, Qualification)âĸ Infrastructure Upgrade - GlobalTech ($320K, Negotiation) |
đ¤ You | Tell me more about the Acme Corp opportunity |
đ¤ AI Assistant | Here are the key details for the Acme Corp Cloud Migration opportunity:đŧ Opportunity Details:âĸ Account: Acme Corpâĸ Amount: $250,000âĸ Stage: Proposalâĸ Close Date: 2024-03-15âĸ Decision Maker: Sarah Johnson (IT Director)đ Intelligence Insights:âĸ Similar cloud deals average 45 days in proposal stageâĸ 73% win rate when executive sponsor engaged earlyâĸ Competitor: AWS (primary threat)âĸ Next action: Schedule technical deep-dive |
đ¤ You | What similar deals have we won? Show me the patterns |
đ¤ AI Assistant | I found 8 similar cloud migration deals you've won in the past 12 months. Here are the key patterns:đ¯ Success Patterns:âĸ Average deal size: $275K (vs $250K current)âĸ 67% had solution architect engaged by day 14âĸ 89% included a pilot/POC phaseâĸ Executive sponsors attended 78% of demosđ Recommendation: Schedule Aaron for a technical deep-dive with their DevOps team this week. Based on similar wins, proposing a 2-week pilot will increase close probability by 34%.đ Would you like me to generate a business case document for this opportunity? |
Related MCP server: Salesforce MCP Server
đ¤ What is MCP?
The Model Context Protocol (MCP) is a standardized way for AI models to interact with external tools and resources. MCP servers provide specific capabilities that can be used by AI models through a consistent interface. This Salesforce MCP server allows AI models to interact with Salesforce data and operations in a structured way.
đ Installation
npm (recommended)
# Run directly with npx
npx @aaronsb/salesforce-cloud-mcp
# Or install globally
npm install -g @aaronsb/salesforce-cloud-mcpFrom Source
git clone https://github.com/aaronsb/salesforce-cloud.git
cd salesforce-cloud
npm install
npm run build
node build/index.jsâī¸ Configuration
The server requires configuration in your Claude desktop app's configuration file. On Linux, this is located at ~/.config/Claude/claude_desktop_config.json. On macOS, it's at ~/Library/Application Support/Claude/claude_desktop_config.json.
Add the following configuration to the mcpServers object in your config file:
{
"mcpServers": {
"salesforce-cloud": {
"command": "node",
"args": ["/path/to/salesforce-cloud/build/index.js"],
"env": {
"SF_CLIENT_ID": "your_client_id",
"SF_CLIENT_SECRET": "your_client_secret",
"SF_USERNAME": "your_salesforce_username",
"SF_PASSWORD": "your_salesforce_password",
"SF_LOGIN_URL": "https://login.salesforce.com"
}
}
}
}Required Environment Variables
SF_CLIENT_ID: Your Salesforce OAuth client IDSF_CLIENT_SECRET: Your Salesforce OAuth client secretSF_USERNAME: Your Salesforce usernameSF_PASSWORD: Your Salesforce passwordSF_LOGIN_URL: Salesforce login URL (optional, defaults to https://login.salesforce.com)
To obtain these credentials:
Go to Setup in your Salesforce org
Navigate to App Manager
Create a new Connected App
Enable OAuth settings
Add necessary OAuth scopes
Save and wait for activation
Copy the generated Consumer Key (Client ID) and Consumer Secret (Client Secret)
đ¯ Working with Custom Fields
When constructing queries or working with Salesforce data, it's important to understand that many fields referenced may be custom fields specific to your Salesforce instance. Here's what you need to know:
Understanding Custom Fields
Custom fields in Salesforce end with
__cin their API namesWhat appears as "Implementation Status" in the UI might be stored as "Implementation_Status__c"
Custom fields can represent organization-specific business concepts
Best Practices
Object Metadata Analysis:
Use the
describe_objecttool withincludeFields: trueto examine both standard and custom fieldsLook for fields that match your intent in both standard and custom field lists
Map user-friendly field names to their actual API names
Field Type Consideration:
Custom fields can be various types (text, picklist, lookup, etc.)
Understanding field types helps construct appropriate queries
Custom fields might reference other custom objects through lookup relationships
Query Construction:
Build queries that can handle both standard and custom fields
Use field metadata to validate field existence before querying
Consider relationships between objects, especially with custom lookup fields
Example
If searching for "Project Status":
First, examine the object's fields to find the actual field name:
{
"objectName": "Opportunity",
"includeFields": true
}Look for fields like "Project_Status__c" or similar custom fields that match your intent
Use the discovered field name in your queries:
{
"query": "SELECT Id, Name, Project_Status__c FROM Opportunity"
}đ ī¸ Tools
Core Salesforce Operations
search_fields
Find the field(s) that carry a concept when you know what you want to query but not the API name. Searches the discovered field catalog (ADR-302) by keyword across field API names, labels, and help text, ranked by match strength.
{
term: string; // Required: matched against field name, label, help text
objectName?: string; // Optional: scope to one object (default: all core objects)
includeValues?: boolean; // Optional: return active picklist values for matches (default: false)
minPopulationPct?: number;// Optional: drop fields below this population density (0-100)
limit?: number; // Optional: max matches (default: 25, max: 100)
}Example:
{
"term": "ai",
"objectName": "Opportunity",
"includeValues": true
}The match is lexical, not semantic: it finds fields whose metadata contains the term, so a concept the schema names differently won't surface â read salesforce://field-catalog/{objectName}/all to browse everything.
execute_soql
Execute a SOQL query with pagination support.
{
query: string; // Required: SOQL query to execute
pageSize?: number; // Optional: Number of records per page (default: 25)
pageNumber?: number; // Optional: Page number to retrieve (default: 1)
}Example:
{
"query": "SELECT Id, Name FROM Account",
"pageSize": 10,
"pageNumber": 1
}describe_object
Get metadata about a Salesforce object with optional field information.
{
objectName: string; // Required: API name of the Salesforce object
includeFields?: boolean; // Optional: Whether to include field metadata (default: false)
pageSize?: number; // Optional: Number of fields per page (default: 50)
pageNumber?: number; // Optional: Page number to retrieve (default: 1)
}Example:
{
"objectName": "Account",
"includeFields": true
}create_record
Create a new record in Salesforce.
{
objectName: string; // Required: API name of the Salesforce object
data: Record<string, any>; // Required: Record data as key-value pairs
}Example:
{
"objectName": "Account",
"data": {
"Name": "Test Account",
"Industry": "Technology"
}
}update_record
Update an existing record in Salesforce.
{
objectName: string; // Required: API name of the Salesforce object
recordId: string; // Required: ID of the record to update
data: Record<string, any>; // Required: Record data to update
}Example:
{
"objectName": "Account",
"recordId": "001XXXXXXXXXXXXXXX",
"data": {
"Name": "Updated Account Name"
}
}delete_record
Delete a record from Salesforce.
{
objectName: string; // Required: API name of the Salesforce object
recordId: string; // Required: ID of the record to delete
}Example:
{
"objectName": "Account",
"recordId": "001XXXXXXXXXXXXXXX"
}get_user_info
Get information about the current user. No parameters required.
{}list_objects
List all available Salesforce objects with pagination support.
{
pageSize?: number; // Optional: Number of objects per page (default: 25)
pageNumber?: number; // Optional: Page number to retrieve (default: 1)
}Opportunity Management
search_opportunities
Search for Salesforce opportunities using flexible criteria and pattern matching.
{
namePattern?: string; // Optional: Pattern to match in Opportunity Name
accountNamePattern?: string; // Optional: Pattern to match in Account Name
stage?: string; // Optional: Exact match for opportunity stage
pageSize?: number; // Optional: Number of records per page (default: 25)
pageNumber?: number; // Optional: Page number to retrieve (default: 1)
}get_opportunity_details
Get detailed information about a specific opportunity including all available fields and related records.
{
opportunityId: string; // Required: The ID of the Salesforce opportunity
}đ§ Opportunity Intelligence
analyze_conversation
Analyze conversation activity and engagement patterns for an opportunity. Extracts insights from calls, emails, and other activities to provide engagement recommendations.
{
opportunityId: string; // Required: The ID of the Salesforce opportunity
}Example:
{
"opportunityId": "006XXXXXXXXXX"
}enrich_opportunity
Enrich an opportunity with market intelligence, industry insights, and strategic recommendations based on similar deal patterns and best practices.
{
opportunityId: string; // Required: The ID of the Salesforce opportunity
includeCompetitiveIntel?: boolean; // Optional: Include competitive analysis (default: false)
includeBestPractices?: boolean; // Optional: Include best practices (default: true)
}Example:
{
"opportunityId": "006XXXXXXXXXX",
"includeCompetitiveIntel": true,
"includeBestPractices": true
}find_similar_opportunities
Find opportunities similar to a reference opportunity or based on specific criteria. Includes pattern analysis and similarity scoring.
{
referenceOpportunityId?: string; // Optional: Reference opportunity for similarity matching
industry?: string; // Optional: Filter by industry
minAmount?: number; // Optional: Minimum opportunity amount
maxAmount?: number; // Optional: Maximum opportunity amount
stage?: string; // Optional: Filter by opportunity stage
isWon?: boolean; // Optional: Filter by won/lost status
closeDateStart?: string; // Optional: Start date (YYYY-MM-DD)
closeDateEnd?: string; // Optional: End date (YYYY-MM-DD)
includeAnalysis?: boolean; // Optional: Include pattern analysis (default: true)
limit?: number; // Optional: Max results (default: 50)
}Examples:
Find similar to a reference opportunity:
{
"referenceOpportunityId": "006XXXXXXXXXX",
"includeAnalysis": true
}Find by criteria:
{
"industry": "Information Technology & Services",
"minAmount": 100000,
"stage": "Closed Won",
"limit": 20
}opportunity_insights
Generate detailed insights and analytics from opportunity data including pipeline health, performance metrics, and trends.
{
timeframe?: string; // Optional: 'current_quarter', 'last_quarter', etc.
includeStageAnalysis?: boolean; // Optional: Stage distribution analysis (default: true)
includeOwnerPerformance?: boolean; // Optional: Owner performance metrics (default: true)
includeIndustryTrends?: boolean; // Optional: Industry trends (default: true)
includePipelineHealth?: boolean; // Optional: Pipeline health analysis (default: true)
includeConversionRates?: boolean; // Optional: Conversion rates (default: true)
minAmount?: number; // Optional: Minimum amount filter
maxAmount?: number; // Optional: Maximum amount filter
industry?: string; // Optional: Industry filter
owner?: string; // Optional: Owner filter
}Example:
{
"timeframe": "current_quarter",
"includeStageAnalysis": true,
"includeOwnerPerformance": true,
"minAmount": 50000
}generate_business_case
Generate a professional business case document for an opportunity. Returns step-by-step instructions for creating a formatted business case using TeXFlow.
{
opportunityId: string; // Required: The ID of the Salesforce opportunity
clientName?: string; // Optional: Client name for the document title
outputFormat?: string; // Optional: 'pdf', 'docx', or 'markdown' (default: 'pdf')
}Example:
{
"opportunityId": "006XXXXXXXXXX",
"clientName": "Acme Corporation",
"outputFormat": "pdf"
}đĻ Response Formats
Paginated Response
Operations that return multiple records use this format:
{
records: T[]; // Array of records for the current page
totalSize: number; // Total number of records
pageInfo: {
currentPage: number; // Current page number
totalPages: number; // Total number of pages
hasNextPage: boolean; // Whether there are more pages after this one
hasPreviousPage: boolean; // Whether there are pages before this one
}
}Error Handling
All tools return errors in a consistent format:
{
content: [{
type: "text",
text: "Error: [error message]"
}],
isError: true
}đģ Development
To run the server locally for development:
Set up your environment variables in a
.envfileBuild the project:
npm run buildStart the server:
node build/index.js⨠Key Features
đ§ AI-Powered Intelligence: Advanced opportunity analysis, conversation insights, and market intelligence
đ Pattern Recognition: Identify similar opportunities and success patterns in your pipeline
đ Business Case Generation: Automated creation of professional business case documents using TeXFlow
đ Smart Search: Flexible opportunity search with pattern matching and filtering
đ Pipeline Analytics: Detailed insights on pipeline health, conversion rates, and performance metrics
đ§ Standard Operations: Full CRUD operations with custom field support
đ Document Integration: Seamless integration with TeXFlow MCP server for document generation
⥠Optimized for AI: Response structures designed for AI model consumption
đ Future Possibilities
The Salesforce API offers numerous expansion opportunities:
Support for more Salesforce objects (Leads, Cases, Contacts, etc.)
Integration with Salesforce Flow and Process Builder
Enhanced competitive intelligence features
Bulk API operations for large datasets
Chatter API integration and social selling insights
Custom report and dashboard access
Advanced forecasting and predictive analytics
We'd love to hear your ideas about what would be most valuable to add next!
đ¤ Contributing
We welcome contributions from the community! Whether it's adding new features, improving documentation, or reporting bugs, your input helps make this project better for everyone. Feel free to submit a Pull Request or open an Issue to start a discussion.
đ License
This project is licensed under the MIT License - see the LICENSE file for details.
Available Tools
18 toolsanalyzeB
Run analytics on any Salesforce object â group by categorical fields, aggregate numeric fields, and compute custom expressions. Uses field-type metadata for validation.
Inputs: object (required), filter, compute, groupBy, +1 more.
analyze_conversationB
Analyze conversation activity and engagement patterns for an opportunity. Extracts insights from Gong calls, emails, and other activities to provide engagement recommendations.
Inputs: opportunityId (required).
batchA
Execute multiple operations in a single call with result references. Use $N.field to reference prior results (e.g., $0.id for the ID from operation 0). Destructive operations require confirm: true.
Inputs: operations (required), detail, onError.
create_recordB
Create a new record in Salesforce. Supports both standard and custom fields in the data object.
Inputs: data (required), objectName (required).
delete_recordB
Delete a record from Salesforce
Inputs: recordId (required), objectName (required).
describe_objectA
Get an object's full metadata, including every standard and custom field when includeFields is true. Returns the complete schema â exhaustive but unranked, and large on customised objects. To find out which fields this org actually populates, read salesforce://field-catalog/{objectName} instead; it is ranked and far smaller.
Inputs: objectName (required), intent, pageSize, pageNumber, +1 more.
download_fileA
Download a file from Salesforce. Accepts a ContentVersionId (068...) or ContentDocumentId (069...). Saves to a sandboxed workspace directory (default: ~/.local/share/salesforce-cloud-mcp/workspace/, configurable via SF_WORKSPACE_DIR). Text files (CSV, JSON, XML, TXT, etc.) also return content inline. Binary files return the saved path.
Inputs: contentId (required).
enrich_opportunityB
Enrich an opportunity with market intelligence, industry insights, and strategic recommendations based on similar deal patterns and best practices.
Inputs: opportunityId (required), includeBestPractices, includeCompetitiveIntel.
execute_soqlA
Execute a SOQL query. Supports both standard and custom fields (custom fields end with __c in their API names). To see which fields this org actually populates on an object, read the salesforce://field-catalog/{objectName} resource â it is ranked, far smaller than a full schema, and works for any object. That catalog is a usage filter rather than a field list: standard fields remain queryable whether or not they appear in it. Use describe_object when you want an object's complete schema.
Inputs: query (required), detail, pageSize, pageNumber.
find_similar_opportunitiesB
Find opportunities similar to a reference opportunity or based on specific criteria. Includes pattern analysis and similarity scoring to identify market trends and success patterns.
Inputs: isWon, limit, stage, industry, +6 more.
generate_business_caseA
Generate a markdown business case report for an opportunity. Fetches opportunity details, contacts, conversation insights, and similar won deals to produce a complete report.
Inputs: opportunityId (required), clientName.
get_opportunity_detailsA
Get detailed information about a Salesforce opportunity including all available fields (both standard and custom), related records, and metadata
Inputs: opportunityId (required), detail, fields, intent.
get_user_infoB
Get information about the current user
Inputs: no named parameters.
list_objectsB
List all available Salesforce objects, including both standard and custom objects
Inputs: pageSize, pageNumber.
opportunity_insightsC
Generate detailed insights and analytics from opportunity data including pipeline health, performance metrics, industry trends, and strategic recommendations.
Inputs: owner, industry, maxAmount, minAmount, +6 more.
search_fieldsA
Find the field(s) that carry a concept, when you know what you want to query but not the API name. Searches every scored field on the discovered objects â not just the promoted ones â across API names, labels, and help text, ranked by match strength. Searches the core objects by default; pass objectName to scope to one, which discovers it on demand. Set includeValues to get the value set for matched picklists, so you can write the WHERE clause without a second lookup. The match is lexical, not semantic: it finds fields whose name, label or help text contains the term, so a concept this org names differently will not surface, and an object that has not been discovered is not searched. Read salesforce://field-catalog/{objectName}/all to browse everything on an object.
Inputs: term (required), limit, objectName, includeValues, +1 more.
search_opportunitiesA
Search for Salesforce opportunities by name, account, and stage. Returns matching opportunities ordered by close date. Results include both standard and custom fields.
Inputs: stage, detail, pageSize, pageNumber, +2 more.
update_recordA
Update an existing record in Salesforce. Supports updating both standard and custom fields.
Inputs: data (required), recordId (required), objectName (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogâĻ
TDQS
Scored across 18 tools
The generic CRUD/query/metadata tools are distinct, but at least four opportunity-focused tools (opportunity_insights, enrich_opportunity, generate_business_case, analyze_conversation) all describe generating insights/recommendations from opportunity data with blurred boundaries. An agent could easily select the wrong one for a given request.
Most tools follow a clear verb_noun pattern (create_record, delete_record, search_opportunities, describe_object). Minor deviations like opportunity_insights, batch, and bare analyze keep it from being fully consistent.
18 tools is on the heavy side for a cohesive set, and several opportunity-insight tools could be consolidated. It is not excessive, but the surface feels padded rather than tightly scoped.
The set covers record create/update/delete, SOQL querying, object/field metadata, file download, batch operations, and a broad opportunity workflow. The main gap is a generic get_record/list_records tool, though execute_soql can work around it, and file upload is absent.
Maintenance
Related MCP Connectors
Plan Salesforce deploys, open pull requests and trigger pipelines from your AI client.
Connects your AI assistant to a living playbook distilled from your team's sales calls.
Ask about your deals, pace to target, and team odds from Stratyfix. Read only, real permissions.
CRM, inbox, meetings, revenue intelligence, analytics and automations for AI agents.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with Salesforce through a secure interface for performing CRUD operations, executing SOQL queries, and managing schema discovery. It features a smart learning system that analyzes custom objects and fields to provide intelligent assistance tailored to specific Salesforce configurations.1423 npm17BSD 2-Clause "Simplified"
- AlicenseAqualityCmaintenanceEnables interaction with Salesforce orgs to perform operations like querying data with SOQL, managing records, and executing Apex code. It provides configurable access levels and support for both standard and Tooling APIs via natural language interfaces.11MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA natural language interface for Salesforce data that allows users to query accounts, opportunities, contacts, leads, and activities through conversational prompts. It supports SOQL queries and provides tools for data retrieval and analysis without requiring technical Salesforce knowledge.48 npm-
- AlicenseBqualityDmaintenanceProvides AI agents with secure access to Salesforce data and operations, enabling natural language interaction with CRM for sales, marketing, and executive teams.65MIT