The Botforge MCP for AI. Manage Status and Test Leads via Chat.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
The Botforge manages your entire conversational AI backend from one place. Use this server to check bot operational status, list active bots, submit contact forms for lead capture, and subscribe to real-time user events—all through simple natural language commands.
What your AI can do
Get bot status
Checks and reports the current operational status of a specific chatbot ID.
Get samples
Retrieves sample data to show the expected format and fields for a bot's contact form.
List bots
Returns a list of every chatbot configured in your Botforge account.
Retrieves a full inventory, including names and IDs, for every bot configured in your account.
Verifies if a specific chatbot is online and responsive by querying its current operational state.
Sends structured lead or contact information directly to the designated bot form for processing.
Retrieves sample data and metadata on required form fields, helping you understand how to structure submissions.
Subscribes your system to webhooks, ensuring you receive immediate notifications whenever a user interacts with any bot.
Ask an AI about this
Waiting for input…
The Botforge: 5 Tools for Chatbot Management
These tools let you manage bot status, retrieve required data samples, list all bots in your account, submit contact leads, and subscribe to real-time event webhooks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using The Botforge on VinkiusGet Bot Status
Checks and reports the current operational status of a specific chatbot ID.
Get Samples
Retrieves sample data to show the expected format and fields for a bot's contact...
List Bots
Returns a list of every chatbot configured in your Botforge account.
Submit Contact
Sends structured data, like a name and email, to the bot's primary contact form for...
Subscribe Webhook
Sets up real-time event monitoring by subscribing your system to all user...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with The Botforge, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by The Botforge. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 5 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Managing your bot fleet shouldn't involve constant dashboard switching.
Today, checking on a chatbot ecosystem is a mess of tabs: one tab for Bot A's status, another for Bot B's metrics, and yet a third place to manually submit lead data. You end up copy-pasting IDs and switching between the main bot dashboard, the webhook console, and your CRM—it’s slow, error-prone, and frankly, annoying.
With The Botforge MCP Server, you keep it all in one chat window. Need to know if 'Sales Assistant' is online? Ask with an AI prompt. Want to feed a lead into 'Lead Intake'? Use the `submit_contact` tool. You get instant status checks and reliable data entry without leaving your agent.
The Botforge MCP Server: Submit Leads via Chat.
Manual lead capture involves filling out web forms, which breaks if the form changes or requires complex validation. You have to wait for a manual workflow step just to get data into the bot engine.
Now, you simply run `submit_contact` and pass your structured JSON payload. The agent handles the connection and data transfer instantly. It's clean, reliable, and works every time.
What your AI can actually do with this
The Botforge MCP Server manages your entire conversational AI backend from one place. You connect this server to your agent so you can control bot status, manage leads, and track user interactions using simple commands. It’s how you run a whole operation without leaving your main workspace.
Listing All Chatbots (list_bots)
The list_bots tool gives you a complete inventory of every chatbot set up in your Botforge account. You call this when you need to see all the names and IDs associated with your bots. It's how you verify what’s running; it returns a full list, so you don’t have to guess which bot ID belongs to which department or function.
Checking Operational Status (get_bot_status)
The get_bot_status tool verifies if any specific chatbot is online and responsive. You pass in a unique chatbot ID, and the server reports its current operational state. This lets you know instantly if a bot is active, offline, or running into issues, so your agent can alert you before users get stuck.
Retrieving Form Field Samples (get_samples)
Before sending any lead data, you need to know what the form expects. The get_samples tool retrieves sample data and metadata for a bot's contact form. You use this to understand exactly how your bot structures its required fields—whether it needs an email address in a certain format or if the name field accepts special characters.
It’s crucial for making sure your submissions don't bounce back.
Submitting Contact Data (submit_contact)
The submit_contact tool sends structured lead or contact information directly to a bot's primary form for logging and processing. You provide specific details, like a name and an email address, and the server handles sending that data correctly through the designated bot engine. This is your mechanism for automated lead capture; you use it when you need to log a prospect without manual copy-pasting.
Monitoring Real-Time Events (subscribe_webhook)
The subscribe_webhook tool sets up real-time event monitoring across all connected bots. You subscribe your system to webhooks, which means you get immediate notifications every time a user interacts with any bot in your account. This gives you visibility into conversation flow—you know the second an interaction happens, letting you track usage metrics and spot trends right away.
019dd173-493a-7185-bf7d-d137f0bb1005 Here's how it actually works
The bottom line is you manage and monitor your whole conversational ecosystem using simple chat prompts instead of logging into a separate dashboard.
Subscribe to this server and provide your The Botforge API Key (you find this in your account dashboard).
Connect the server to your preferred AI client (Claude, Cursor, etc.).
Use natural conversation commands—like 'List all bots' or 'Check status for bot X'—to execute tools.
Who is this actually for?
Support managers who are tired of manually checking dashboards for bot uptime. Marketing leads who need to automate lead capture without building custom web forms. And developers who just want a simple way to test and verify complex chatbot integrations.
Uses list_bots and get_samples to quickly audit the bot landscape, verifying form field structures before coding.
Monitors overall bot health using get_bot_status across multiple bots, ensuring zero downtime for critical customer channels.
Automates lead capture by calling submit_contact, feeding external source data directly into the bot system.
What Changes When You Connect
Instant visibility into your whole setup. Instead of clicking through multiple dashboards, use list_bots to get an immediate inventory of all chatbots in one chat command.
Eliminate manual lead entry. Use submit_contact to send external data directly to the bot's form. It’s perfect for automated lead capture from a CRM or spreadsheet.
Know your schema before you build. The get_samples tool lets you pull sample data and inspect required fields, so you never guess what structure your bot needs.
Never miss an interaction. With subscribe_webhook, you get real-time event alerts on user activity. You monitor everything without leaving your main workspace.
Quickly diagnose issues. If a bot goes down, use get_bot_status to check its live status immediately. It's fast debugging with zero effort.
See it in action
Auditing Bot Health After an Update
A support manager just pushed a major update and needs to know if all 15 bots are still online. They use the agent to run list_bots first, then loop through the IDs using get_bot_status. This verifies bot uptime across the entire fleet in minutes.
Automating Lead Funnel Input
A marketing team captures leads from a third-party survey tool. Instead of manually entering data, they pipe the JSON payload into submit_contact. This guarantees every lead hits the bot engine correctly and instantly.
Debugging Webhook Failures
A developer suspects their webhook connection is failing intermittently. They use subscribe_webhook to confirm that the system receives event data in real-time, immediately isolating whether the problem is on the client side or the bot's end.
Verifying Form Data Requirements
A developer needs to write code that sends contact details but isn't sure if the bot requires a phone number. They run get_samples first, which pulls the metadata, confirming they must include a phone field.
The honest tradeoffs
Assuming all bots are online
The user sees an error message that 'something is wrong' but doesn't know which bot or why. They try to solve it by just re-running the connection command.
First, use list_bots to get a full inventory of IDs. Then, systematically check each one using get_bot_status. This tells you exactly which bot is failing and why.
Sending bad data formats
A user tries to submit contact info but forgets the required JSON structure for first name or email, causing the submission tool to fail silently.
Before submitting, always run get_samples to verify the exact schema and field names. This guarantees your payload matches what the bot is expecting.
Over-relying on manual monitoring
The user manually checks a dashboard every hour for activity, wasting time and missing peak interaction moments.
Use subscribe_webhook once. This sets up persistent, real-time listening so you get instant alerts the moment any bot receives an interaction.
When It Fits, When It Doesn't
Use this server if your main job involves coordinating multiple chatbots or managing a complex lead flow from external systems into conversational AI. You need to monitor uptime (get_bot_status), understand data requirements (get_samples), and automate submissions (submit_contact).
Don't use it if you just need basic information, like checking the status of a single, known bot—some general monitoring tools might suffice. More importantly, don't use this if you are only building simple FAQs that never change; those systems probably don't require this level of deep operational integration.
When in doubt about data structure or uptime, always check get_samples and list_bots first. They provide the foundational context needed for reliable automation.
Questions you might have
How do I check if my bot is online using get_bot_status? +
You call get_bot_status and provide the specific Bot ID. The tool returns its current status—'Online,' 'Offline,' or 'Maintenance.' This tells you immediately if it's responsive.
What is the best way to automate lead capture with submit_contact? +
The submit_contact tool requires structured JSON data. Always use get_samples first to confirm the exact field names (like 'email' vs. 'user_email') your bot expects.
Can I track all user interactions in real time using subscribe_webhook? +
Yes, running subscribe_webhook links your system to the bot engine events. You get immediate notifications for every single user interaction across your entire fleet.
How do I list all my existing chatbots? Use list_bots. +
Just ask the agent to run list_bots. It immediately returns a complete inventory of every bot ID and name you've configured in The Botforge account.
Before I run `list_bots`, what credentials do I need to connect my agent? +
You'll need your The Botforge API Key. This key, found in your account dashboard, authenticates your connection and grants your AI client the permissions required to manage all listed bots.
How do I use `get_samples` to understand my bot’s expected data format? +
It returns sample data and field configurations for your specific bot. Use this output to build accurate JSON payloads, ensuring that the keys and required types match exactly what the bot expects.
If I use `submit_contact` with bad data, how do I handle validation errors? +
The tool returns a structured error message when submission fails. Always check the response payload for specific field violations—for instance, an invalid email format or missing required fields—and adjust your input accordingly.
Does `get_bot_status` help me monitor if my bot is running slowly or hitting rate limits? +
It confirms operational status and responsiveness. While it doesn't track load history, continuous performance issues will result in a non-optimal response time or an explicit throttling error code within the API output.
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.
We've already built the connector for The Botforge. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 5 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.