Connect VS Code

← Agents

Sign-in not yet verified: VS Code 1.106 and later support Client ID Metadata Documents (CIMD), the client registration method Monomer uses, but Monomer sign-in has not been tested with VS Code. If VS Code asks for a Client ID or reports unsupported registration, stop and contact Monomer. Use only the client registration details supplied by Monomer.

This guide covers GitHub Copilot in VS Code. Copilot CLI versions 1.0.83 and later also support CIMD, but Monomer sign-in has not been tested with them. Copilot cloud agent does not support remote MCP servers that use OAuth, so it cannot connect to Monomer.

Add the server

1. In VS Code, run MCP: Open User Configuration from the Command Palette. For a project-specific setup, use .vscode/mcp.json instead.
2. Add monomer under servers, preserving existing entries:

{
  "servers": {
    "monomer": {
      "type": "http",
      "url": "https://api.monomer.cc/mcp"
    }
  }
}

3. Run MCP: List Servers, select Monomer, and start it. Review the server trust prompt if shown.
4. If OAuth is offered, complete the Monomer sign-in flow.
5. Open GitHub Copilot Chat in Agent mode and select Monomer’s tools.

See VS Code MCP setup for configuration and tool controls. MCP access may be restricted by your organization.

The VS Code 1.106 release notes describe automatic CIMD sign-in, used instead of dynamic client registration when the authorization server supports CIMD, as Monomer does. Earlier VS Code versions do not support CIMD, so update VS Code before connecting.

Verify

Only after OAuth completes, run the Workspace access check in Agent chat. Follow troubleshooting for other connection problems.

No successful Monomer OAuth test is claimed for VS Code.

After connecting, follow Direct your agent to read resources, follow availableOperations, and fetch input schemas with monomer_describe.