# How to integrate Salesforce service cloud MCP with Vercel AI SDK v6 ```json { "title": "How to integrate Salesforce service cloud MCP with Vercel AI SDK v6", "toolkit": "Salesforce service cloud", "toolkit_slug": "salesforce_service_cloud", "framework": "Vercel AI SDK", "framework_slug": "ai-sdk", "url": "https://composio.dev/toolkits/salesforce_service_cloud/framework/ai-sdk", "markdown_url": "https://composio.dev/toolkits/salesforce_service_cloud/framework/ai-sdk.md", "updated_at": "2026-05-12T10:24:36.668Z" } ``` ## Introduction This guide walks you through connecting Salesforce service cloud to Vercel AI SDK v6 using the Composio tool router. By the end, you'll have a working Salesforce service cloud agent that can list all open support cases for today, update case status to resolved for customer, fetch recent customer interactions for an account through natural language commands. This guide will help you understand how to give your Vercel AI SDK agent real control over a Salesforce service cloud account through Composio's Salesforce service cloud MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Salesforce service cloud with - [ChatGPT](https://composio.dev/toolkits/salesforce_service_cloud/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/salesforce_service_cloud/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/salesforce_service_cloud/framework/codex) - [Cursor](https://composio.dev/toolkits/salesforce_service_cloud/framework/cursor) - [VS Code](https://composio.dev/toolkits/salesforce_service_cloud/framework/vscode) - [OpenCode](https://composio.dev/toolkits/salesforce_service_cloud/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/salesforce_service_cloud/framework/openclaw) - [Hermes](https://composio.dev/toolkits/salesforce_service_cloud/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/salesforce_service_cloud/framework/cli) - [Google ADK](https://composio.dev/toolkits/salesforce_service_cloud/framework/google-adk) - [LangChain](https://composio.dev/toolkits/salesforce_service_cloud/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/salesforce_service_cloud/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/salesforce_service_cloud/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/salesforce_service_cloud/framework/crew-ai) ## TL;DR Here's what you'll learn: - How to set up and configure a Vercel AI SDK agent with Salesforce service cloud integration - Using Composio's Tool Router to dynamically load and access Salesforce service cloud tools - Creating an MCP client connection using HTTP transport - Building an interactive CLI chat interface with conversation history management - Handling tool calls and results within the Vercel AI SDK framework ## What is Vercel AI SDK? The Vercel AI SDK is a TypeScript library for building AI-powered applications. It provides tools for creating agents that can use external services and maintain conversation state. Key features include: - streamText: Core function for streaming responses with real-time tool support - MCP Client: Built-in support for Model Context Protocol via @ai-sdk/mcp - Step Counting: Control multi-step tool execution with stopWhen: stepCountIs() - OpenAI Provider: Native integration with OpenAI models ## What is the Salesforce service cloud MCP server, and what's possible with it? The Salesforce service cloud MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Salesforce Service Cloud account. It provides structured and secure access to your customer service data, so your agent can perform actions like managing cases, retrieving knowledge articles, automating service processes, and tracking customer interactions on your behalf. - Case management and triage: Empower your agent to create, update, assign, or close customer service cases, ensuring timely resolution of inquiries and incidents. - Knowledge base retrieval: Let your agent search, read, and recommend relevant knowledge articles to assist with customer support and internal troubleshooting. - Customer interaction tracking: Have your agent log new interactions, fetch historical communication, and surface recent touchpoints for a full view of customer engagement. - Omnichannel support automation: Enable your agent to route cases, escalate issues, and manage service requests across chat, email, phone, and social channels all from one place. - Service workflow automation: Direct your agent to trigger macros, update case statuses, or launch automated actions to streamline repetitive tasks and boost support team productivity. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `SALESFORCE_SERVICE_CLOUD_CHASITOR_SNEAK_PEEK` | Chasitor Sneak Peek | Send real-time typing indicator (sneak peek) to Live Agent during active chat session. Allows agents to see what visitors are typing before the message is sent. Requires an active Live Agent chat session with valid session_key and affinity token. The sequence number must increment with each request. | | `SALESFORCE_SERVICE_CLOUD_COMPOSITE_BATCH` | Composite Batch | Tool to execute multiple independent REST subrequests in one batch call. Use when bundling up to 25 independent operations to minimize round trips. Subrequests cannot reference each other. | | `SALESFORCE_SERVICE_CLOUD_COMPOSITE_REQUEST` | Composite Request | Execute up to 25 dependent Salesforce REST subrequests in a single API call. Subrequests execute sequentially and can reference results from earlier requests using '@{referenceId.field}' syntax. Use this when operations depend on each other (e.g., create Account then create related Contact). For independent operations, use Composite Batch instead. | | `SALESFORCE_SERVICE_CLOUD_COMPOSITE_SOBJECT_TREE` | Composite SObject Tree | Create one or more nested sObject record trees in a single API call. Supports parent-child relationships up to 5 levels deep, with a maximum of 200 total records across all trees. Use this for bulk insertion of related records (e.g., Account with Contacts, or Orders with Line Items). Relationships must be Master-Detail or Lookup. Only supports INSERT operations, not upserts. | | `SALESFORCE_SERVICE_CLOUD_CREATE_CASE_RECORD` | Create Case Record | Tool to create or upsert a Salesforce Case record. Use when you need to add a new Case or update via external ID. | | `SALESFORCE_SERVICE_CLOUD_DELETE_CASE_RECORD` | Delete Case Record | Tool to delete a Salesforce Case record. Use when you need to remove a case by its record ID. | | `SALESFORCE_SERVICE_CLOUD_DESCRIBE_S_OBJECT` | Describe SObject | Tool to retrieve metadata of any sObject. Use when you need to inspect field definitions, relationships, and supported features for objects like Account, Contact, Case, etc. | | `SALESFORCE_SERVICE_CLOUD_GENERATE_REQUEST_ID` | Generate Request ID | Generate a UUIDv4 string to use as an Idempotency-Key header in Salesforce User Interface API requests. This prevents duplicate record creation when POST, PATCH, or DELETE requests are retried due to network failures or timeouts. The same key returns cached responses for 30 days, avoiding duplicate operations and saving server resources. Use this tool whenever you need to ensure idempotent behavior for Salesforce UI API operations. | | `SALESFORCE_SERVICE_CLOUD_GENERATE_SIGNED_JWT_ASSERTION` | Generate Signed JWT Assertion | Tool to generate a signed JWT assertion for Salesforce JWT bearer OAuth flow. Use when you need to perform server-to-server authentication using a connected app’s certificate. Use before exchanging the assertion for an access token. | | `SALESFORCE_SERVICE_CLOUD_GET_CASE_RECORD` | Get Case Record | Retrieve a Salesforce Case record by its ID. Returns Case details including status, priority, subject, description, owner, and timestamps. Useful for: - Looking up Case details by ID - Checking Case status and priority - Getting customer issue information - Retrieving Case metadata and relationships Requires a valid 15 or 18-character Salesforce Case ID. Optionally specify which fields to retrieve using the fields parameter; otherwise all accessible fields are returned. | | `SALESFORCE_SERVICE_CLOUD_GET_CHAT_MESSAGES` | Get Chat Messages | Tool to long-poll for chat messages/events. Use after CreateChatSession to retrieve incoming chat events. Returns empty messages list when no new messages (HTTP 204). Call with ack from prior response to maintain sequence. | | `SALESFORCE_SERVICE_CLOUD_GET_LIVE_AGENT_API_VERSION` | Get Live Agent API Version | Tool to retrieve current Live Agent API version. Use when initializing chat sessions to ensure subsequent calls target the correct REST API version. | | `SALESFORCE_SERVICE_CLOUD_LIST_EINSTEIN_BOTS` | List Einstein Bots | Lists all Einstein Bot definitions in the Salesforce organization. This action queries the BotDefinition object using the Salesforce Tooling API to retrieve metadata about all Einstein Bots, including their IDs, labels, developer names, and language settings. Use this action when you need to: - Get a list of available Einstein Bots in the org - Find valid bot IDs for use with other Einstein Bots API operations - Retrieve bot metadata such as names and language settings Returns an empty list if no bots exist or if Tooling API access is unavailable. | | `SALESFORCE_SERVICE_CLOUD_QUERY_ALL_SOQL` | Query All SOQL | Tool to execute a SOQL query including deleted and archived records. Use when you need to fetch all rows including soft-deleted data in Salesforce. | | `SALESFORCE_SERVICE_CLOUD_QUERY_SOQL` | Query SOQL | Tool to execute a SOQL query. Use when you need to retrieve records from Salesforce via SOQL. | | `SALESFORCE_SERVICE_CLOUD_RECONNECT_CHAT_SESSION` | Reconnect Chat Session | Tool to reconnect a Live Agent chat session after the affinity token changes. Use this when you receive a 503 (Service Unavailable) response during chat operations, indicating the affinity token has changed and the session needs to be reestablished on a new server. After reconnecting, you must call ResyncChasitorState to restore the visitor's chat context. Note: Requires valid session_key and affinity tokens from an active Live Agent chat session. | | `SALESFORCE_SERVICE_CLOUD_RESYNC_CHASITOR_STATE` | Resync Chasitor State | Resynchronizes the chat visitor's state after a session reconnection. This action is part of the Salesforce Live Agent chat session recovery workflow: 1. First, call ReconnectChatSession with the session_key and affinity_token 2. Then, call this action to restore the visitor's chat state 3. Finally, resume normal chat operations (sending messages, getting messages, etc.) Prerequisites: - An active or recently disconnected Live Agent chat session - Valid session_key and affinity_token from the original session - Live Agent must be properly configured in the Salesforce org Note: The legacy Live Agent product is being phased out in favor of Messaging for In-App and Web. This action sends a POST request to /chat/rest/Chasitor/ChasitorResyncState with required Live Agent headers but no request body. | | `SALESFORCE_SERVICE_CLOUD_RETRIEVE_CONNECTED_APP_PRIVATE_KEY` | Retrieve Connected App Private Key | Tool to retrieve RSA private key PEM for a Salesforce Connected App. Use when signing JWT assertions for OAuth flows. Provide the app's Connected App ID and optional secret name or file path. Use before generating signed JWTs. | | `SALESFORCE_SERVICE_CLOUD_RETRIEVE_SALESFORCE_USERNAME` | Retrieve Salesforce Username | Tool to retrieve the Salesforce username. Use when you need the current authenticated user's username. Use after completing OAuth2 authentication. | | `SALESFORCE_SERVICE_CLOUD_SEND_CUSTOM_EVENT` | Send Custom Event | Send a custom event from a chat visitor to a Live Agent during an active chat session. Use this tool to trigger custom event handlers on the agent's side, enabling custom interactions beyond standard chat messages. Custom events can be used for actions like form submissions, button clicks, page navigation, or any application-specific events that need to be communicated to the agent. Prerequisites: - An active Live Agent chat session must be established - Live Agent REST API must be configured and enabled in your Salesforce org - Valid session_key and affinity_token from session initialization Note: This endpoint requires Live Agent to be properly configured. The API typically returns 204 No Content on success. | | `SALESFORCE_SERVICE_CLOUD_SET_BREADCRUMB` | Set Breadcrumb | Tool to set a breadcrumb URL for the visitor's current page. Use after a visitor navigates to a new page during an active chat session. | | `SALESFORCE_SERVICE_CLOUD_UPLOAD_FILE_TO_S3` | Upload File to S3 | Tool to upload a file to managed S3 storage. Use when you need to persist files externally. | | `SALESFORCE_SERVICE_CLOUD_VISITOR_SENSITIVE_DATA_RULE` | Visitor Sensitive Data Rule Triggered | Tool to trigger sensitive data rules for the chat visitor. Use after detecting sensitive content to apply visitor masking or handling rules. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Salesforce service cloud MCP server is an implementation of the Model Context Protocol that connects your AI agent to Salesforce service cloud. It provides structured and secure access so your agent can perform Salesforce service cloud operations on your behalf through a secure, permission-based interface. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before you begin, make sure you have: - Node.js and npm installed - A Composio account with API key - An OpenAI API key ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install required dependencies First, install the necessary packages for your project. What you're installing: - @ai-sdk/openai: Vercel AI SDK's OpenAI provider - @ai-sdk/mcp: MCP client for Vercel AI SDK - @composio/core: Composio SDK for tool integration - ai: Core Vercel AI SDK - dotenv: Environment variable management ```bash npm install @ai-sdk/openai @ai-sdk/mcp @composio/core ai dotenv ``` ### 3. Set up environment variables Create a .env file in your project root. What's needed: - OPENAI_API_KEY: Your OpenAI API key for GPT model access - COMPOSIO_API_KEY: Your Composio API key for tool access - COMPOSIO_USER_ID: A unique identifier for the user session ```bash OPENAI_API_KEY=your_openai_api_key_here COMPOSIO_API_KEY=your_composio_api_key_here COMPOSIO_USER_ID=your_user_id_here ``` ### 4. Import required modules and validate environment What's happening: - We're importing all necessary libraries including Vercel AI SDK's OpenAI provider and Composio - The dotenv/config import automatically loads environment variables - The MCP client import enables connection to Composio's tool server ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); ``` ### 5. Create Tool Router session and initialize MCP client What's happening: - We're creating a Tool Router session that gives your agent access to Salesforce service cloud tools - The create method takes the user ID and specifies which toolkits should be available - The returned mcp object contains the URL and authentication headers needed to connect to the MCP server - This session provides access to all Salesforce service cloud-related tools through the MCP protocol ```typescript async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["salesforce_service_cloud"], }); const mcpUrl = session.mcp.url; ``` ### 6. Connect to MCP server and retrieve tools What's happening: - We're creating an MCP client that connects to our Composio Tool Router session via HTTP - The mcp.url provides the endpoint, and mcp.headers contains authentication credentials - The type: "http" is important - Composio requires HTTP transport - tools() retrieves all available Salesforce service cloud tools that the agent can use ```typescript const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); ``` ### 7. Initialize conversation and CLI interface What's happening: - We initialize an empty messages array to maintain conversation history - A readline interface is created to accept user input from the command line - Instructions are displayed to guide the user on how to interact with the agent ```typescript let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to salesforce_service_cloud, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); ``` ### 8. Handle user input and stream responses with real-time tool feedback What's happening: - We use streamText instead of generateText to stream responses in real-time - toolChoice: "auto" allows the model to decide when to use Salesforce service cloud tools - stopWhen: stepCountIs(10) allows up to 10 steps for complex multi-tool operations - onStepFinish callback displays which tools are being used in real-time - We iterate through the text stream to create a typewriter effect as the agent responds - The complete response is added to conversation history to maintain context - Errors are caught and displayed with helpful retry suggestions ```typescript rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Complete Code ```typescript import "dotenv/config"; import { openai } from "@ai-sdk/openai"; import { Composio } from "@composio/core"; import * as readline from "readline"; import { streamText, type ModelMessage, stepCountIs } from "ai"; import { createMCPClient } from "@ai-sdk/mcp"; const composioAPIKey = process.env.COMPOSIO_API_KEY; const composioUserID = process.env.COMPOSIO_USER_ID; if (!process.env.OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set"); if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set"); if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set"); const composio = new Composio({ apiKey: composioAPIKey, }); async function main() { // Create a tool router session for the user const session = await composio.create(composioUserID!, { toolkits: ["salesforce_service_cloud"], }); const mcpUrl = session.mcp.url; const mcpClient = await createMCPClient({ transport: { type: "http", url: mcpUrl, headers: session.mcp.headers, // Authentication headers for the Composio MCP server }, }); const tools = await mcpClient.tools(); let messages: ModelMessage[] = []; console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n"); console.log( "Ask any questions related to salesforce_service_cloud, like summarize my last 5 emails, send an email, etc... :)))\n", ); const rl = readline.createInterface({ input: process.stdin, output: process.stdout, prompt: "> ", }); rl.prompt(); rl.on("line", async (userInput: string) => { const trimmedInput = userInput.trim(); if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) { console.log("\nGoodbye!"); rl.close(); process.exit(0); } if (!trimmedInput) { rl.prompt(); return; } messages.push({ role: "user", content: trimmedInput }); console.log("\nAgent is thinking...\n"); try { const stream = streamText({ model: openai("gpt-5"), messages, tools, toolChoice: "auto", stopWhen: stepCountIs(10), onStepFinish: (step) => { for (const toolCall of step.toolCalls) { console.log(`[Using tool: ${toolCall.toolName}]`); } if (step.toolCalls.length > 0) { console.log(""); // Add space after tool calls } }, }); for await (const chunk of stream.textStream) { process.stdout.write(chunk); } console.log("\n\n---\n"); // Get final result for message history const response = await stream.response; if (response?.messages?.length) { messages.push(...response.messages); } } catch (error) { console.error("\nAn error occurred while talking to the agent:"); console.error(error); console.log( "\nYou can try again or restart the app if it keeps happening.\n", ); } finally { rl.prompt(); } }); rl.on("close", async () => { await mcpClient.close(); console.log("\n👋 Session ended."); process.exit(0); }); } main().catch((err) => { console.error("Fatal error:", err); process.exit(1); }); ``` ## Conclusion You've successfully built a Salesforce service cloud agent using the Vercel AI SDK with streaming capabilities! This implementation provides a powerful foundation for building AI applications with natural language interfaces and real-time feedback. Key features of this implementation: - Real-time streaming responses for a better user experience with typewriter effect - Live tool execution feedback showing which tools are being used as the agent works - Dynamic tool loading through Composio's Tool Router with secure authentication - Multi-step tool execution with configurable step limits (up to 10 steps) - Comprehensive error handling for robust agent execution - Conversation history maintenance for context-aware responses You can extend this further by adding custom error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows. ## How to build Salesforce service cloud MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/salesforce_service_cloud/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/salesforce_service_cloud/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/salesforce_service_cloud/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/salesforce_service_cloud/framework/codex) - [Cursor](https://composio.dev/toolkits/salesforce_service_cloud/framework/cursor) - [VS Code](https://composio.dev/toolkits/salesforce_service_cloud/framework/vscode) - [OpenCode](https://composio.dev/toolkits/salesforce_service_cloud/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/salesforce_service_cloud/framework/openclaw) - [Hermes](https://composio.dev/toolkits/salesforce_service_cloud/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/salesforce_service_cloud/framework/cli) - [Google ADK](https://composio.dev/toolkits/salesforce_service_cloud/framework/google-adk) - [LangChain](https://composio.dev/toolkits/salesforce_service_cloud/framework/langchain) - [Mastra AI](https://composio.dev/toolkits/salesforce_service_cloud/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/salesforce_service_cloud/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/salesforce_service_cloud/framework/crew-ai) ## Related Toolkits - [Hubspot](https://composio.dev/toolkits/hubspot) - HubSpot is an all-in-one marketing, sales, and customer service platform. It lets teams nurture leads, automate outreach, and track every customer interaction in one place. - [Pipedrive](https://composio.dev/toolkits/pipedrive) - Pipedrive is a sales management platform offering pipeline visualization, lead tracking, and workflow automation. It helps sales teams keep deals moving forward efficiently and never miss a follow-up. - [Salesforce](https://composio.dev/toolkits/salesforce) - Salesforce is a leading CRM platform that helps businesses manage sales, service, and marketing. It centralizes customer data, enabling teams to drive growth and build strong relationships. - [Apollo](https://composio.dev/toolkits/apollo) - Apollo is a CRM and lead generation platform that helps businesses discover contacts and manage sales pipelines. Use it to streamline customer outreach and track your deals from one place. - [Attio](https://composio.dev/toolkits/attio) - Attio is a customizable CRM and workspace for managing your team's relationships and workflows. It helps teams organize contacts, automate tasks, and collaborate more efficiently. - [Acculynx](https://composio.dev/toolkits/acculynx) - AccuLynx is a cloud-based roofing business management software for contractors. It streamlines project tracking, lead management, and document sharing. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Affinity](https://composio.dev/toolkits/affinity) - Affinity is a relationship intelligence CRM that helps private capital investors find, manage, and close more deals. It streamlines deal flow and surfaces key connections to help you win opportunities. - [Agencyzoom](https://composio.dev/toolkits/agencyzoom) - AgencyZoom is a sales and performance platform built for P&C insurance agencies. It helps agents boost sales, retain clients, and analyze producer results in one place. - [Bettercontact](https://composio.dev/toolkits/bettercontact) - Bettercontact is a smart contact enrichment tool for finding emails and phone numbers. It helps boost lead generation with automated, waterfall search across multiple sources. - [Blackbaud](https://composio.dev/toolkits/blackbaud) - Blackbaud provides cloud-based software for nonprofits, schools, and healthcare institutions. It streamlines fundraising, donor management, and mission-driven operations. - [Brilliant directories](https://composio.dev/toolkits/brilliant_directories) - Brilliant Directories is an all-in-one platform for building and managing online membership communities and business directories. It streamlines listings, member management, and engagement tools into a single, easy interface. - [Capsule crm](https://composio.dev/toolkits/capsule_crm) - Capsule CRM is a user-friendly CRM platform for managing contacts and sales pipelines. It helps businesses organize relationships and streamline their sales process efficiently. - [Centralstationcrm](https://composio.dev/toolkits/centralstationcrm) - CentralStationCRM is an easy-to-use CRM software focused on collaboration and long-term customer relationships. It helps teams manage contacts, deals, and communications all in one place. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Close](https://composio.dev/toolkits/close) - Close is a CRM platform built for sales teams, combining calling, email automation, and predictive dialers. It streamlines sales workflows and boosts productivity with all-in-one communication tools. - [Dropcontact](https://composio.dev/toolkits/dropcontact) - Dropcontact is a B2B email finder and data enrichment service for professionals. It delivers verified email addresses and enriches contact info with up-to-date data. - [Dynamics365](https://composio.dev/toolkits/dynamics365) - Dynamics 365 is Microsoft's platform combining CRM, ERP, and productivity apps. It streamlines sales, marketing, service, and operations in one place. - [Espocrm](https://composio.dev/toolkits/espocrm) - EspoCRM is an open-source web application for managing customer relationships. It helps businesses organize contacts, track leads, and streamline their sales process. - [Fireberry](https://composio.dev/toolkits/fireberry) - Fireberry is a CRM platform that streamlines customer and sales management. It helps businesses organize contacts, automate sales, and integrate with other business tools. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Salesforce service cloud MCP? With a standalone Salesforce service cloud MCP server, the agents and LLMs can only access a fixed set of Salesforce service cloud tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Salesforce service cloud and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Vercel AI SDK v6? Yes, you can. Vercel AI SDK v6 fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Salesforce service cloud tools. ### Can I manage the permissions and scopes for Salesforce service cloud while using Tool Router? Yes, absolutely. You can configure which Salesforce service cloud scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Salesforce service cloud data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)