What Salesforce data can I access?

Leads, Opportunities, Accounts, Contacts, Tasks, and aggregate pipeline summaries. All data respects your Salesforce field-level security permissions.

Can I create and update records?

Yes! You can create Leads and Tasks, update Leads and Opportunities (stage, amount, close date), and log activities — all through natural conversation.

How does authentication work?

Uses OAuth 2.0 Client Credentials flow. You provide your Salesforce Instance URL, Consumer Key, and Consumer Secret from a Connected App. The server handles token exchange and renewal automatically.

Salesforce Sales Cloud MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Salesforce Sales Cloud
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Salesforce Sales Cloud through the Vinkius — pass the Edge URL in the `mcps` parameter and every Salesforce Sales Cloud tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Salesforce Sales Cloud Specialist",
    goal="Help users interact with Salesforce Sales Cloud effectively",
    backstory=(
        "You are an expert at leveraging Salesforce Sales 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 Sales Cloud "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 Sales Cloud MCP Server

Connect Salesforce Sales Cloud to any AI agent — instant access to your CRM data without switching tabs.

When paired with CrewAI, Salesforce Sales Cloud becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Salesforce Sales 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

Leads — Search, create, update, and qualify leads by name, email, or company
Opportunities — Track deals, update stages, amounts, and close dates
Accounts — Look up company details including revenue, industry, and employees
Contacts — Find contacts by name or email with account associations
Activities — Log calls, meetings, and emails as Tasks linked to records
Pipeline — Get an instant summary of your open pipeline by stage

The Salesforce Sales Cloud MCP Server exposes 10 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 Sales Cloud to CrewAI via MCP

Follow these steps to integrate the Salesforce Sales 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 10 tools from Salesforce Sales Cloud

Why Use CrewAI with the Salesforce Sales Cloud MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Salesforce Sales 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 Sales Cloud + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Salesforce Sales Cloud MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Salesforce Sales 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 Sales Cloud, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Salesforce Sales 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 Sales Cloud against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Salesforce Sales Cloud MCP Tools for CrewAI (10)

These 10 tools become available when you connect Salesforce Sales Cloud to CrewAI via MCP:

sf_create_lead

lastName and company are required fields in Salesforce. Status defaults to "Open - Not Contacted". Once qualified, leads can be converted to Contact + Account + Opportunity in the Salesforce UI. Returns the created lead with its 18-character Salesforce ID. Create a new lead in Salesforce Sales Cloud with name, company, email, phone, title, and initial status

sf_log_activity

Link to a person via whoId (Contact or Lead ID) and/or to a record via whatId (Account or Opportunity ID). Status defaults to "Completed". Priority: High, Normal, Low. Use to log completed calls, meetings, or emails for activity tracking and reporting. Log a call, meeting, or email as a completed Task in Salesforce linked to a contact, lead, account, or opportunity

sf_opportunities_by_stage

Returns deals sorted by amount descending. Standard stages: Prospecting, Qualification, Needs Analysis, Value Proposition, Id. Decision Makers, Perception Analysis, Proposal/Price Quote, Negotiation/Review, Closed Won, Closed Lost. Use for questions like "what deals are in Negotiation?" or "total value of Closed Won this quarter." Get all Salesforce opportunities at a specific pipeline stage for bottleneck analysis, forecasting, or stage review

sf_pipeline_summary

Returns the number of deals and total monetary value at each stage. Perfect for pipeline health checks, forecasting conversations, and identifying bottleneck stages. Use when the user asks "how is the pipeline?", "what is our total pipeline value?", or "which stage has the most deals?" Get an aggregate snapshot of the open sales pipeline — deal count and total value per stage for a quick health check

sf_search_accounts

Returns account name, industry, annual revenue, number of employees, phone, website, billing city/state/country, and owner. Accounts are the company-level records that contacts and opportunities are linked to. Use when the user asks about a company or needs account-level data. Search Salesforce accounts (companies) by name to find organizations with industry, revenue, employee count, and location

sf_search_contacts

Returns contact name, email, phone, account name, title, department, and mailing address. Contacts are qualified individuals linked to accounts — different from leads (unqualified prospects). Use when the user asks about a specific customer contact. Search Salesforce contacts by name or email to find people at customer accounts with title, department, and phone

sf_search_leads

Returns lead name, company, email, phone, title, status (e.g., Open - Not Contacted, Working, Closed - Converted), rating (Hot/Warm/Cold), lead source, and assigned owner. Use when the user wants to find a specific prospect, check lead status, or review unqualified pipeline. Search Salesforce leads by name, email, or company to find prospective customers in the sales pipeline

sf_search_opportunities

Returns opportunity name, stage (Prospecting/Qualification/Needs Analysis/Value Proposition/Id. Decision Makers/Perception Analysis/Proposal/Negotiation/Closed Won/Closed Lost), amount, close date, probability percentage, and assigned owner. Use for pipeline review, deal lookup, or forecasting queries. Search Salesforce opportunities by name to find deals with stage, amount, probability, close date, and owner

sf_update_lead

Only specified fields are updated. Common operations: change Status to "Working" or "Closed - Converted", set Rating to Hot/Warm/Cold for prioritization, or update contact details. Requires the 18-character Salesforce ID. Update an existing Salesforce lead — change status, rating, contact info, or other fields to reflect qualification progress

sf_update_opportunity

Common operations: advance StageName when deal progresses, update Amount after negotiation, push CloseDate when timeline shifts, set StageName to "Closed Won"/"Closed Lost" to close. Only specified fields change. Update a Salesforce opportunity — advance stage, change amount, update close date, or add notes to reflect deal progress

Example Prompts for Salesforce Sales Cloud in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Salesforce Sales Cloud immediately.

"Show me all hot leads from this week"

"What does my pipeline look like right now?"

"Create a new lead: John Smith from Acme Corp, john@acme.com"

Troubleshooting Salesforce Sales Cloud MCP Server with CrewAI

Common issues when connecting Salesforce Sales Cloud to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Salesforce Sales Cloud + CrewAI FAQ

Common questions about integrating Salesforce Sales Cloud MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard 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?

Yes. Each agent has its own 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?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using 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)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.