Source checked: 2026-06-19 Official source: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Claude web custom connectors require human app settings steps. Claude connects to remote MCP servers from Anthropic cloud infrastructure, so the server must be public HTTPS and reachable from Anthropic, not merely reachable from the user's laptop.
Core hosted remote MCP URL: https://core.gradien.ai/mcp
Recommended setup path:
- Fetch the current Claude custom connector documentation before giving UI-specific instructions, because Claude settings labels move.
- Hand the user the hosted URL directly:
https://core.gradien.ai/mcp. Hosted Claude setup is a settings-page connector flow, not a CLI install. - If the user wants a guided CLI walkthrough only for Core signup/session help, use
npx -y @gradien/core-agent-setup install --base-url https://core.gradien.ai --yes --harness claude-web, but still expect the final Claude settings step to be manual. - Do not omit the harness flag for Claude web when using the CLI; on machines with Codex installed, the CLI may otherwise detect Codex and configure the wrong app.
Human handoff:
- Open Claude in your browser.
- Open Settings or Customize.
- Go to Connectors.
- Choose Add custom connector.
- Enter name: Core.
- Paste this remote MCP server URL:
https://core.gradien.ai/mcp. - Approve the Core login or permissions screen.
For Team or Enterprise plans, an Owner may need to add the custom connector under Organization settings first; members then connect it individually from Customize -> Connectors.
If Claude says Authorization with the MCP server failed, do not ask the user to retry blindly. Fetch troubleshooting and check the protected-resource metadata, authorization-server metadata, dynamic client registration or configured OAuth client, redirect URI allowlist, scopes, and token audience.
After the user returns, ask them to start a new Claude chat if needed and verify that Core tools are available.
