Install Guide

Install Enchant in Cursor

Cursor's MCP support is built around mcp.json plus remote HTTP endpoints. That makes Enchant a good fit: one /mcp URL, one OAuth login, and one agent runtime that can discover many paid services without separate provider setup.

Open setup console All guides

Setup

Open Enchant agent setup and make sure the account has credits before adding the server.

Add the hosted MCP URL in Cursor's MCP settings or mcp.json.

If Cursor prompts for OAuth, finish the browser connection to Enchant.

If you use cursor-agent in the terminal, the same MCP config can be reused there.

Configuration

Global mcp.json example

Place this in ~/.cursor/mcp.json for a user-wide install, or in .cursor/mcp.json for a project-scoped install.

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

cursor-agent CLI login

Cursor's CLI uses the same MCP configuration as the editor and can trigger the same OAuth login flow.

cursor-agent mcp list
cursor-agent mcp login enchant

Manual bearer token config

Use this when you want an API-key-first install instead of the hosted OAuth flow.

{
  "mcpServers": {
    "enchant": {
      "url": "${ENCHANT_BASE_URL}/mcp",
      "headers": {
        "Authorization": "Bearer ${ENCHANT_API_KEY}"
      }
    }
  }
}

Fallback Option

If you want one-click distribution later

Cursor also supports marketplace listings and Add to Cursor links. Enchant currently provides the hosted MCP URL and install guides; a one-click installation can be added later.

Notes

Cursor supports Streamable HTTP MCP servers for both local and remote installs, which is the right transport for Enchant.

The same config works for the Cursor editor and cursor-agent CLI, so one install can cover both workflows.

If you share mcp.json in a repo, prefer env vars for tokens rather than checking secrets into the file.