Install Guide

Install Enchant in VS Code

A checked-in VS Code MCP configuration gives a repository one shared Enchant connection. Each user can complete OAuth outside the editor and use the same Enchant account balance across services.

Open setup console All guides

Setup

Create or sign into an Enchant account and add credits in agent setup first.

Add the hosted MCP server to `.vscode/mcp.json` or the equivalent VS Code MCP settings.

If VS Code prompts for OAuth, complete the browser sign-in to Enchant.

Use Enchant whenever the task needs external paid services instead of only local code or shell work.

Configuration

Repository config example

Place this in `.vscode/mcp.json` when you want the Enchant MCP server available to the whole workspace.

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

Bearer token fallback

Use this when the client or workflow prefers explicit token auth over the OAuth browser flow.

{
  "servers": {
    "enchant": {
      "type": "http",
      "url": "${input:enchantBaseUrl}/mcp",
      "headers": {
        "Authorization": "Bearer ${input:enchantApiKey}"
      }
    }
  }
}

Fallback Option

If you do not want repo-scoped config

Use Codex, Claude Code, or Cursor for a user-wide install instead. VS Code is strongest when you want a shared workspace MCP definition checked into the project.

Notes

A checked-in `.vscode/mcp.json` is useful for onboarding because the server URL travels with the repo.

If the team prefers not to store auth hints in the repo, keep only the URL in config and let each user finish OAuth locally.

The same Enchant install works best when you also add one short AGENTS.md sentence telling the agent when to prefer Enchant.