Bring Aidbase
to Cursor
Learn how to connect Aidbase to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Aidbase MCP Server?
Connect your Aidbase account to any AI agent and take full control of your automated customer support and intelligent knowledge management workflows through natural conversation.
What you can do
- Chatbot Orchestration — List and manage all configured AI chatbots programmatically, retrieving detailed high-fidelity metadata and configuration settings in real-time
- Knowledge Graph Ingestion — Programmatically update what your AI knows by pushing new website URLs or injecting specific Q&A items into existing FAQs dynamically
- Conversational Intelligence — Send messages and retrieve high-fidelity AI responses from specific chatbots to test performance or integrate chat into custom workflows
- AI Email Inbox Management — Access and monitor your automated email responders and their assigned knowledge bases to ensure perfectly coordinated context application
- Operational Monitoring — Verify API connectivity and retrieve account-level status directly through your agent for instant performance reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Aidbase dashboard (Settings > API Keys)
3. Start orchestrating your customer service intelligence from Claude, Cursor, or any MCP client
No more manual logging into support portals to update FAQs or check bot logs. Your AI acts as your dedicated support engineer and knowledge architect.
Who is this for?
- Customer Support Leads — instantly update AI knowledge bases with fresh documentation using natural language commands
- Product Managers — monitor chatbot interactions and verify responder accuracy without leaving your workspace
- Developers — integrate high-speed AI support intelligence into custom internal tools through simple AI queries
Built-in capabilities (11)
Add FAQ to knowledge base
Add a website to knowledge base
Check API Status
Get Chatbot details
Get AI Inbox details
List Chatbot knowledge items
List all AI Chatbots
List Inbox knowledge items
List Email AI Inboxes
List all Knowledge items
Send a message to a Chatbot
Why Cursor?
Cursor's Agent mode turns Aidbase into an in-editor superpower. Ask Cursor to generate code using live data from Aidbase and it fetches, processes, and writes. all in a single agentic loop. 11 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
Aidbase in Cursor
Aidbase and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Aidbase 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 Aidbase in Cursor
The Aidbase 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 11 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
Aidbase for Cursor
Every tool call from Cursor to the Aidbase 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 Aidbase API Key?
Log in to your account, navigate to Settings > API Keys, and generate a new key for your integration.
Can I test bot responses via AI?
Yes! The send_aidbase_reply tool allows your agent to interact with specific bots and retrieve high-fidelity AI responses programmatically.
How do I teach the AI a new URL?
Use the add_aidbase_website_knowledge tool and provide the target URL. Aidbase will automatically crawl and index the content for your bots.
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.