Connect your AI Agents to Salesforce in minutes

Available tools
create_account
Create a new Salesforce account. Required: Name (must be unique). Use unique account names with timestamps to avoid duplicates.
get_account
Retrieve a Salesforce account by ID with complete details including standard and custom fields. Returns account information such as name, industry, revenue, employee count, addresses, and any custom fields. Use this to fetch full account details before updating or to verify account data. Supports selective field retrieval for performance optimization.
update_account
Update an existing Salesforce account with new information. Modify any account fields including name, industry, revenue, employee count, addresses, parent relationship, and custom fields. Only provide fields you want to change - unchanged fields remain as-is. Supports partial updates for efficient data management. Use when account information changes or to enrich account data.
delete_account
Permanently delete a Salesforce account from the system. This moves the account to the Recycle Bin where it can be restored within 15 days, after which it's permanently deleted. Use with extreme caution - deleting accounts removes all related contacts, opportunities, cases, and activities. This is a destructive operation that impacts multiple objects. Requires delete permissions on Account object.
list_accounts
List Salesforce accounts with automatic field access handling. Dynamically removes inaccessible fields and retries query.
search_accounts
Search Salesforce accounts using text queries across name, website, and phone fields. Automatically handles field access permissions by removing inaccessible fields and retrying. More powerful than list_accounts for finding specific accounts by keywords. Returns ranked results based on relevance.
create_event
Create a new Salesforce event. Required workflow: Call discover_required_fields('Event') first to identify mandatory fields and prevent creation errors.
get_event
Get a Salesforce event by ID
update_event
Update an existing Salesforce event
delete_event
Delete a Salesforce event
list_events
List Salesforce events
log_activity
Log a Salesforce activity

How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Salesforce MCP server
FAQs on using Merge's Salesforce MCP server
How can I use the Salesforce MCP server?
The use cases naturally depend on the agent you’ve built, but here are a few common ones:
- Automated opportunity creation: Your agent can automatically create Salesforce Opportunities when leads hit qualification thresholds
- Real-time opportunity updates: As sales reps talk to prospects, your agent can automatically update opportunity details, such as the deal amount, expected close date, and status
- Sales intelligence: Your agent can help sales leaders create custom reports on rep performance via CRM data. For example, a sales leader can ask for a quota attainment report, and the agent can use fields like sales reps’ names, historical quotas, and close-won revenues to create them
- Proposal writing: Your agent can generate personalized sales proposals by pulling data from the relevant CRM opportunity pages and by leveraging similar past proposals from other prospects
What are popular tools for Salesforce’s MCP server?
Here are some popular MCP tools broken down into categories:
Accounts:
- <code class="blog_inline-code">search_accounts</code>
- <code class="blog_inline-code">get_account</code>
- <code class="blog_inline-code">create_account</code>
- <code class="blog_inline-code">update_account</code>
- <code class="blog_inline-code">list_accounts</code>
Leads:
- <code class="blog_inline-code">search_leads</code>
- <code class="blog_inline-code">get_lead</code>
- <code class="blog_inline-code">create_lead</code>
- <code class="blog_inline-code">update_lead</code>
- <code class="blog_inline-code">delete_lead</code>
- <code class="blog_inline-code">list_leads</code>
Opportunities:
- <code class="blog_inline-code">search_opportunities</code>
- <code class="blog_inline-code">get_opportunity</code>
- <code class="blog_inline-code">create_opportunity</code>
- <code class="blog_inline-code">list_opportunities</code>
Cases:
- <code class="blog_inline-code">search_cases</code>
- <code class="blog_inline-code">get_case</code>
- <code class="blog_inline-code">create_case</code>
- <code class="blog_inline-code">update_case</code>
- <code class="blog_inline-code">list_cases</code>
What makes Merge Agent Handler’s Salesforce MCP server better than alternative Salesforce MCP servers?
Here are just a few reasons:
- Enterprise-grade security with DLP: Merge Agent Handler scans tool inputs and responses for sensitive data and applies configured rules to block, redact, or mask sensitive information. This protects Salesforce data handled by agents
- Real-time observability and a fully-searchable audit trail: Every tool call is logged, including underlying API requests, enabling debugging, monitoring, and compliance reviews. Logs are also fully-searchable, making it easy for your team to troubleshoot and resolve specific integration issues quickly
- Built-in authentication and credential lifecycle management: Agent Handler provides guided authentication flows, dynamic authorization, and secure credential handling without requiring custom auth code
- Connector Studio for customizing Salesforce tools: You can add, modify, or extend Salesforce connector functionality, which is especially useful when your agents need to work with and support custom Salesforce objects or workflows
How can I add the Salesforce MCP connector to Tool Packs in Merge Agent Handler?
To add the Salesforce connector to a Tool Pack in Merge Agent Handler:
1. Log into the Agent Handler dashboard.
2. Create or select a Tool Pack. Navigate to "Tool Packs" in the sidebar, and either create a new Tool Pack or select an existing one.
3. Add the Salesforce connector to your Tool Pack. Simply Click "Add Connector," select Salesforce from the available connectors, and configure the authentication type (Individual or Shared credentials).
4. Customize the connector (optional). Navigate to "Connectors" in the sidebar, and then select the Salesforce connector. From there, you can add new tools, modify existing tool descriptions, or adjust input schemas. You can also edit tool implementations for custom Salesforce actions.
5. Save your changes.The Salesforce connector and its tools should now be available in your Tool Pack.
Explore other MCP servers built and managed by Merge








Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
