# GitHub Copilot CLI

> Connect MCP Bond to the GitHub Copilot CLI.

## Quick setup

Follow the current, tested steps on [the GitHub Copilot CLI setup page](https://docs.valency.io/guides/microsoft/copilot-cli/). The sections below cover additional cases and troubleshooting.

**Prefer to set it up yourself?**

1. Check `copilot mcp list`. If it already lists Valency, including through a plugin, do not add another connection. Otherwise run:

   ```bash
   copilot mcp add --transport http valency https://mcp.valency.io/
   ```

   This saves Valency to your user-level Copilot CLI configuration.

2. Load the connection and sign in. If Copilot CLI is already open, exit it with `/exit` and run `copilot --continue` from the same terminal and directory to resume your conversation. Otherwise start it with `copilot`. Complete Valency browser sign-in if it opens automatically. If Valency still needs authorization and no browser opens, enter `/mcp auth valency` **at the Copilot CLI prompt**.

   A Valency account is created automatically on first sign-in. You do not need an API token, client ID, or secret, and your Valency email does not have to match your GitHub email.

3. Ask Copilot to call Valency's `list_sources` tool. A returned source list confirms that the agent can use the connection. `copilot mcp list` or `/mcp` showing Valency only confirms configuration.

4. Ask [(more prompt ideas)](https://docs.valency.io/reference/examples.md):

   > Use Valency to search for papers about quantum computing

:::tip[What success looks like]
You see paper results in your terminal, with sources you can inspect.
:::

:::caution[Copilot CLI only]
MCP Bond is supported in the Copilot CLI. The Copilot coding agent and Copilot code review do not currently support its remote OAuth MCP server.
:::

## Troubleshooting

**Tools don't appear after adding Valency?**
Run `copilot mcp get valency` to check its status. Resume the conversation with `copilot --continue` so it loads the server. If it needs authorization, enter `/mcp auth valency` after Copilot has finished its current turn.

**Need to start over with a direct connection?**
Run `copilot mcp remove valency`, then follow the add and sign-in steps above. This removes a user-configured server, not one supplied by a plugin.

---

## Need help?

If something isn't working, check [Troubleshooting](https://docs.valency.io/help/troubleshooting.md) for common fixes. See the [FAQ](https://docs.valency.io/help/faq.md) for general questions, or [report an issue](https://docs.valency.io/help/reporting-issues.md) if you're still stuck.