PlugWiki
Coder logo

Coder MCP Server: Setup for Claude, Cursor and Other Apps

OfficialLocal

Lets Claude, Cursor and other assistants manage Coder workspaces and templates, and edit files and run commands inside workspaces.

Coder has an MCP server built in, so you need a Coder deployment to use it. Run it on your computer with the Coder command line tool, or point your assistant at the address of your own deployment. Both sign in with your existing Coder account.

The tools can start and delete workspaces, delete templates, and run commands inside workspaces. The remote address needs an admin to turn on an experiment first.

Good for

  • Developers on a Coder deployment who want an assistant to create and manage workspaces
  • Platform teams who author and update Coder templates
  • Teams who delegate coding tasks to Coder Agents chats from their assistant

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Coder MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Coder MCP server to Claude Code. Run this command:
    
    claude mcp add coder -- coder exp mcp server
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Coder CLI, signed in with coder login.

Read-only mode: Add --allowed-tools followed by a comma-separated list of the tools to expose, for example coder_list_workspaces,coder_get_workspace. Only those tools are served.

Replace coder.example.com with your Coder deployment. The remote address needs the OAuth2 provider and the mcp-server-http experiment turned on by an admin, per Coder's docs.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists your workspaces

    Lists the workspaces of the signed-in user.

    Try: “List my Coder workspaces.”

    Read · coder_list_workspaces

  • Shows one workspace

    Returns the details of a workspace by name or ID, with more data than the list.

    Try: “Show the status of my dev workspace.”

    Read · coder_get_workspace

  • Creates a workspace from a template

    Creates a new workspace from a template. The tool description tells the assistant to confirm the template and settings with you first.

    Try: “Create a workspace from the Go template.”

    Write · coder_create_workspace

  • Starts, stops or deletes a workspace

    Creates a build for an existing workspace to start, stop or delete it. A start can use a preset or parameter overrides.

    Try: “Stop my dev workspace.”

    Delete · coder_create_workspace_build

  • Reads a workspace build log

    Returns the logs of a workspace build, to check whether it built.

    Try: “Why did my last workspace build fail?”

    Read · coder_get_workspace_build_logs

  • Reads a workspace agent log

    Returns the logs of a workspace agent. More logs may appear after the call.

    Try: “Show the agent logs for my workspace.”

    Read · coder_get_workspace_agent_logs

  • Lists templates

    Lists templates, and shows whether Coder Agents may create workspaces from each.

    Try: “What templates can I use?”

    Read · coder_list_templates

  • Shows a template and its presets

    Returns a template's details, parameters and presets for its active version.

    Try: “What parameters does the Go template take?”

    Read · coder_get_template

  • Lists template version parameters

    Returns the parameters of a template version, which are the workspace settings you choose when creating one.

    Try: “List the settings for this template version.”

    Read · coder_template_version_parameters

  • Creates a template version

    Creates a template version, the step before creating or updating a template. Templates are Terraform that define a development environment.

    Try: “Create a new template version from these files.”

    Write · coder_create_template_version

  • Uploads template files

    Creates and uploads a tar file from a map of file names to contents. It is used to build template versions.

    Try: “Upload these Terraform files for a new template.”

    Write · coder_upload_tar_file

  • Creates a template

    Creates a template from a template version.

    Try: “Create a template from the version I just uploaded.”

    Write · coder_create_template

From the official docs

Permissions

high risk · 4 things to watch

High risk

The assistant can create, stop and delete workspaces, delete templates, and run commands inside workspaces as you. Use the local server's allowed tools flag to expose only what you need.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can run commands inside your workspaces

    One tool runs shell commands, and others write files and signal processes in a workspace. Limit the tools with the local --allowed-tools flag if you only need reading. github.com

  • It can delete workspaces and templates

    A build can delete a workspace, and one tool deletes a template. The tool description calls template deletion irreversible. github.com

  • It acts with all your Coder permissions

    The server uses your signed-in account, so it can do what you can do. Use a limited account or token if you can. github.com

  • A session token in a config file is a secret

    The manual remote setup puts a token in the client config. Keep that file private and delete the token when done. github.com

Security advisories

No published security advisories for the MCP server as of Nov 1, 2026.

42 other advisories are about the wider coder project, not this MCP server. See them on GitHub

Technical details
Turning on read-onlyNo read-only mode. The local server takes an --allowed-tools flag that lists the only tools it will expose, which you can use to leave out write and delete tools.
Talks toYour Coder deployment
Sign-in and keysThe local server uses your existing coder login. The remote server uses OAuth2 sign-in, or a session token you create under Settings > Tokens and send in a header.
Scopes
  • Your Coder user permissions

Questions

Do I need my own Coder deployment?

Yes. The MCP server talks to a Coder deployment, either through the local Coder command line tool or through your deployment's own address.

What is the Coder MCP server URL?

It is your deployment's address plus /api/experimental/mcp/http, for example https://coder.example.com/api/experimental/mcp/http. An admin must first enable the OAuth2 provider and the mcp-server-http experiment.

Do I need an API key?

No for the local server, which uses your coder login. The remote server signs in with OAuth2, or with a session token from Settings > Tokens if your app cannot do OAuth2.

Can I limit which tools it exposes?

Yes for the local server. Pass a comma-separated list to its --allowed-tools flag and only those tools are offered.

Can it delete things?

Yes. It can delete workspaces and templates and run commands inside workspaces.

Is it a stable feature?

Not yet. The command is under the exp group and the remote address is under experimental, so details may change between releases.

Which tools do I get, and is the list complete?

It depends on your Coder version. This page follows the main branch, which has 39 tools. Release 2.38.5 has 38 and swaps the workspace execute and process tools for coder_workspace_bash, coder_workspace_edit_file and coder_report_task. Coder says tools can change between releases, so check the toolsdk source for yours.

Information

updated Nov 2, 2026

Publisher
Official
Transport
stdio, Streamable HTTP
Auth
OAuth
Version
2.38.5
License
AGPL-3.0
Last commit
Oct 31, 2026
Open issues
741
Listed in
Official MCP registry

WebsiteGitHubOfficial MCP RegistryChangelogIssues

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.