Bring Chatbot Training
to Cursor
Learn how to connect Botsonic to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Botsonic MCP Server?
Connect your Botsonic (by Writesonic) account to any AI agent and manage your AI chatbot fleet through natural conversation.
What you can do
- Bot Management — Create, update, list, and inspect AI chatbots with personality, instructions, and knowledge base configuration
- Knowledge Base Training — Add web page URLs to a bot's knowledge base and review all training sources (URLs, documents, files)
- Conversation History — Browse all chat sessions per bot and inspect the full message history of any conversation
- Live Querying — Send messages to a bot and receive AI-generated responses in real time
- Lead Capture — Retrieve all leads collected by the chatbot during customer conversations
- Performance Analytics — Track usage metrics including conversation volume, message count, resolution rate, and customer satisfaction
How it works
1. Subscribe to this server
2. Enter your Botsonic API Token from your Writesonic dashboard
3. Start managing your chatbot fleet from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Customer Support Teams — monitor bot conversations, review resolution rates, and capture leads without switching dashboards
- Product Managers — train bots with new knowledge sources and test responses through conversational AI
- Growth Teams — analyze chatbot engagement metrics and lead capture performance across all bots
Built-in capabilities (12)
Add knowledge URL
Verify connectivity
Create a bot
Get bot details
Get bot analytics
Get conversation
List all bots
List conversations
List knowledge base
List captured leads
Send message to bot
Update a bot
Why Cursor?
Cursor's Agent mode turns Botsonic into an in-editor superpower. Ask Cursor to generate code using live data from Botsonic 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.
- —
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
Botsonic in Cursor
Botsonic and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Botsonic 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 Botsonic in Cursor
The Botsonic 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 12 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
Botsonic for Cursor
Every tool call from Cursor to the Botsonic MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I train a bot by adding web pages to its knowledge base?
Yes! The add_knowledge_url action accepts a Bot ID and a URL. Botsonic will crawl the page and add its content to the bot's training data. Use list_knowledge_base to review all sources (URLs, documents, files) currently training a specific bot.
Can I retrieve leads captured by my chatbot during customer interactions?
Yes. The list_leads tool retrieves all leads collected by a specific bot during conversations, including contact details, conversation context, and capture timestamp. This is ideal for syncing chatbot-qualified leads into your CRM.
How can I measure the performance of my chatbots?
Use get_bot_analytics with the Bot ID. It returns conversation count, total messages, resolution rate (percentage of conversations resolved without human handoff), and customer satisfaction scores. Compare across bots to identify which ones need KB improvements.
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.