Bring Llm Training
to Cursor
Learn how to connect Chaindesk 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 Chaindesk MCP Server?
Connect your Chaindesk.ai account to any AI agent and take full control of your custom LLM orchestration and automated knowledge retrieval workflows through natural conversation.
What you can do
- Agent Orchestration — Create and manage multiple high-fidelity AI agent instances programmatically, including configuring system prompts and model selection
- Knowledge Graph Ingestion — Programmatically upsert data sources (website URLs, text, documents) into connected datastores to maintain a real-time knowledge base
- Deep Semantic Querying — Interact with your custom agents to retrieve context-aware AI responses based on your proprietary data and high-fidelity grounding
- Conversation Intelligence — Access complete session histories and message threads to provide perfectly coordinated context for support and research tasks
- Datastore Monitoring — Access and monitor your directory of knowledge collections (datastores) and their status directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Chaindesk dashboard (Settings > API Keys)
3. Start building and querying your custom AI assistants from Claude, Cursor, or any MCP client
No more manual copy-pasting of text for bot training. Your AI acts as your dedicated agent engineer and knowledge architect.
Who is this for?
- Developers & Ops — integrate custom-trained AI models into internal tools and automate document ingestion using natural language commands
- Support Teams — monitor agent responses and update knowledge bases in real-time without leaving your workspace
- Product Leads — coordinate the deployment of specialized AI assistants for different business units through simple AI queries
Built-in capabilities (11)
Provide name, datastoreId, and system prompt. Create a new AI agent
Delete an agent
Get details of a specific agent
Get details of a datastore
Get messages from a conversation
List all AI agents
Can be filtered by agentId. List chat conversations
List all datastores
Send a message to an agent
Update an existing agent
Add or update a data source
Why Cursor?
Cursor's Agent mode turns Chaindesk into an in-editor superpower. Ask Cursor to generate code using live data from Chaindesk 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
Chaindesk in Cursor
Chaindesk and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Chaindesk 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 Chaindesk in Cursor
The Chaindesk 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
Chaindesk for Cursor
Every tool call from Cursor to the Chaindesk 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 Chaindesk API Key?
Log in to your Chaindesk.ai account, navigate to Settings > API Keys, and generate a new key for your integration.
What is a Datastore?
A Datastore is a collection of documents and URLs that your AI agent uses as its knowledge base to answer queries accurately.
Can I maintain conversation context via AI?
Yes! Provide a unique conversationId to the query_agent tool to maintain historical context across multiple turns with your custom bot.
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.