Pipedrive MCP Server for CursorGive Cursor instant access to 12 tools to Create New Deal, Get Api Status, Get Deal Details, and more
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 App Connector for Cursor
The Pipedrive app connector for Cursor is a standout in the Industry Titans category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Pipedrive and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"pipedrive": {
"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 MCP Server
Connect your Pipedrive account to any AI agent and take full control of your sales orchestration and pipeline management through natural conversation. Pipedrive is the leading CRM for sales teams, and this integration allows you to retrieve deal metadata, update customer records, and monitor activity logs directly from your chat interface.
Cursor's Agent mode turns Pipedrive into an in-editor superpower. Ask Cursor to generate code using live data from Pipedrive 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
- Deal & Pipeline Orchestration — List all managed deals and retrieve detailed metadata programmatically across various pipelines and stages to ensure your sales velocity is always synchronized.
- Contact & Organization Intelligence — Access and monitor your centralized database of persons and organizations directly from the AI interface to maintain high-fidelity customer profiles.
- Activity & Workflow Control — List and create sales activities (calls, meetings, tasks) via natural language to drive better team productivity and follow-up efficiency.
- Sales Search & Discovery — Perform targeted searches for specific deals or contacts to maintain a clear overview of your opportunities using simple AI commands.
- Operational Monitoring — Track system responses and manage user account metadata to ensure your sales workflows are always optimized.
The Pipedrive 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.
All 12 Pipedrive tools available for Cursor
When Cursor connects to Pipedrive through Vinkius, your AI agent gets direct access to every tool listed below — spanning pipeline-management, deal-tracking, crm, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Add new deal
Check connection
Get deal info
Get company info
Get contact info
List client companies
List individual contacts
List workflow stages
List CRM deals
List sales workflows
List tasks and meetings
Find deals
Connect Pipedrive to Cursor via MCP
Follow these steps to wire Pipedrive into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Pipedrive
Why Use Cursor with the Pipedrive MCP Server
Cursor AI Code Editor provides unique advantages when paired with Pipedrive 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 + Cursor Use Cases
Practical scenarios where Cursor combined with the Pipedrive 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
Example Prompts for Pipedrive in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Pipedrive immediately.
"List all my open deals in Pipedrive."
"Show me all deals in the negotiation stage with a value above $50,000 and their expected close dates."
"Add a new activity to schedule a demo call with contact Maria Chen at Meridian Corp for next Tuesday."
Troubleshooting Pipedrive MCP Server with Cursor
Common issues when connecting Pipedrive to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Pipedrive + Cursor FAQ
Common questions about integrating Pipedrive 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.