Outreach MCP Server for CursorGive Cursor instant access to 12 tools to Add To Sequence, Create Prospect, Get Prospect 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 Outreach 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 Outreach and 3,400+ MCP Servers from a single visual interface.
{
"mcpServers": {
"outreach-alternative": {
"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 Outreach MCP Server
Connect your Outreach.io account to any AI agent and take full control of your sales orchestration and prospect engagement through natural conversation. Outreach is the premier sales engagement platform, and this integration allows you to retrieve prospect metadata, enroll leads into automated sequences, and monitor mailing performance directly from your chat interface.
Cursor's Agent mode turns Outreach into an in-editor superpower. Ask Cursor to generate code using live data from Outreach 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
- Prospect & Audience Orchestration — List all managed prospects and retrieve detailed profile metadata programmatically to ensure your sales database is always synchronized.
- Sequence & Automation Control — Enroll prospects into automated sequences and monitor sequence states directly from the AI interface to track lead nurturing progress.
- Communication Intelligence — Access and monitor sent mailings and retrieve detailed engagement metadata via natural language to drive better follow-up efficiency.
- Account & Deal Oversight — Access organizational accounts and monitor sales opportunities using simple AI commands to maintain a clear overview of your pipeline.
- Operational Monitoring — Track system responses and manage sales tasks to ensure your outreach workflows are always optimized.
The Outreach 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 Outreach tools available for Cursor
When Cursor connects to Outreach through Vinkius, your AI agent gets direct access to every tool listed below — spanning outreach, sales-engagement, prospecting-api, 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.
Enroll prospect in sequence
Add new prospect
Get full prospect info
Get account profile
List outreach accounts
List message templates
List sales deals
List engageable people
List pending actions
List sent mailings
List sales sequences
Modify prospect info
Connect Outreach to Cursor via MCP
Follow these steps to wire Outreach 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 Outreach
Why Use Cursor with the Outreach MCP Server
Cursor AI Code Editor provides unique advantages when paired with Outreach 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
Outreach + Cursor Use Cases
Practical scenarios where Cursor combined with the Outreach 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 Outreach in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Outreach immediately.
"List all active prospects in Outreach."
"Show me all active email sequences and their open rates for this quarter."
"Find all prospects who replied positively to the Enterprise sequence in the last 7 days."
Troubleshooting Outreach MCP Server with Cursor
Common issues when connecting Outreach to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Outreach + Cursor FAQ
Common questions about integrating Outreach 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.