Confirm the ChatGPT workspace has custom remote MCP connector support enabled.
ChatGPT requires a hosted MCP server with OAuth metadata, protected-resource discovery, and browser sign-in. Enchant provides each of those connection details for custom connectors.
Confirm the ChatGPT workspace has custom remote MCP connector support enabled.
Import the Enchant MCP server URL in ChatGPT's connector settings or app configuration flow.
Complete the browser OAuth handoff to your Enchant account.
Enable the connector in chat or deep research so ChatGPT can call Enchant tools when needed.
ChatGPT should discover OAuth metadata from the hosted MCP server and protected-resource metadata routes.
https://askenchant.com/mcpUse this pattern when testing remote MCP servers through the API or deep research tooling.
{
"type": "mcp",
"server_label": "enchant",
"server_url": "https://askenchant.com/mcp",
"require_approval": "never"
}Use Codex, Claude Code, or Cursor first. Enchant's MCP server is ready for hosted OAuth, but ChatGPT availability still depends on workspace settings and rollout state for custom connector installs.
ChatGPT's MCP support is best for hosted remote servers rather than local stdio installs, which matches Enchant's design.
OAuth is the intended auth path here. Unlike coding CLIs, ChatGPT is not the place to rely on a manually pasted bearer token.
For API-based testing, remember that MCP tools used in deep research need the approval mode and tool policy you expect.