How to Use the Coder (Remote Dev) MCP in Claude Code
Manage Coder (Remote Dev) workspaces and inspect deployment stats directly from the Claude Code terminal.
Works with every AI agent you already use
…and any MCP-compatible client
Connect Coder (Remote Dev) MCP to Claude Code
Create your Vinkius account to connect Coder (Remote Dev) to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.
Headless Workspace Lifecycle Management
Controlling remote Coder developer environments from the command line is handled by Claude Code using `create_workspace` and `cancel_workspace_build`. This MCP Server spins up Coder boxes, checks build parameters using `get_workspace_build_params`, and tears them down inside the Claude Code session. You can pipe these Coder actions into shell scripts or run them in Claude Code CI/CD runs. The Claude Code terminal agent coordinates the entire Coder build and outputs clean status logs directly to stdout.
Command-Line Deployment Auditing with Claude Code
Monitoring Coder deployment configurations and active server metrics is driven in Claude Code by `get_deployment_config` and `get_deployment_stats`. Claude Code executes these queries via MCP to output Coder resource usage and active user statistics. Active Coder provisioner daemons are inspected using `list_org_provisioner_daemons`, while organization roles are listed with `list_org_roles`. You get a complete picture of your Coder cluster's health without leaving your Claude Code SSH session.
Terminal-Based Agent Debugging
Troubleshooting remote Coder workspace agent issues in Claude Code is managed through `get_agent_debug_logs` and `get_agent_logs`. Claude Code streams live Coder agent logs and parses system errors directly in your terminal buffer. Checking network routes via `get_agent_debug_magicsock` allows the agent to find Coder connection bottlenecks. You get instant diagnostics on failing Coder Tailscale nodes without running manual network probes in Claude Code.
Set up Coder (Remote Dev) MCP in Claude Code
Prerequisites
- Claude Code CLI installed (
npm install -g @anthropic-ai/claude-code) - Active Vinkius subscription with a valid endpoint token
- 1
Run the add command
Open your terminal and run the command shown on the right. Replace
[YOUR_TOKEN_HERE]with your endpoint token from cloud.vinkius.com. Use--scope userto make it available across all projects. - 2
Verify the connection
Start a Claude Code session and type
/mcpto list connected servers. You should seecoder-remote-dev-mcpwith a green status indicator. - 3
Start using tools
Ask Claude Code something like "Check my latest Coder (Remote Dev) transactions." It will automatically discover and invoke the available Coder (Remote Dev) tools.
claude mcp add --transport http coder-remote-dev-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Why Choose Vinkius
Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.
Real-time monitoring
Live
visibility into every interaction
Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.
Built-in savings
60%
lower AI costs
Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.
Single dashboard
One
place for every integration
Every tool your AI connects to, managed from a single screen. One account, complete control.
Common questions about Coder (Remote Dev) MCP in Claude Code
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
Start using the Coder (Remote Dev) MCP today
We host it, we monitor it, we maintain it. You just paste one token.