Connect Claude

Connect Claude, then ask for one thing.

Add one connector in Claude's settings, approve one sign-in, and ask for a read you can check. The same connector also works in ChatGPT, Cursor, VS Code, Claude Code and Codex.

Your apps, skills and knowledge stay with your ahel account. Keys stay in the vault and never cross into the chat.

Before you start

Two things to have ready

  1. An ahel account with one app ready

    Sign in to ahel and connect the vendor account your first app needs, so there is something to read.

  2. A Claude account that allows custom connectors

    Your Claude plan and workspace must allow custom connectors. On a team plan an admin may control that. ahel cannot override Claude's account policy.

Phone or computer

Add ahel to Claude

Open Claude connectors

  1. In Claude, open Settings, then Connectors, and choose Add custom connector.
  2. Name it ahel and paste your connector address as the server URL:
    https://mcp.ahel.ai

  3. Choose Connect, then approve the ahel sign-in.

On a phone, do this at claude.ai in your browser.

Your first question

Ask for one read you can check

Start by asking what is connected, then ask for something you would recognise as right.

  • Check what is connected on ahel and show any setup still missing.

  • Using ahel, find the open tickets assigned to me.

The second question is an example: use a read from an app you have connected. No app yet? Bring one from your API or pick one from Discover.

When nothing runs

Signed in, but Claude never uses it

ahel runs the sign-in and the key vault, so you do not build that layer. When the sign-in finishes but Claude does not call ahel, check these in order.

  1. The connector is on in this chat

    A connector can be added but turned off for the conversation you are in. Check Claude's connector controls for this chat.

  2. The right workspace

    In more than one ahel workspace? Use the per-workspace link under Connect your AI in the app. Signing in once does not authorize every team.

  3. The app is ready

    Check the app's status in ahel. An installed app can still need a vendor sign-in or a key. Finish that in ahel's setup, never by pasting a key into the chat.

  4. Your Claude permissions

    On a team or enterprise plan, an admin setting can block custom connectors. Ask your admin rather than widening permissions or sharing credentials.

  5. A fresh tool list

    If the tools look out of date, remove the connector and add it again with the same address, then sign in once more.

Other AIs

What each AI shows

One connector address serves every AI below. What you see depends on the AI.

AIWhereWhat you see
ClaudePhone or computerCards
ChatGPTPhone or computerWorks. Cards not yet verified.
CursorComputerComplete text
VS CodeComputerWorks. Cards not yet verified.
Claude CodeComputerComplete text
CodexComputerComplete text

Questions

Everything else.

What address do I paste into Claude?

https://mcp.ahel.ai. Name the connector ahel, then approve the browser sign-in.

Does it work on a phone?

Yes. On a phone, do the setup at claude.ai in your browser.

Does ChatGPT show the same cards?

ChatGPT works through Developer mode, on plans that allow custom apps. Cards there are not verified yet.

Can Claude see my keys?

No. Keys are sealed in the vault and added on ahel's side. No tool on the connector reads or reveals a key.

Try Team for 14 days with no credit card. Your existing Free allowance applies during the trial, and it returns to Free on its own with nothing charged. Team adds the shared vault, approval rules and the audit log. See plans.

Add ahel to Claude.

One connector, one sign-in. Claude shows your apps as cards.