Skip to content
aheldocs

Type to search every page. Use the arrow keys to move and Enter to open.

    Reference and troubleshooting · Reference

    Connector and client reference

    The ahel connector address, how AI tools sign in to it, workspace selection, app addresses, supported tools and the errors they can show.

    The facts about the connector, in one place. For step-by-step setup, see Connect your AI.

    Addresses

    AddressWhat it is
    https://mcp.ahel.aiThe ahel connector. Serves every app that is on in your workspace.
    https://mcp.ahel.ai?workspace= followed by your workspace's codeThe same connector, pinned to one workspace. Copy it from Connect your AI; you never need to type the code.
    https://mcp.ahel.ai/apps/ followed by an app's nameOne Studio app on its own.
    Your own subdomainA Studio app on your own domain, on Launch and Team.

    Without a workspace in the address, the connector uses the first workspace you joined.

    How AI tools sign in

    The connector is a remote MCP server over Streamable HTTP, and AI tools sign in to it with OAuth. You never paste an ahel key into a tool.

    1. The tool calls the connector and is told to sign in. The answer points it to the sign-in details at https://mcp.ahel.ai/.well-known/oauth-protected-resource.
    2. The tool registers itself. No manual setup is needed for tools that support dynamic client registration.
    3. Your browser opens ahel's consent screen, which lists what the tool "will be able to" do and what it "will never be able to" do. You press Allow or Not now. ahel always shows this screen, even if the tool did not ask for it.
    4. The tool gets a short-lived token and renews it on its own. If renewing fails, sign in from the tool again.

    Supported tools

    Claude shows your apps as cards. ChatGPT works through Developer mode, on plans that allow custom apps; we have not verified cards there yet. Cursor, Claude Code and Codex get complete text.

    ToolSetupShows
    ClaudeCustom connectorCards, with complete text
    ChatGPTDeveloper mode, on plans that allow custom appsComplete text. Cards not yet verified
    CursorInstall link or MCP settingsComplete text
    Claude Codeclaude mcp add commandComplete text
    Codexcodex mcp add commandComplete text
    VS CodeInstall link or .vscode/mcp.jsonWorks. Cards not yet verified
    Another MCP toolRemote server with OAuthComplete text

    Errors a tool can show

    What the tool reportsMeaningWhat to do
    Needs authentication, or HTTP 401The tool is not signed in, or its sign-in endedSign in again from the tool
    "This sign-in has no seat in the selected workspace"The address names a workspace you are not a member ofUse the address from Connect your AI in your own workspace, or ask for an invite
    "This workspace is over its seat limit"More members than the plan's seatsThe owner adds seats or removes members
    The workspace is suspended (HTTP 403)The connector is off for this workspaceGet help
    "Too many requests. Try again in" a few seconds (HTTP 429)A requests-a-minute or calls-a-day limit was reachedWait and try again; see Plans, limits and usage
    "This app has reached its monthly request pool."A public app used its owner's monthly poolTry again next month, or tell the app's owner
    Usage unavailable (HTTP 503)ahel could not check usage for a momentTry again shortly

    What the connector never does

    • It never sends an app key to the AI tool. Keys are added on the server when a call runs.
    • It never runs a change without a person's press. See Confirm, receipts and approvals.

    Last updated 5 October 2026