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 Contacts MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Pipedrive Contacts
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Pipedrive Contacts through Vinkius, pass the Edge URL in the `mcps` parameter and every Pipedrive Contacts 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 Contacts Specialist",
    goal="Help users interact with Pipedrive Contacts effectively",
    backstory=(
        "You are an expert at leveraging Pipedrive Contacts 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 Contacts "
        "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 Contacts MCP Server

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

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

Follow these steps to integrate the Pipedrive Contacts 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 Contacts

Why Use CrewAI with the Pipedrive Contacts MCP Server

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

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

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

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

Pipedrive Contacts MCP Tools for CrewAI (11)

These 11 tools become available when you connect Pipedrive Contacts to CrewAI via MCP:

pd_create_org

Name is required. Address is optional. Once created, persons and deals can be linked to this organization. Returns the created org with its new Pipedrive ID. Create a new organization (company/account) in Pipedrive with name and address

pd_create_person

Name is required. Link to an existing organization via org_id (use pd_search_orgs to find). Pipedrive supports multiple emails and phones per person — here a single value is accepted for simplicity. Returns the created person with their new ID. Create a new contact (person) in Pipedrive with name, email, phone, and optional organization link

pd_delete_person

Use only when the user explicitly wants to delete a contact. Consider whether the contact should remain in the system for historical deal tracking before deleting. Permanently delete a contact from Pipedrive — this action cannot be undone

pd_get_org

Returns org name, address, open/won/lost deal counts, number of people linked, and all custom fields. Use after searching to drill into a specific company for full details. Get complete details of a specific Pipedrive organization by ID, including address, deal stats, and custom fields

pd_get_person

Returns full contact data: name, all emails, all phones, organization, open/won/lost deal counts, activities count, and custom fields. Use after searching to drill into a specific contact. Get complete details of a specific Pipedrive contact by ID, including all custom fields and activity history

pd_list_persons

Returns names, emails, phones, and linked orgs. Use for contact directory browsing, headcount analysis, or when the user wants to see all people in the CRM. List all contacts in Pipedrive with names, emails, phones, and organization associations

pd_person_deals

Returns deal titles, values, stages, and statuses. Use when the user asks "what deals does this person have?" or wants to see the full sales relationship history for a contact. Get all deals linked to a specific contact person to see their sales history and active opportunities

pd_search_orgs

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

pd_search_persons

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

pd_update_org

Only specified fields change. Use when the user wants to correct company info, update the address, or rename an account. Update an existing Pipedrive organization — change name, address, or other properties

pd_update_person

Only specified fields are changed. Use when the user wants to correct contact details, update a phone number, or change the associated organization. Update an existing Pipedrive contact — change name, email, phone, or other properties

Example Prompts for Pipedrive Contacts in CrewAI

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

"Search for deals with Acme Corp"

"Create a call activity for tomorrow at 2pm"

"Show me the pipeline stages"

Troubleshooting Pipedrive Contacts MCP Server with CrewAI

Common issues when connecting Pipedrive Contacts 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 Contacts + CrewAI FAQ

Common questions about integrating Pipedrive Contacts 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.