
### GitHub Copilot CLI

Auth: OAuth browser login with your meinKontext account or an agent profile. [Choose access](/docs/agents).

1. With a current Copilot CLI installed and signed into GitHub, run the command below. Alternatively, enter `/mcp add` in Copilot and select HTTP with the same URL.
2. Open `/mcp` to inspect the connection. When authentication is needed, use `/mcp auth meinkontext` and complete the browser login.
3. Ask: “Use meinKontext to list my available context objects. Do not change anything.” Verify the actual `list_objects` call and result.

```bash
copilot mcp add --transport http meinkontext https://meinkontext.de/mcp
```

- Caveat: The user configuration is `~/.copilot/mcp-config.json` and uses `mcpServers`. Copilot CLI does not read VS Code's `.vscode/mcp.json`. [CLI setup](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/add-mcp-servers).
- Caveat: A `needs-auth` status requires fresh authorization through `/mcp auth meinkontext`. Do not paste a bearer into command arguments or configuration files. [CLI authentication reference](https://docs.github.com/en/copilot/reference/copilot-cli-reference/cli-command-reference).
- Caveat: Check organization MCP policy if the server is unavailable. Missing tools can reflect profile access; an empty object list can be valid. Reconnect after server-side tool or instruction changes.
- Caveat: For [VS Code](/docs/connect?client=copilot-vscode) and the [GitHub cloud agent](/docs/connect?client=copilot-cloud), use their separate instructions.
- Caveat: Researched on 31 October 2026 from official documentation; native Copilot login/tool calls and proactive skill or memory adoption have not yet been verified.