What Pipedrive data can I access?

Deals, Persons, Organizations, Activities, Notes, and Pipelines. All data respects your Pipedrive permissions.

Can I create and update records?

Yes! Create and update deals, contacts, activities, and notes — all through natural conversation.

How does authentication work?

Uses your personal Pipedrive API token. Find it in Settings > Personal preferences > API. No OAuth flow needed.

Pipedrive CRM (Full) MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Pipedrive CRM (Full)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Pipedrive CRM (Full) through Vinkius, pass the Edge URL in the `mcps` parameter and every Pipedrive CRM (Full) 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="Pipedrive CRM (Full) Specialist",
    goal="Help users interact with Pipedrive CRM (Full) effectively",
    backstory=(
        "You are an expert at leveraging Pipedrive CRM (Full) 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 CRM (Full) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 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 Pipedrive CRM (Full) MCP Server

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

When paired with CrewAI, Pipedrive CRM (Full) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Pipedrive CRM (Full) 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 CRM (Full) MCP Server exposes 11 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 CRM (Full) to CrewAI via MCP

Follow these steps to integrate the Pipedrive CRM (Full) 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 11 tools from Pipedrive CRM (Full)

Why Use CrewAI with the Pipedrive CRM (Full) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Pipedrive CRM (Full) 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 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

Pipedrive CRM (Full) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Pipedrive CRM (Full) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Pipedrive CRM (Full) 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 Pipedrive CRM (Full), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Pipedrive CRM (Full) 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 Pipedrive CRM (Full) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Pipedrive CRM (Full) MCP Tools for CrewAI (11)

These 11 tools become available when you connect Pipedrive CRM (Full) to CrewAI via MCP:

pd_create_activity

Subject and type are required. Type must be one of: call, meeting, email, task, lunch, deadline. Optionally set due_date (YYYY-MM-DD) and link to deal_id, person_id, or both. Add a note for context. Activities appear in the Pipedrive calendar and task queue. Schedule a sales activity in Pipedrive — a call, meeting, email, task, lunch, or deadline linked to deals or contacts

pd_create_deal

Title is required. Optionally specify monetary value, currency (USD/EUR/GBP/etc.), linked person_id and org_id (use search tools to find these), and pipeline/stage placement (use pd_list_pipelines and pd_list_stages to find IDs). If no pipeline is specified, the deal enters the default pipeline at its first stage. Create a new deal in your Pipedrive sales pipeline with title, value, currency, and linked contact/organization

pd_create_note

Notes appear in the timeline/history of the linked record. Link to exactly one of: deal_id, person_id, or org_id. Use to log meeting summaries, call notes, or internal context on any CRM record. Create a note in Pipedrive attached to a deal, person, or organization for activity logging

pd_create_person

Name is required. Email and phone are optional but recommended for contact management. Link to an existing organization using org_id (use pd_search_organizations to find). Returns the created person with their new Pipedrive ID. Create a new contact (person) in Pipedrive with name, email, phone, and optional organization link

pd_list_activities

Returns subject, type (call/meeting/email/task/lunch/deadline), due date, due time, completion status, and linked deal/person. Use when the user asks about upcoming tasks, scheduled meetings, overdue activities, or recent sales activity. List recent Pipedrive activities (calls, meetings, tasks, emails) with due dates, types, and completion status

pd_list_pipelines

Returns pipeline name, total deal count, and whether it is active. Most Pipedrive accounts have one default pipeline, but larger teams may have separate pipelines for different sales processes (e.g., New Business vs Renewals). Use to find pipeline IDs before creating deals or filtering by pipeline. List all sales pipelines configured in Pipedrive with their names, deal counts, and order

pd_list_stages

Returns stage name, display order, number of deals at each stage, and rotten days (warning threshold). Use to find stage IDs for creating or moving deals, or to understand the sales process flow. List the stages within a Pipedrive pipeline showing stage names, order, deal counts, and win probability

pd_search_deals

Returns deal title, monetary value, currency, pipeline stage, pipeline name, linked person (contact), and organization. Use when the user wants to find a specific deal, check pipeline status, look up deal values, or see which stage a deal is in. Search Pipedrive deals by name or keyword to find opportunities in your sales pipeline with value, stage, and contact info

pd_search_organizations

Returns org name, address, and associated data. Use when the user wants to find a company, needs org IDs for linking to deals or persons, or wants to look up account details. Search Pipedrive organizations (companies) by name to find accounts in your CRM

pd_search_persons

Returns person name, email addresses, phone numbers, and linked organization. Use when the user wants to find a contact, look up someone by email, or get person IDs for linking to deals or activities. Search Pipedrive contacts (persons) by name, email, or phone to find people in your CRM

pd_update_deal

Only specified fields are updated. Common use: advance stage_id when a deal progresses, update value after negotiation, or set status to "won"/"lost" to close a deal. Available statuses: open, won, lost, deleted. Update an existing Pipedrive deal — change stage, value, title, or mark as won/lost to reflect pipeline progress

Example Prompts for Pipedrive CRM (Full) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Pipedrive CRM (Full) immediately.

"Search for deals with Acme Corp"

"Create a call activity for tomorrow at 2pm"

"Show me the pipeline stages"

Troubleshooting Pipedrive CRM (Full) MCP Server with CrewAI

Common issues when connecting Pipedrive CRM (Full) 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

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

Pipedrive CRM (Full) + CrewAI FAQ

Common questions about integrating Pipedrive CRM (Full) 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.