Pipedrive Deals MCP Server for Cursor 12 tools — connect in under 2 minutes
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Pipedrive Deals and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"pipedrive-deals": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
Cursor's Agent mode turns Pipedrive Deals into an in-editor superpower. Ask Cursor to generate code using live data from Pipedrive Deals and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
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 Cursor 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 Cursor via MCP
Follow these steps to integrate the Pipedrive Deals MCP Server with Cursor.
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
Save the file
Cursor will automatically detect the new MCP server
Start using Pipedrive Deals
Open Agent mode in chat and ask: "Using Pipedrive Deals, help me...". 12 tools available
Why Use Cursor with the Pipedrive Deals MCP Server
Cursor AI Code Editor provides unique advantages when paired with Pipedrive Deals through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Pipedrive Deals + Cursor Use Cases
Practical scenarios where Cursor combined with the Pipedrive Deals MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Pipedrive Deals MCP Tools for Cursor (12)
These 12 tools become available when you connect Pipedrive Deals to Cursor via MCP:
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
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
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
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
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
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
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
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
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
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
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
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 Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Pipedrive Deals immediately.
"Search for deals with Acme Corp"
"Create a call activity for tomorrow at 2pm"
"Show me the pipeline stages"
Troubleshooting Pipedrive Deals MCP Server with Cursor
Common issues when connecting Pipedrive Deals to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Pipedrive Deals + Cursor FAQ
Common questions about integrating Pipedrive Deals MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
Connect Pipedrive Deals with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Pipedrive Deals to Cursor
Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.