Bring Nosql
to Cursor
Learn how to connect Azure Cosmos DB Container to Cursor and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Azure Cosmos DB Container MCP Server?
This server strips away dangerous global Azure permissions. It gives your AI agent one surgical superpower: the ability to query, insert, and update documents inside one specific Cosmos DB Container.
By strictly scoping access, your AI can safely manage structured data, store chat histories, and process complex NoSQL queries without ever touching your critical cloud databases.
The Superpowers
- Absolute Containment: The agent is locked to a single container. It cannot list other databases or drop your production data.
- Native Cosmos DB Integration: Direct interactions with Cosmos DB, supporting rich SQL queries and partition management.
- Plug & Play Database: Instantly gives your agent a scalable NoSQL database to store structured memories and application state.
Built-in capabilities (4)
Make sure to provide the ID and Partition Key properties inside the documentJson if required. Create a new document in the Cosmos DB Container
Provide partitionKey if your container requires it. Delete a document from the Cosmos DB Container
Provide partitionKey if your container requires it. Retrieve a specific document by its ID
You can optionally provide parameters in JSON format. Do not include the DB or Container name in the query, Cosmos expects queries like "SELECT * FROM c WHERE c.status = @status". Execute a SQL query against the configured Cosmos DB Container
Why Cursor?
Cursor's Agent mode turns Azure Cosmos DB Container into an in-editor superpower. Ask Cursor to generate code using live data from Azure Cosmos DB Container and it fetches, processes, and writes. all in a single agentic loop. 4 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
Azure Cosmos DB Container in Cursor
Azure Cosmos DB Container and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Azure Cosmos DB Container 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 | 4,000+ 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 Azure Cosmos DB Container in Cursor
The Azure Cosmos DB Container 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 4 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
Azure Cosmos DB Container for Cursor
Every tool call from Cursor to the Azure Cosmos DB Container MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Why limit the agent to a single Cosmos Container?
To enforce zero-trust security. An autonomous AI agent should not have the ability to read or delete data across your entire Cosmos DB Account (which might include user passwords, financial records, etc.). By scoping it to a single container, you eliminate the risk of catastrophic data loss.
How do I write Cosmos SQL queries here?
You don't need to specify the database or container in the query. Just use the standard alias c. For example: SELECT * FROM c WHERE c.isComplete = false. You can also pass parameters securely.
Do I need to handle Partition Keys?
The query tool automatically enables cross-partition queries to simplify AI workflows. However, for getting, creating, or deleting specific documents, you should provide the partitionKey if your container is configured to require one.
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.
Explore More MCP Servers
View all →
Jasper
10 toolsEquip your AI agent with direct access to Jasper — generate marketing copy, manage brand voices, and orchestrate content campaigns without opening the Jasper app.
YAML/JSON Converter
1 toolsPrevent DevOps YAML hallucination. Convert complex YAML files to JSON for safe AI processing, and back to perfect YAML.
Groq
8 toolsEmpower LLM applications via Groq — perform ultra-fast LPU-accelerated chat completions, handle audio transcription and translation, and use JSON mode directly from any AI agent.
Prowlarr (Indexers)
8 toolsManage Prowlarr indexers—list, add, test, and monitor health status of your Usenet and Torrent indexers directly from your AI agent.