Compatible with every major AI agent and IDE
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 Claude Desktop?
Claude Desktop is the definitive way to connect Coder (Remote Dev) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 84 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Coder (Remote Dev) in Claude Desktop
Coder (Remote Dev) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Coder (Remote Dev) to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.
Explore More MCP Servers
View all →
Miro
14 toolsManage Miro boards, items and comments via API — create boards, add sticky notes, browse items and manage members from any AI agent.

Teambition
10 toolsCollaborative project management platform by Alibaba — manage tasks, projects, and team workflows via AI.

Pipedrive CRM (Full)
11 toolsManage deals, contacts, organizations, activities, notes, and pipelines — complete Pipedrive CRM access through natural conversation.

Microsoft Teams Webhook Notifier
1 toolsThis MCP does exactly one thing: it sends messages to your Microsoft Teams channels. That's its only function, and nothing else. Incredible for giving your AI agents a voice.
