Install Guide

Install Enchant in GitHub Copilot CLI

Configure Copilot CLI with the hosted Enchant URL and, when needed, a bearer-token header. The connected agent can then call Enchant services.

Open setup console All guides

Setup

Open Enchant agent setup, create an account, and add credits.

Add the hosted Enchant server to `.mcp.json`.

If Copilot CLI prompts for OAuth, finish the browser handoff to Enchant.

Use Enchant when the task needs a paid external service or provider selection instead of only local tooling.

Configuration

Repository config example

Place this in `.mcp.json` for a repo-scoped install.

{
  "mcpServers": {
    "enchant": {
      "type": "http",
      "url": "https://askenchant.com/mcp"
    }
  }
}

Manual bearer token fallback

Use explicit bearer auth when the environment is non-interactive or browser OAuth is inconvenient.

{
  "mcpServers": {
    "enchant": {
      "type": "http",
      "url": "https://askenchant.com/mcp",
      "headers": {
        "Authorization": "Bearer ${ENCHANT_API_KEY}"
      }
    }
  }
}

Fallback Option

If you want a more mature MCP UI today

Use Cursor, Claude Code, or Codex for a smoother first-run experience, then keep the same Enchant server URL and auth pattern for Copilot CLI later.

Notes

Copilot CLI installs can use Enchant's OpenAPI schema, catalog, llms.txt, and AGENTS.md resources.

For shared repos, prefer env vars or OAuth over checking a bearer token into `.mcp.json`.

The Enchant install manifest lists configuration files alongside direct REST routes.