2,500+ MCP servers ready to use
Vinkius

Pipedrive Deals MCP Server for CrewAI 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

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

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Pipedrive Deals
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 Pipedrive Deals MCP Server

Connect Pipedrive CRM to any AI agent — manage your entire sales pipeline without switching tabs.

When paired with CrewAI, Pipedrive Deals becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Pipedrive Deals tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Deals — Search, create, and update deals with pipeline tracking
  • Contacts — Find and create persons with email, phone, and organization
  • Organizations — Search companies linked to deals and contacts
  • Activities — Create calls, meetings, tasks, and emails
  • Notes — Attach notes to deals, persons, or organizations
  • Pipelines — View all pipeline stages and deal flow

The Pipedrive Deals MCP Server exposes 12 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 Pipedrive Deals to CrewAI via MCP

Follow these steps to integrate the Pipedrive Deals MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Pipedrive Deals

Why Use CrewAI with the Pipedrive Deals MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Pipedrive Deals through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Pipedrive Deals + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Pipedrive Deals MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Pipedrive Deals for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Pipedrive Deals, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Pipedrive Deals tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Pipedrive Deals against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Pipedrive Deals MCP Tools for CrewAI (12)

These 12 tools become available when you connect Pipedrive Deals to CrewAI via MCP:

01

pd_create_deal

Title is required. Use pd_list_pipelines and pd_list_stages to find pipeline_id and stage_id. Link to existing contacts via person_id and org_id (use search tools to find these). Expected close date uses YYYY-MM-DD format. Create a new deal in Pipedrive with title, value, currency, expected close date, and pipeline/stage placement

02

pd_deal_followers

Followers receive notification updates about deal changes. Use to check who on the team is tracking a deal or to understand deal visibility across the organization. Get internal team members (users) following a specific deal in Pipedrive for visibility tracking

03

pd_deal_participants

Participants are contacts involved in the deal beyond the primary contact — e.g., decision makers, influencers, legal reviewers. Use when the user asks "who is involved in this deal?" or needs stakeholder information. Get all persons (contacts) participating in a specific Pipedrive deal

04

pd_deal_timeline

Use for trend analysis: "how many deals were created this month?", "show deal velocity over the last 12 weeks". Interval can be day/week/month, amount is the number of periods to look back. Get deal creation trends over time — how many deals were added per day, week, or month in a pipeline

05

pd_deals_by_pipeline

Use when the user wants to see all deals in a specific sales process (e.g., "show all deals in the Enterprise pipeline"). Find pipeline IDs using pd_list_pipelines. Get all deals in a specific pipeline for pipeline-level analysis and reporting

06

pd_deals_by_stage

Returns deals with title, value, persons, and orgs at that stage. Use for questions like "what deals are in Proposal?" or "how much is in Negotiation?". Find stage IDs using pd_list_stages. Get all deals at a specific pipeline stage for bottleneck analysis, forecasting, or stage-specific review

07

pd_delete_deal

This is permanent and removes all associated data. Consider using pd_update_deal with status="deleted" for soft-delete instead. Use only when the user explicitly wants to permanently remove a deal. Permanently delete a deal from Pipedrive — this action cannot be undone

08

pd_get_deal

Returns full deal data including title, value, stage, pipeline, linked persons/orgs, expected close date, creation date, and all custom fields. Use after searching to drill into a specific deal. Get the complete details of a specific Pipedrive deal by ID including all custom fields and history

09

pd_list_pipelines

Use to find pipeline IDs for filtering deals or creating new deals in a specific pipeline. List all sales pipelines in Pipedrive with names, deal counts, and active status

10

pd_list_stages

Essential for finding stage IDs to create, filter, or move deals. Shows each stage name, its order in the pipeline, and how many deals are at each stage. List stages within a Pipedrive pipeline showing names, display order, and deal counts per stage

11

pd_search_deals

Returns deal title, monetary value, currency, pipeline stage, pipeline name, linked person, and organization. Use when the user wants to find a specific deal or check pipeline status. Search Pipedrive deals by title or keyword to find opportunities with value, stage, pipeline, and linked contacts

12

pd_update_deal

Advance stage_id to move deals forward. Set status to "won" or "lost" to close. Update value after negotiation. Only specified fields change. Update a Pipedrive deal — advance stage, change value, or mark as won/lost to reflect pipeline progress

Example Prompts for Pipedrive Deals in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Pipedrive Deals immediately.

01

"Search for deals with Acme Corp"

02

"Create a call activity for tomorrow at 2pm"

03

"Show me the pipeline stages"

Troubleshooting Pipedrive Deals MCP Server with CrewAI

Common issues when connecting Pipedrive Deals to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

Rate limiting or 429 errors

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

Pipedrive Deals + CrewAI FAQ

Common questions about integrating Pipedrive Deals MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Pipedrive Deals to CrewAI

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.