Bring Chatbot Platform
to Claude Desktop
Learn how to connect The Botforge to Claude Desktop and start using 5 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the The Botforge MCP Server?
Connect your The Botforge account to any AI agent and simplify how you manage your conversational AI, handle contact submissions, and monitor bot health through natural conversation.
What you can do
- Bot Oversight — List all chatbots in your account and retrieve real-time operational status for specific bot IDs.
- Contact Submission — Programmatically submit data to your bot's contact forms, ideal for automated lead capture.
- Event Integration — Subscribe to bot events via webhooks to receive real-time updates on user interactions.
- Metadata Inspection — Retrieve sample data and form field configurations to understand your bot's data structure.
- Operational Monitoring — Check connectivity and verify if your bots are online and responsive via AI queries.
How it works
- Subscribe to this server
- Enter your The Botforge API Key (found in your account dashboard)
- Start managing your conversational ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Chatbot Developers — quickly check bot statuses and test form submissions via simple AI commands.
- Marketing Teams — automate lead capture from external sources directly into your bot engine.
- Support Managers — monitor bot health and receive real-time interaction events without leaving the workspace.
Built-in capabilities (5)
Check bot operational status
Get bot form field samples
List all chatbots
Pass data as a JSON string. Submit data to the bot contact form
Pass data as a JSON string. Subscribe to bot events via webhook
Why Claude Desktop?
Claude Desktop is the definitive way to connect The Botforge to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 5 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
The Botforge in Claude Desktop
The Botforge and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect The Botforge 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 | 4,000+ 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 The Botforge in Claude Desktop
The The Botforge 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 5 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
The Botforge for Claude Desktop
Every tool call from Claude Desktop to the The Botforge MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check if a specific chatbot is online via AI?
Yes! Use the get_bot_status tool and provide the Bot ID. Your agent will retrieve the current operational state of that specific bot.
How do I submit data to my bot's contact form using the agent?
Use the submit_contact action. Provide the contact details (name, email, message) in a JSON string. The agent will transmit this data directly to the bot engine.
Is it possible to see which fields my bot expects in its form?
Absolutely. Use the get_samples query. The agent will retrieve sample data based on your bot's configured form fields, helping you understand the required structure.
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.
Explore More MCP Servers
View all →
Pipedrive
12 toolsAutomate sales CRM via Pipedrive — manage deals, persons, and activities directly from any AI agent.
Justia Legal Intelligence
2 toolsUniversal legal intelligence — search cases, statutes, and lawyers via AI.
AntChain
10 toolsAlibaba's enterprise blockchain API hub — query blocks, transactions, smart contracts, and accounts on AntChain BaaS.
Fizzpa
12 toolsMarket your restaurant or food business with digital menus, online ordering integration, and customer engagement tools.