Open the Enchant setup console and make sure the account has credits before adding the server.
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.
Start with hosted MCP first.
Cursor supports remote Streamable HTTP MCP servers and OAuth, with mcp.json as the common install surface for editor and CLI.
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.
Use the exact configuration this client expects.
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'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 enchantUse 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}"
}
}
}
}If you want one-click distribution later
Cursor also supports a marketplace-style MCP discovery surface and Add to Cursor links. Enchant's current implementation gives you the hosted MCP URL and install guides first, and a dedicated one-click distribution path can sit on top later.
Small details that make the setup reliable.
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.