Bring Chatbot Builder
to Cursor
Learn how to connect BotGenuity 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 BotGenuity MCP Server?
Connect your BotGenuity account to any AI agent and take full control of your automated customer engagement and chatbot operations through natural conversation.
What you can do
- Bot Orchestration — List and manage all your AI chatbot instances programmatically, retrieving detailed configuration and high-fidelity operational status in real-time
- Lead Capture Intelligence — Access complete directories of leads captured during bot interactions, including high-fidelity contact metadata and conversation context
- Conversation Discovery — Retrieve detailed chat histories and individual message threads to maintain a perfectly coordinated overview of customer needs
- Real-Time Interaction — Programmatically send messages to your chatbots to test performance or integrate bot responses into custom business workflows
- Platform Monitoring — Access chatbot configuration details and monitor account-level connectivity directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key (Bearer Token) from your BotGenuity dashboard (Settings > Security)
3. Start managing your conversational AI pipeline from Claude, Cursor, or any MCP client
No more manual toggling between chatbot portals or digging through individual lead tables. Your AI acts as your dedicated bot engineer and lead coordinator.
Who is this for?
- Customer Support Teams — instantly retrieve chat histories and monitor bot performance using natural language commands
- Marketing Managers — track lead generation trends and verify bot engagement without leaving your workspace
- Product Teams — integrate custom-trained chatbot responses into internal tools through simple AI queries
Built-in capabilities (6)
Send a message to a chatbot and get a response
Get details of a specific chatbot
Get full history for a conversation
List leads captured by a chatbot
List conversations for a chatbot
List all chatbots in your BotGenuity account
Why Cursor?
Cursor's Agent mode turns BotGenuity into an in-editor superpower. Ask Cursor to generate code using live data from BotGenuity 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
BotGenuity in Cursor
BotGenuity and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BotGenuity 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 BotGenuity in Cursor
The BotGenuity 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
BotGenuity for Cursor
Every tool call from Cursor to the BotGenuity 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 BotGenuity API Key?
Log in to your account, select a chatbot, navigate to Settings > Security, and generate your API Bearer Token.
Can I test bot responses via AI?
Yes! The chat_with_bot tool allows you to interact with your chatbots and retrieve high-fidelity AI responses programmatically.
How do I retrieve captured leads?
Use the list_captured_leads tool with a specific chatbot ID to retrieve all contact information collected during user sessions.
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.