Enchant
Install Guide

Install Enchant in GitHub Copilot CLI

Copilot CLI's MCP config is close to the Cursor and Claude Code model: one hosted server URL, one optional bearer header, and one agent that can call many services through Enchant.

Open setup consoleBrowse all guidesTechnical reference
Recommended Setup

Start with hosted MCP first.

GitHub Copilot CLI can read `.mcp.json`, which makes Enchant a good fit for repo-local or user-local MCP installs.

01

Open the Enchant setup console, create an account, and add credits.

02

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

03

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

04

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

Configuration

Use the exact configuration this client expects.

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.

Operational Notes

Small details that make the setup reliable.

01

Copilot CLI style installs benefit from the same Enchant machine-readable surfaces: OpenAPI, catalog, llms.txt, and AGENTS.md.

02

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

03

The Enchant install manifest is useful here because it exposes both config artifacts and direct REST routes in one place.