> ## Documentation Index
> Fetch the complete documentation index at: https://smithers.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up with GitHub Copilot

> Connect Smithers to GitHub Copilot: no plugin exists, so we recommend registering the MCP server in VS Code (and in the cloud coding agent if you use it).

Copilot has no Smithers plugin, so we recommend the MCP server. Copilot has
two surfaces with different config formats (the in-editor agent in VS Code and
the autonomous cloud coding agent), so the simplest path is letting Copilot
write its own config.

## Install (recommended)

Paste this into Copilot Chat in your project:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Set up Smithers (a durable AI workflow orchestrator) in this repo:
run `bunx smithers-orchestrator init`, then register its MCP server for
Copilot by creating .vscode/mcp.json with a stdio server named "smithers"
running `bunx smithers-orchestrator --mcp` (see
https://smithers.sh/agents/copilot for the exact shape). From now on, use
Smithers for multi-step, long-running, or approval-gated work.
```

If you use the cloud Copilot coding agent too, the
[Technical API page](/agents/copilot) covers its separate MCP registration.

## Check it worked

Say:

> "What Smithers workflows are available here?"

Copilot should list them via the Smithers tools. From there, ask for outcomes
([What You Can Do](/guide/what-you-can-do)) and Copilot drives the runs.

<Note>
  The agent-facing details (both MCP schemas, custom instructions) live in the
  Technical API at [GitHub Copilot](/agents/copilot). You don't need them;
  Copilot does.
</Note>