Bring Chatbot Builder
to Cline
Learn how to connect BotGenuity to Cline 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 Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including BotGenuity tool calls without waiting for prompts between steps. Connect 6 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
BotGenuity in Cline
BotGenuity and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BotGenuity to Cline 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 Cline
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 Cline 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 Cline
Every tool call from Cline 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.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.