Bring Remote Development
to Cursor
Learn how to connect Coder (Remote Dev) to Cursor and start using 84 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 Coder (Remote Dev) MCP Server?
Connect your Coder deployment to any AI agent to orchestrate remote development infrastructure and monitor workspace health through natural language.
What you can do
- Deployment Monitoring — Retrieve build info, deployment statistics, and check for available updates to keep your infrastructure current.
- AI Bridge Management — List connected AI clients, available models, and active sessions to understand how AI is being utilized in your workspaces.
- Agent Operations — Stream logs from specific workspace agents and manage application statuses to troubleshoot remote environments instantly.
- Infrastructure Config — Access SSH configurations and deployment settings to ensure seamless connectivity for your engineering team.
- Session Insights — Fetch threads and interceptions from AI sessions to audit and optimize AI-assisted development workflows.
How it works
- Subscribe to this server
- Enter your Coder URL and Session Token
- Start managing your remote dev clusters from Claude, Cursor, or any MCP-compatible client
Who is this for?
- DevOps Engineers — monitor deployment health and configuration without leaving the terminal or chat interface.
- Platform Teams — manage AI Bridge sessions and model availability across the organization's remote workspaces.
- Software Developers — quickly retrieve SSH configs and agent logs to debug environment issues without context switching.
Built-in capabilities (84)
Add an enterprise license
Authenticate agent using cloud provider identity
Cancel a pending or running build
Check if user has permission to perform actions
Start a new AI chat session
Send a message to a chat session
Create a group in an organization
Create an organization
Create a user
Create a user secret
Create a long-running AI task for a user
Create a user token
Create a workspace
Create a port share for a workspace
Delete an enterprise license
Delete a user
Download a file by ID
Get DERP and connection details for an agent
List running containers and devcontainers
Get the last 10MiB of agent logs (local agent API)
Get Tailscale magicsock debug info (local agent API)
Get the startup manifest from the server (local agent API)
Get external authentication tokens for the agent
Stream logs from a specific agent
Get threads for an AI session
Get basic API information
Redirect to a URI with an encrypted API key
Get the base host for applications
Get dashboard branding and banners
Get a paginated list of audit logs
Get Coder build info
Get messages for a chat session
Get deployment configuration
Get deployment statistics
Initiate device-based OAuth
Get Daily Active User stats
Get usage data for templates
Get activity duration per user
List user notifications
Get global notification settings
List available notification templates
Get prebuild settings
Get SSH configuration
Check for Coder updates
Get user profile
Get workspace metadata
Get workspace ACLs
Get details of a specific build
Get logs for a specific build
List parameters used for the build
List connected AI Bridge clients
List AI interceptions
List available AI models
List active AI Bridge sessions
List user chat sessions
List linked external accounts (e.g., GitHub)
List groups
List enterprise licenses
List members of an organization
List active provisioner daemons
List jobs for the organization provisioners
List assignable roles in an organization
List organizations
Manage long-running AI tasks
List starter template examples
List versions for a template
List all templates
List user secrets
List user tokens
List users
List port shares for a workspace
g., owner:me). List workspaces
Authenticate a user with email and password
Register a new log source
Send logs to the server
Update status of an application running on the agent
Update dashboard branding and banners
Update an organization
Update prebuild settings
Update user profile
Update workspace ACLs
Update workspace autostart schedule
Update workspace autoupdates schedule
Upload a file (tar or zip)
Why Cursor?
Cursor's Agent mode turns Coder (Remote Dev) into an in-editor superpower. Ask Cursor to generate code using live data from Coder (Remote Dev) and it fetches, processes, and writes. all in a single agentic loop. 84 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
Coder (Remote Dev) in Cursor
Coder (Remote Dev) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Coder (Remote Dev) 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 Coder (Remote Dev) in Cursor
The Coder (Remote Dev) 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 84 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
Coder (Remote Dev) for Cursor
Every tool call from Cursor to the Coder (Remote Dev) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I check the health and usage of my Coder deployment?
Yes. Use the get_deployment_stats tool to retrieve workspace and session statistics, providing a clear overview of your infrastructure's current state.
How do I see which AI models are available in my Coder instance?
Simply run the list_ai_models tool. It will return a list of all AI models currently configured and available through the Coder AI Bridge.
Can I view logs for a specific workspace agent to debug issues?
Yes! Use the get_agent_logs tool with the target agent_id. This allows you to stream and inspect logs directly from the remote environment.
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 →
Blip
10 toolsBuild intelligent chatbots for WhatsApp, Messenger, and web that engage customers with conversational commerce flows.
Foursquare Alternative
7 toolsManage your location data — audit places, photos, and tips via AI.
Mode (Collaborative Data Platform)
7 toolsManage collaborative analytics via Mode — list data reports, explore organizational spaces, and audit data sources.
Calendarific Alternative
2 toolsUniversal holiday intelligence — get public, bank, and religious holidays worldwide via AI.