Set Up with GitHub Copilot

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:

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 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) and Copilot drives the runs.

The agent-facing details (both MCP schemas, custom instructions) live in the Technical API at GitHub Copilot. You don’t need them; Copilot does.

Set Up with Cursor

Set Up with Pi

Start here

Tutorials

Set up

How-to guides

Reference

Explanation

Compare

Set Up with GitHub Copilot

Install (recommended)

Check it worked

​Install (recommended)

​Check it worked

Install (recommended)

Check it worked