Bring Conversational Marketing
to Cursor
Learn how to connect Dashly to Cursor and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Dashly MCP Server?
Connect your Dashly account to any AI agent and take full control of your conversational marketing and user tracking workflows through natural conversation.
What you can do
- User Lifecycle Orchestration — List and manage your entire high-fidelity user database programmatically, retrieving detailed profile metadata and custom property updates
- Conversational Intelligence — Query active chat sessions, retrieve high-fidelity message history, and send instant replies directly through your agent
- Event Tracking Architecture — Programmatically record custom user actions (e.g., 'Pricing Viewed') to maintain a perfectly coordinated audit trail of customer behavior
- Channel Optimization — Access your complete directory of communication channels to coordinate your engagement strategy across multiple touchpoints
- Operational Monitoring — Verify account-level API connectivity and monitor user activity trends directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your Auth Token from your Dashly dashboard (Settings > Integrations > API Keys)
3. Start orchestrating your customer engagement from Claude, Cursor, or any MCP client
No more manual toggling between chat tabs or missing critical user events. Your AI acts as your dedicated engagement coordinator and behavioral architect.
Who is this for?
- Customer Support Leads — instantly retrieve user history and reply to conversations using natural language commands
- Marketing Operations — track custom events and segment users without leaving your creative workspace
- Product Managers — monitor user property updates and engagement health through simple AI queries
Built-in capabilities (8)
Get details for a specific conversation
Get details for a specific user
List communication channels
List recent conversations
List all Dashly users
Send a reply to a conversation
Set custom properties for a user
Track a custom event for a user
Why Cursor?
Cursor's Agent mode turns Dashly into an in-editor superpower. Ask Cursor to generate code using live data from Dashly and it fetches, processes, and writes. all in a single agentic loop. 8 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
Dashly in Cursor
Dashly and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Dashly 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 Dashly in Cursor
The Dashly 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 8 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
Dashly for Cursor
Every tool call from Cursor to the Dashly MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Dashly Auth Token?
Log in to your account, navigate to Settings > Integrations > API Keys, and copy your unique Auth Token.
Can I record custom user events via AI?
Yes! The track_event tool allows your agent to log specific user actions programmatically by providing the user ID and event name.
How do I check active chat sessions?
Use the list_conversations tool to retrieve a comprehensive directory of all current chat interactions and their high-fidelity metadata.
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.