Bring Community Feedback
to Cursor
Learn how to connect UserEcho to Cursor and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the UserEcho MCP Server?
Connect your UserEcho account to any AI agent and simplify how you manage your community feedback, helpdesk tickets, and self-service content through natural conversation.
What you can do
- Helpdesk Management — List all support tickets and retrieve detailed conversation history and status for specific issues.
- Direct Ticketing — Programmatically create new support tickets directly from your agent to accelerate customer assistance.
- Knowledge Base Access — List and query all articles in your help center to verify self-service documentation.
- Forum Oversight — List and monitor feedback and support forums to understand community trends and suggestions.
- User Directory — List account users and team members to manage your support organization structure.
- Issue Tracking — Monitor the progress of client requests and verify resolution times via AI.
How it works
1. Subscribe to this server
2. Enter your UserEcho API Token and Subdomain (found in your developer settings)
3. Start managing your community feedback from Claude, Cursor, or any MCP client
Who is this for?
- Customer Support Managers — quickly retrieve ticket histories and monitor team activity via simple AI commands.
- Community Managers — monitor forum feedback and verify article availability directly from the workspace.
- Product Teams — coordinate bug reports and feature requests coming from UserEcho forums.
Built-in capabilities (6)
Add a new ticket
Get details for a specific ticket
List account users
List UserEcho forums
List knowledge base articles
List helpdesk tickets
Why Cursor?
Cursor's Agent mode turns UserEcho into an in-editor superpower. Ask Cursor to generate code using live data from UserEcho and it fetches, processes, and writes. all in a single agentic loop. 6 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
UserEcho in Cursor
UserEcho and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect UserEcho 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 UserEcho in Cursor
The UserEcho 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 6 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
UserEcho for Cursor
Every tool call from Cursor to the UserEcho MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the full conversation history of a support ticket?
Yes! Use the get_ticket_details tool and provide the Ticket ID. Your agent will retrieve the complete metadata and all conversation threads for that specific issue.
How do I list all the help center articles in my account?
Run the list_kb_articles query. The agent will retrieve a complete list of all articles currently published in your UserEcho knowledge base.
Is it possible to create a new ticket via AI for a customer?
Absolutely. Use the create_support_ticket action. Provide a header and the detailed content, and the agent will instantly log the request in your UserEcho helpdesk.
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.