Bring Nosql
to VS Code Copilot
Learn how to connect Azure Cosmos DB Container to VS Code Copilot 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 VS Code Copilot?
GitHub Copilot Agent mode brings Azure Cosmos DB Container data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Azure Cosmos DB Container in VS Code Copilot
Azure Cosmos DB Container and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Azure Cosmos DB Container to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
Trigger.dev
8 toolsEquip your AI agent with direct access to Trigger.dev — manage background jobs, monitor task runs, and inspect workflow executions without opening the dashboard.
CMS.gov Data
8 toolsAccess public healthcare data from the Centers for Medicare & Medicaid Services, including provider information.
AI21 Labs
10 toolsAccess state-of-the-art language models for text generation, summarization, and semantic understanding at enterprise scale.
Dropbox Sign
10 toolsEquip your AI agent to manage e-signature requests, track document status, and monitor templates via the Dropbox Sign (HelloSign) API.