VS Code / Copilot

VS Code / Copilot

Connect VS Code and GitHub Copilot to the active workspace by adding
Twelfth as an MCP server. The connection
reads by default and changes nothing unless you turn on Allow changes. Reach it from Settings → AI & agents → VS Code / Copilot.

Connect

The simplest route needs no key: in Twelfth, open Settings → AI & agents → Settings
and select Install in VS Code under Developer tools. VS Code opens with
Twelfth filled in. Sign in when it asks, then choose the workspace and tools.
The steps below use a workspace key instead, for owners and
admins who need one.

  1. In Twelfth, open Settings → AI & agents, go to the Settings tab and, under API keys, choose Connect an agent → VS Code / Copilot. Twelfth creates a key for this connection, copies it to your clipboard, and starts waiting for VS Code / Copilot’s first request. Copy the key now if you need it again, because Twelfth shows it only once.
  2. In VS Code’s MCP configuration, add a server pointing at the Twelfth endpoint shown on the connection’s row, with the key Twelfth just copied for you.
  3. Reload VS Code’s MCP servers, then ask Copilot to list Twelfth’s tools to confirm the connection.

Follow the exact steps on the connection’s row in Twelfth. It carries the current
endpoint and the ready-to-paste MCP server entry for your workspace.

GitHub Copilot CLI

Copilot CLI installs Twelfth as a plugin from the open-source
twelfth-ai/twelfth-mcp repository.
The plugin adds the Twelfth server and a skill that helps Copilot use its tools.

copilot plugin marketplace add twelfth-ai/twelfth-mcp
copilot plugin install twelfth@twelfth

Run copilot mcp list to confirm: twelfth appears under plugin servers.
The first time Copilot calls a Twelfth tool, it sends you to Twelfth to sign
in, choose the workspace and approve the read tools. No key is involved.

Previous Cursor Next Generic MCP