Bring Thinkstack
to Cursor
Learn how to connect ThinkStack to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ThinkStack MCP Server?
Connect your ThinkStack account to any AI agent and manage your chatbots, knowledge bases, and conversations through natural language.
What you can do
- Chatbot Management u2014 List and configure all AI chatbots in your account
- Knowledge Base u2014 Add, list, and remove knowledge sources (URLs, documents) for any chatbot
- Live Queries u2014 Send messages to your chatbots and receive AI-generated responses in real time
- Conversation History u2014 Review all chat sessions with full message history and user metadata
- Actions & Webhooks u2014 View all configured REST API actions for your chatbots
How it works
1. Subscribe to this server
2. Retrieve your API Key from the ThinkStack dashboard
3. Start managing chatbots from Claude, Cursor, or any MCP client
Who is this for?
- Support Teams u2014 monitor chatbot conversations and optimize knowledge base accuracy
- Product Managers u2014 review chatbot usage patterns and refine AI responses
- Developers u2014 manage knowledge sources and test chatbot queries programmatically
Built-in capabilities (10)
The content will be crawled and indexed automatically. Add a knowledge source
Verify ThinkStack API connectivity
Remove a knowledge source
Get chatbot details
Get conversation details
List bot actions
List all chatbots
List conversations
List knowledge sources
Query a chatbot
Why Cursor?
Cursor's Agent mode turns ThinkStack into an in-editor superpower. Ask Cursor to generate code using live data from ThinkStack and it fetches, processes, and writes. all in a single agentic loop. 10 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
ThinkStack in Cursor
ThinkStack and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ThinkStack 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 ThinkStack in Cursor
The ThinkStack 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 10 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
ThinkStack for Cursor
Every tool call from Cursor to the ThinkStack 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 query my chatbot via AI agent?
Use the send_query tool with the bot ID and your message. The chatbot responds based on its trained knowledge base.
Can I manage knowledge sources programmatically?
Yes. Use add_source to add new URLs, list_sources to browse, and delete_source to remove outdated sources from any chatbot.
How do I review chat conversations?
Use list_conversations to see all chats for a bot, then get_conversation to read the full message history of any specific session.
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.