Connect Copilot CLI

Connect Copilot CLI to your workspace memory. The server is https://agentics.you/mcp, named agentics in every tool, so an admin can allowlist one name.

One click from the desktop app

In the Agentics desktop app, Connect your agents lists Copilot CLI with its state. Nothing changes until you confirm.

1. Click Connect. Before anything changes, the app shows what it will do: “Make an agent key on agentics.you for your own Copilot CLI agent, then add Agentics to Copilot CLI for your user: copilot mcp add writes the entry with Bearer pending, and Agentics puts the key in its place in ~/.copilot/mcp-config.json, which it makes readable by you only.” With it are the command it runs and the file it changes.
2. Click Confirm. The app saves a backup of the file beside it (<file>.agentics-backup-<timestamp>, readable by you only), runs copilot mcp add --transport http --header 'Authorization: Bearer pending' agentics https://agentics.you/mcp, then runs copilot mcp list to check that agentics is there.

If Copilot CLI isn't installed, its row says so and offers nothing to click. Once it has agentics, the row says Connected and offers Disconnect.

The app is for macOS and Windows. Get it from Download, which lists each build once a release is published.

By hand

Copilot CLI sends an agent key instead of signing in. First create one for your Copilot CLI agent under API keys, Agent keys: it is shown once.

Then run this in a terminal. It is the command the app runs, and it writes Authorization: Bearer pending where the key goes, so the key is never on a command line:

copilot mcp add --transport http --header 'Authorization: Bearer pending' agentics https://agentics.you/mcp

The quotes are for a macOS or Linux shell.

In ~/.copilot/mcp-config.json, put the key in place of pending in mcpServers.agentics.headers.Authorization, then make the file readable by you only (chmod 600 ~/.copilot/mcp-config.json on macOS and Linux).

The entry it writes to ~/.copilot/mcp-config.json includes:

{
  "mcpServers": {
    "agentics": {
      "type": "http",
      "url": "https://agentics.you/mcp"
    }
  }
}

If COPILOT_HOME is set, the file is mcp-config.json in the folder it names.

~ is your home folder.

Sign in

Nothing more to sign in to: Copilot CLI sends its agent key. You can see and revoke the key in Agent keys on agentics.you.

A console API key (ak_…) does not work here. Production answers HTTP 401 {"error":"invalid_token"} to one.

Check it worked

Run copilot mcp list. It lists agentics at https://agentics.you/mcp.

Then ask your agent to use it:

remember answers with saved true and a receipt_hash. recall returns that memory in results. Open the verify_url: the check does not show the memory's text.

Disconnect

In the desktop app, click Disconnect, then Confirm. Remove agentics from Copilot CLI for your user with Copilot CLI's own remove command, then revoke its agent key on agentics.you. The backup Agentics keeps of the file leaves the key out.

By hand, run:

copilot mcp remove agentics

Then revoke its agent key under API keys, Agent keys.

If your organization manages Copilot CLI

Before it changes anything, the app reads these files. One that blocks agentics stops the connect: the row says “Blocked by your organization's policy” and names the file. One that already provides agentics means there is nothing to add. A file that exists but can't be read stops the connect too.

• GitHub Copilot's managed settings, which VS Code and Copilot CLI both apply. allowedMcpServers and deniedMcpServers list the servers that may run. The app looks at /Library/Managed Preferences/com.github.copilot.plist, /Library/Managed Preferences/%USER%/com.github.copilot.plist and /Library/Application Support/GitHubCopilot/managed-settings.json on macOS, HKLM\SOFTWARE\Policies\GitHubCopilot and %ProgramFiles%\GitHubCopilot\managed-settings.json on Windows and /etc/github-copilot/managed-settings.json on Linux.

What the app can't check

• Copilot CLI connects with an agent key, which a workspace admin signed in to this app can make.
• Copilot policies your organization sets on GitHub (its MCP registry and allowlist) aren't visible on this computer. Copilot CLI applies them when it starts agentics.

If it does not connect

More errors are on Connect any MCP client.