Bring Chatbot Training
to Claude Desktop
Learn how to connect Botsonic to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Botsonic to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Botsonic in Claude Desktop
Botsonic and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Botsonic to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
