Salesforce Service Cloud MCP Server for CrewAI 8 tools — connect in under 2 minutes
Connect your CrewAI agents to Salesforce Service Cloud through the Vinkius — pass the Edge URL in the `mcps` parameter and every Salesforce Service Cloud tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
from crewai import Agent, Task, Crew
agent = Agent(
role="Salesforce Service Cloud Specialist",
goal="Help users interact with Salesforce Service Cloud effectively",
backstory=(
"You are an expert at leveraging Salesforce Service Cloud tools "
"for automation and data analysis."
),
# Your Vinkius token — get it at cloud.vinkius.com
mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)
task = Task(
description=(
"Explore all available tools in Salesforce Service Cloud "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 8 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Salesforce Service Cloud MCP Server
Connect Salesforce Service Cloud to any AI agent.
When paired with CrewAI, Salesforce Service Cloud becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Salesforce Service Cloud tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.
What you can do
- Cases — Search, create, update, and filter by status or priority
- Comments — Read and add internal/public case comments
- Knowledge — Search published knowledge articles for instant answers
- Metrics — Aggregate case counts by status and priority
The Salesforce Service Cloud MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Salesforce Service Cloud to CrewAI via MCP
Follow these steps to integrate the Salesforce Service Cloud MCP Server with CrewAI.
Install CrewAI
Run pip install crewai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
Customize the agent
Adjust the role, goal, and backstory to fit your use case
Run the crew
Run python crew.py — CrewAI auto-discovers 8 tools from Salesforce Service Cloud
Why Use CrewAI with the Salesforce Service Cloud MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Salesforce Service Cloud through the Model Context Protocol.
Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools
CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Salesforce Service Cloud + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Salesforce Service Cloud MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Salesforce Service Cloud for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff
Scheduled intelligence reports: set up a crew that periodically queries Salesforce Service Cloud, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Salesforce Service Cloud tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow
Compliance and audit automation: a compliance agent queries Salesforce Service Cloud against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Salesforce Service Cloud MCP Tools for CrewAI (8)
These 8 tools become available when you connect Salesforce Service Cloud to CrewAI via MCP:
sf_add_case_comment
Set isPublished to true if the comment should be visible to the customer (e.g., in a customer portal). Default is internal-only. Use to log agent responses, internal notes, or resolution steps on a support case. Add a comment to a Salesforce case — internal note or customer-visible response
sf_case_comments
Returns comment body, whether it is published (customer-visible), creator name, and creation date. Comments provide the full conversation history of a support case. Use to review case discussions or get context before responding. Get all comments (internal and customer-visible) on a specific Salesforce case for case history review
sf_case_metrics
Returns summary data: how many cases at each status × priority intersection. Perfect for support team dashboards, capacity planning, and identifying volume trends. Use when the user asks "how many open cases do we have?" or "what is the case breakdown by priority?" Get aggregate support case metrics — case counts grouped by status and priority for a team dashboard view
sf_cases_by_status
Returns cases sorted by priority then creation date. Use for support queue management: "how many new cases are there?", "show escalated cases", or for case workload analysis by status. Get all Salesforce cases at a specific status for queue analysis — New, Working, Escalated, or Closed
sf_create_case
Subject is required. Status defaults to "New". Priority: High, Medium, Low. Origin: Web, Phone, Email. Link to a customer via contactId and their company via accountId (both use 18-char Salesforce IDs). Cases track the complete lifecycle of a customer support issue. Create a new support case in Salesforce Service Cloud with subject, description, priority, origin, and linked contact/account
sf_search_cases
Returns case number, subject, status (New/Working/Escalated/Closed), priority (High/Medium/Low), origin channel (Web/Phone/Email), case owner, and description. Use when the user wants to find a specific support case, look up a case number, or review customer issues. Search Salesforce Service Cloud cases by subject or case number to find customer support issues
sf_search_knowledge
Returns article title, summary, URL, and article type. Salesforce Knowledge is the built-in KB for self-service and agent-assist. Use when the user asks for help articles, documented solutions, or wants to check if an issue has been addressed in the knowledge base. Search the Salesforce Knowledge Base for published articles to find documented solutions and answers
sf_update_case
Common operations: advance Status from "New" to "Working" to "Closed", escalate Priority to "High", or append to Description. Only specified fields change. Update a Salesforce case — change status, escalate priority, or add description to reflect case progress
Example Prompts for Salesforce Service Cloud in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Salesforce Service Cloud immediately.
"How many open P1 cases do we have?"
"Find a knowledge article about password reset"
"Create a high-priority case: Login page returning 500 error"
Troubleshooting Salesforce Service Cloud MCP Server with CrewAI
Common issues when connecting Salesforce Service Cloud to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Salesforce Service Cloud + CrewAI FAQ
Common questions about integrating Salesforce Service Cloud MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.Can different agents in the same crew use different MCP servers?
mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.What happens when an MCP tool call fails during a crew run?
Can CrewAI agents call multiple MCP tools in parallel?
process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.Can I run CrewAI crews on a schedule (cron)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Salesforce Service Cloud with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Salesforce Service Cloud to CrewAI
Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.