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 Cursor?
Cursor's Agent mode turns Deno Deploy into an in-editor superpower. Ask Cursor to generate code using live data from Deno Deploy and it fetches, processes, and writes. all in a single agentic loop. 15 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
Deno Deploy in Cursor
Deno Deploy and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Deno Deploy 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 Deno Deploy in Cursor
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 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
Deno Deploy for Cursor
Every tool call from Cursor 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.
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 →
Exchange Rates API
7 toolsEquip your AI agent to access real-time and historical foreign exchange rates via the ExchangeRatesAPI.io service.

Leiga
8 toolsManage agile projects with AI-assisted sprint planning, task prioritization, and team workload balancing that adapts in real time.

Bitso Exchange
12 toolsTrade dynamically on Mexico's biggest Crypto Exchange. Access live balances, order books, and command trades programmatically.

Metaplane
10 toolsData observability via Metaplane — track monitors, incidents, and data quality metrics.
