How to Use the Coder (Remote Dev) MCP in Claude

Q: How do I link Coder (Remote Dev) to Claude Desktop?

Add the server configuration to your claudedesktopconfig.json file. Include the specific command and arguments required to initialize the connection.

Q: Can Coder (Remote Dev) manage my Claude Desktop workspace ports?

Yes, you can use createworkspaceportshare to expose your running services. This allows you to share workspace access through your agent.

Manage your Coder (Remote Dev) workspaces directly inside Claude Desktop for faster environment control.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Coder (Remote Dev) MCP to Claude Desktop

Create your Vinkius account to connect Coder (Remote Dev) to Claude Desktop and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Coder (Remote Dev) with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Full workspace lifecycle control

Start and stop your development environments without leaving your editor. Use `create_workspace` to spin up new instances or `cancel_workspace_build` when you need to kill a stuck deployment. Your agent handles the heavy lifting by calling `get_workspace` to fetch metadata. You get instant visibility into your infrastructure status right in your chat window.

Active session management

Keep tabs on what your agents are doing in real-time. Use `get_agent_logs` to stream output directly to your chat or `get_agent_containers` to see what is currently running. This MCP Server lets you debug issues by pulling `get_agent_debug_logs`. You no longer need to switch tabs to track down why a container failed to start.

Organization and user auditing

Check on your team's deployment health without opening the dashboard. Run `get_insights_daus` to see active user counts or `get_audit_logs` to review recent activity. Managing team access is simple with tools like `list_users` and `list_groups`. Your agent keeps you updated on organizational changes through direct API interactions.

Setup guide

Set up Coder (Remote Dev) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Coder (Remote Dev) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Coder (Remote Dev) MCP configuration

Copy the JSON snippet on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under coder-remote-dev-mcp.

json

{
  "mcpServers": {
    "coder-remote-dev-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Coder. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Coder (Remote Dev) now

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 Desktop

Add the server configuration to your `claude_desktop_config.json` file. Include the specific command and arguments required to initialize the connection.

Yes, you can use `create_workspace_port_share` to expose your running services. This allows you to share workspace access through your agent.

It runs locally as a subprocess via stdio. This ensures your development environment remains responsive while you chat with your agent.

The server only touches workspace metadata, logs, and user configuration. It never transmits your private source code to unauthorized endpoints.

Use the hammer icon in your chat interface to verify that the tools are active. If they are, you can query your deployment stats immediately.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.