Pipedrive Contacts MCP for AI. Manage your entire sales pipeline from conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Pipedrive Contacts MCP Server connects your AI agent directly to Pipedrive CRM. Manage entire sales pipelines—from finding a contact's phone number to updating their company details and viewing all associated deals—all through natural conversation.
What your AI can do
Pd create org
Creates a new company (organization) in Pipedrive, requiring only the name and optionally taking an address.
Pd create person
Adds a new contact person to Pipedrive using name, email, phone, and linking them to an organization ID.
Pd delete person
Permanently removes a contact record from Pipedrive; use this only when you are certain the data should be deleted.
The agent retrieves all active and closed deals associated with a specific contact using pd_person_deals.
You can create new organizations or contacts, immediately linking them to your CRM records via pd_create_org or pd_create_person.
Find specific people using name, email, or phone number with pd_search_persons, providing their ID and organization link.
Correct company addresses or change a contact's phone number by calling pd_update_org or pd_update_person.
Pull comprehensive data on a company—including address, deal counts (open/won/lost), and custom fields—using pd_get_org.
Ask an AI about this
Waiting for input…
Pipedrive Contacts MCP Server: 11 Tools for CRM Management
These tools let your AI client search, create, read, and write data across every major entity in Pipedrive—persons, organizations, and deals.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Pipedrive Contacts on VinkiusPd Create Org
Creates a new company (organization) in Pipedrive, requiring only the name and optionally taking an address.
Pd Create Person
Adds a new contact person to Pipedrive using name, email, phone, and linking them to...
Pd Delete Person
Permanently removes a contact record from Pipedrive; use this only when you are...
Pd Get Org
Retrieves all details for one company, including its address, deal counts, and any...
Pd Get Person
Pulls complete data on a specific contact, showing all emails, phones, activity...
Pd List Persons
Lists every person in your CRM with their names, emails, phone numbers, and associated organization links.
Pd Person Deals
Gets a list of all deals linked to one specific contact person, detailing titles, values, and stages.
Pd Search Orgs
Searches for companies by name to find the correct organization ID needed for...
Pd Search Persons
Finds people in your CRM using a search query on their name, email, or phone number.
Pd Update Org
Changes an existing company's data—like renaming it or updating its address—using...
Pd Update Person
Corrects a contact's information, such as changing their email or phone number...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Pipedrive Contacts integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Pipedrive Contacts, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Pipedrive. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 11 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Finding basic contact info shouldn't require switching between three tabs.
Today, finding a simple piece of data—like verifying the best email for a prospect or seeing their last known phone number—is a multi-step chore. You open your CRM, run a search, copy an ID, switch to a secondary tab, and then paste that ID into another window just to verify details. It’s clicking across three different screens.
With the Pipedrive Contacts MCP Server, all of that disappears. Your agent handles the whole flow in one chat turn. You simply ask: 'What's Jane Doe's email and phone?' And you get a single, structured answer immediately.
Pipedrive Contacts MCP Server: Manage full data lifecycle.
The biggest time sink is the gap between collecting data (e.g., at a trade show) and actually logging it into the system. You write down names, companies, and follow-up notes on a sticky pad—data that sits outside your workflow.
Now, you can dictate this information to your agent. 'Create an organization for Acme Corp, link John Smith as a contact, and leave a note saying we need to call them next Tuesday.' The server handles the three separate actions in one go.
What your AI can actually do with this
Look, you don't wanna be jumping between tabs just to keep track of who owes who what in Pipedrive. This server hooks your AI agent right into your entire Pipedrive CRM account. You can manage every single contact, company, and deal through natural conversation—no manual data entry, no searching menus.
It’s all built around giving your agent the ability to perform specific actions on your records.
When you need to find someone, you've got options. If you know a name, an email address, or a phone number, you can use pd_search_persons to nail down that person and get their ID and organization link back. Need to see everyone? You can run pd_list_persons to pull every single contact in your CRM, listing out all their names, emails, phone numbers, and which company they belong to.
If you're starting from scratch and just got a company name, you gotta use pd_search_orgs first; that tool searches for companies by name so you can get the necessary organization ID needed before linking any contacts or deals.
Once you have an ID, getting data is simple. To pull all the deep-dive info on a person—emails, phones, how many times they've been active, and what deals they’re tied to—you just run pd_get_person with their specific ID. If you need the full picture of a company, not just the name, you use pd_get_org.
This pulls every detail on an organization: its address, how many open or won deals it has, and any custom fields your team tracks.
Tracking history is where this gets real. You can ask for all the specific deals tied to one person using pd_person_deals; that list shows you the deal titles, their current values, and what stage they're stuck in. If you want to see a contact’s full sales journey—active or closed deals—you use this tool.
When you need details on a company, remember it pulls all the heavy stuff: address info, deal counts (open/won/lost), and any custom fields that matter.
Got new leads? You can create them right from your chat window. To make a whole new company, call pd_create_org, giving it a name and optionally an address. If you're adding a contact person to a brand-new account, you use pd_create_person, supplying the name, email, phone number, and crucially, linking them to the organization ID you just created or found.
And if things change? You can fix 'em. If an address is wrong, you run pd_update_org with the organization ID to rename it or update its mailing details. Did a contact switch jobs and get a new phone number? Use pd_update_person, passing the person's ID to correct their information. Don't forget that if data gets stale, you can permanently remove a record using pd_delete_person; but hey, only do that when you're absolutely sure it needs to be gone.
Basically, this gives your agent total control: find the person (pd_search_persons), get their full history (pd_get_person), pull up company details (pd_get_org), and then build or correct anything—from a new account via pd_create_org to updating someone's phone number via pd_update_person. It handles the whole sales cycle, so you don't have to.
019d75f4-3828-71a4-94b2-f71c826a1625 
Here's how it actually works
The bottom line is that your AI client executes multi-step workflows—search, read, and write—to manage Pipedrive records without you ever leaving your conversation.
First, ask your agent to search for the target entity. For a person, it runs pd_search_persons(email='...'). If it's a company, it calls pd_search_orgs(name='...').
Next, you specify the action: 'Update this contact's phone number' or 'Create a deal for this organization.' The agent then runs the appropriate write tool (pd_update_person, etc.).
Finally, the server confirms the change and returns the updated record data. You get back the full details of the modified person or company.
Who is this actually for?
Sales Development Reps (SDRs) who are tired of logging into the CRM just to copy-paste a contact's phone number. Sales Managers who need an instant, conversational overview of deal flow across multiple accounts. Revenue Operations teams needing real-time data access for reporting that bypasses UI limitations.
Uses the tool to quickly search for prospects by email or phone, and instantly create new contact records and associated activities.
Requests a deal summary for an existing client. The agent runs pd_person_deals to show the full sales history before drafting the next proposal.
Asks, 'What are our open deals with Acme Corp?' and gets a structured report using search and read tools.
What Changes When You Connect
Track full history instantly. Instead of navigating to a contact's profile, ask the agent what deals they have. It runs pd_person_deals and gives you a real-time list of active opportunities.
Save time updating data. If a client changes their address or name, don't log into the CRM. Tell your agent to run pd_update_org, providing only the ID and the new details.
Never lose a lead again. Need to find someone by just an email? Use pd_search_persons. It returns the person's full record—name, phone, org link—in one step.
Build out your network fast. When you meet a new vendor, use pd_create_org and pd_create_person to build two records simultaneously, ensuring perfect data linking from the start.
Get instant visibility into company status. If you're talking about 'Acme Corp,' ask the agent for details using pd_get_org. You get their address, total deals, and open/won counts immediately.
See it in action
Need to find a prospect's current opportunities?
A Sales Rep needs to know the deal history for John Smith. They ask: 'What deals does John have?' The agent runs pd_person_deals and returns a structured table of all associated titles, values, and stages, letting them prep for the call without opening the CRM.
A contact's phone number changed.
The SDR gets a new phone number. Instead of manually logging in to update the record, they tell their agent: 'Update John Doe's phone using pd_update_person.' The server updates the data and confirms the change.
Onboarding a brand-new company.
A new client is signed. The AE asks the agent to create them: 'Create an organization for GlobalTech with address X, and then create contact Jane Doe linked to it.' This uses pd_create_org followed by pd_create_person, ensuring proper data linkage.
Researching a cold lead.
The agent needs info on 'Acme Corp'. It first runs pd_search_orgs to verify the ID, then uses pd_get_org to pull key details like their number of open deals. This confirms the company's status before outreach.
The honest tradeoffs
Assuming IDs are known
The user tries to run pd_update_person('John Doe', 'new@email.com') but forgets the unique ID required by the API, causing an error.
Always use a search tool first. If you need John Doe's data, start with pd_search_persons(name='John Doe'). This returns his ID, which you then pass to pd_update_person.
Trying to list everything at once
The user asks the agent to 'List all contacts and their deals,' leading to a massive data dump that overwhelms both the API and the chat window.
Be specific. If you want deal info, target one person: pd_person_deals(person_id='...'). If you need directory browsing, use pd_list_persons.
Confusing contacts and companies
The user tries to update a company's address using the person tool, which fails because the tools are for different entity types.
Remember the difference: Use pd_update_org only when you are changing company info. Use pd_update_person when you change an individual’s name or email.
When It Fits, When It Doesn't
Use this server if your primary need is managing the core lifecycle of customer relationships: creating, reading, updating, and listing contacts, organizations, and deals within Pipedrive. It's built for sales execution.
Don't use this if you need complex financial reporting (e.g., generating quarterly revenue reports from an accounting ledger). For that, look at dedicated financial data integration tools. Also, if your goal is purely project management task tracking across multiple systems, a specialized task management tool may be better suited. This server excels at 'who owns what' and 'what was promised when.'
Questions you might have
How do I use pd_search_persons to find someone? +
You pass the search criteria (name, email, or phone) directly to pd_search_persons. The server returns a list of matching contacts along with their IDs and organizational links.
Can I use pd_person_deals to see all deals? +
Yes. You must first provide the person's unique ID, then call pd_person_deals. This returns a comprehensive list of every deal linked to that specific contact.
How do I update an organization using pd_update_org? +
You must first get the company's ID (e.g., via pd_search_orgs). Then, you call pd_update_org and specify only the fields you want to change, like 'address' or 'name'.
What is the difference between pd_get_person and pd_list_persons? +
Use pd_search_persons when you know who you are looking for. Use pd_list_persons to get a raw directory list of every single contact in your entire CRM.
If I use pd_delete_person, is that action irreversible? +
Yes, this deletion is permanent and cannot be undone. Before running pd_delete_person, confirm if you need to retain the contact record for historical deal tracking or reporting purposes.
When I use pd_create_person, how do I ensure it links to the right organization? +
You must provide a valid 'org_id' when calling pd_create_person. Always run pd_search_orgs first; this ensures you retrieve the correct ID needed for linking the new contact.
What happens if I use pd_update_person and only change one field? +
The tool updates only the fields you specify. It won't overwrite other data like emails or phone numbers. Just make sure to include the ID of the person record in your request.
After I use pd_search_orgs, how do I get all the company details and custom fields? +
Run pd_get_org using the ID found from the search. This tool pulls comprehensive data—including deal counts, linked people, and every custom field—that a simple search cannot retrieve.
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.
We've already built the connector for Pipedrive Contacts. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.