Compatible with every major AI agent and IDE
What is the Deno Deploy MCP Server?
Connect your Deno Deploy account to any AI agent to orchestrate your edge computing infrastructure through natural conversation. This server provides comprehensive tools for managing the lifecycle of your serverless applications.
What you can do
- App Management — List all applications within your organization, filter by labels, and fetch detailed configurations for specific apps.
- Deployment Lifecycle — Create new deployments (revisions) by uploading assets, and track their progress in real-time.
- Log Observability — Stream build logs for new revisions or query historical application logs with advanced filtering by level and time.
- Infrastructure Layers — Manage shared environment variables and configurations using layers to streamline multi-app setups.
- Domain & Project Insights — Inspect organization details, list associated domains, and manage project-specific deployments.
How it works
- Subscribe to this server
- Enter your Deno Deploy Personal Access Token
- Start deploying and monitoring your edge functions from Claude, Cursor, or any MCP client
Who is this for?
- DevOps Engineers — automate deployment pipelines and monitor system health without leaving the terminal or chat interface.
- Full-stack Developers — quickly check logs or deployment status while debugging code in the IDE.
- Platform Teams — manage organizational resources and shared layers across multiple projects efficiently.
Built-in capabilities (15)
Create a new Deno Deploy application
Create a new deployment (revision) for an app
Create a new layer for sharing environment variables
Create a deployment for a project (v1 API)
Get details for a specific Deno Deploy app
Query application logs
Stream build logs for a revision
Get organization details (v1 API)
Get status of a specific revision
Stream revision progress (SSE)
Supports pagination and label filtering. List Deno Deploy applications
List custom domains for an organization (v1 API)
List projects in an organization (v1 API)
List revisions for an app
Update an existing layer
Why VS Code Copilot?
GitHub Copilot Agent mode brings Deno Deploy data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 15 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
Deno Deploy in VS Code Copilot
Deno Deploy and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Deno Deploy 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 Deno Deploy in VS Code Copilot
The Deno Deploy 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 15 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
Deno Deploy for VS Code Copilot
Every tool call from VS Code Copilot to the Deno Deploy MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I check if my latest deployment was successful?
You can use the get_revision_progress tool with your Revision ID to stream the real-time status, or get_revision to fetch the final state of a specific deployment.
Is it possible to view runtime errors for my application?
Yes. Use the get_app_logs tool. You can filter by level (e.g., 'error') and set a query string to find specific issues within your application logs.
Can I manage environment variables across multiple apps?
Absolutely. Use the create_layer and update_layer tools to create shared configuration layers that can be attached to your Deno Deploy applications.
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 →
Northbeam
10 toolsAnalyze marketing attribution via Northbeam — track metrics, breakdowns, and data exports directly from your AI agent.

Aracaju
5 toolsAccess Aracaju's transparency data—revenues, expenses, bids, contracts, and payroll—directly from your AI agent.

Meshy (3D AI)
17 toolsTransform text and images into high-quality 3D models using Meshy's generative AI directly from your agent.

Flowise
7 toolsManage low-code AI workflows via Flowise — run predictions, track chatflows and agentflows, handle tools, and audit execution history directly from any AI agent.
