Bring Experience Data
to Cursor
Learn how to connect Pitchly to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Pitchly MCP Server?
Connect your Pitchly account to any AI agent and take full control of your organizational experience and content orchestration through natural conversation. Pitchly is the data management platform of choice for professional services firms, and this integration allows you to retrieve workspace metadata, manage custom data tables, and update critical records (deals, bios, tombstones) directly from your chat interface.
What you can do
- Workspace & Table Orchestration — List all managed workspaces and retrieve detailed table structures programmatically to ensure your data foundation is always synchronized.
- Record Lifecycle Management — Query, create, and update records across custom tables with detailed profile metadata directly from the AI interface to maintain high-fidelity business intelligence.
- Content Discovery Intelligence — Search through complex data sets for specific deals, professional bios, or tombstone data via natural language to drive better research efficiency.
- Data Ingestion Control — Automate the creation of new records and manage organizational metadata using simple AI commands.
- Operational Monitoring — Track system responses and manage workspace health to ensure your experience management is always optimized.
How it works
1. Subscribe to this server
2. Enter your Pitchly API Key (Bearer Token) from your developer settings
3. Start managing your professional experience data from Claude, Cursor, or any MCP-compatible client
No more manual spreadsheet updates or searching through disparate databases. Your AI acts as a dedicated experience manager or data coordinator.
Who is this for?
- Professional Services Firms — quickly retrieve deal summaries and monitor team experience without switching apps.
- Marketing & BD Teams — automate the retrieval of tombstone data and track professional bios via natural conversation.
- Knowledge Managers — streamline the retrieval of organizational metadata and monitor data health directly within the chat.
Built-in capabilities (11)
Add a new record to a table
Delete a record from a table
Get details of a specific record
Get details of a specific table
Get details of a specific workspace
List all fields in a table
List records in a Pitchly table
List tables in a workspace
List all Pitchly workspaces
Search records within a table
Update an existing record
Why Cursor?
Cursor's Agent mode turns Pitchly into an in-editor superpower. Ask Cursor to generate code using live data from Pitchly and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
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
Pitchly in Cursor
Pitchly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pitchly to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Pitchly in Cursor
The Pitchly 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. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Pitchly for Cursor
Every tool call from Cursor to the Pitchly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find a specific deal record by its ID?
Yes! Use the get_record tool with the Table ID and Record ID. Your agent will respond with the complete metadata for the entry, including all custom field values in seconds.
How do I find my Pitchly API Key?
Log in to your Pitchly account, navigate to Settings or your Developer Dashboard, and you will find your unique secret API key there. You may need organization admin privileges to see it.
Does this work with custom tables?
Absolutely. This integration dynamically lists all tables available in your workspaces, allowing the AI to interact with any custom schema you've created for deals, bios, or projects.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a 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?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.