Connect Claude Code.

Add Ahel to Claude Code, then approve one browser sign-in.

Set up Claude Code

Needs a computer · Claude Code: Complete text

  1. Run this once in any terminal; it adds Ahel for every project:
    claude mcp add --transport http --scope user ahel 'https://mcp.ahel.ai'

  2. In Claude Code, open /mcp, select ahel, and approve the browser sign-in.

Your apps, skills and knowledge stay with your Ahel account. Part of a team on Ahel? This address connects your AI to the workspace you were invited to. In more than one? Connect your AI in the app has a link for each.

Connect

Do it from here

Choose your AI

Connect Ahel to Claude

Add Ahel once, then sign in to authorize access.

Open Claude connectors

First-time setup

  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.

Claude currently requires this initial setup. Opening it here does not create a connection.

Using Claude Code?

  1. Run this once in any terminal; it adds Ahel for every project:
    claude mcp add --transport http --scope user ahel 'https://mcp.ahel.ai'

  2. In Claude Code, open /mcp, select ahel, and approve the browser sign-in.

Secure browser sign-in. No API keys to paste.

Other AI clients

Use something else?

Questions

Everything else.

What is MCP?

The Model Context Protocol is the open standard AI clients use to reach tools and data. An MCP connector is an address your AI reads tools from. Ahel's connector serves your whole account at one address.

How does the Ahel MCP connector work?

It is a remote MCP server over streamable HTTP. After the client is configured, OAuth signs you in and each authorized call reaches your Ahel workspace. Setup steps depend on the client.

Which AI clients does this work with?

The supported setup paths cover Claude, Claude Code, ChatGPT, Codex, Cursor, and VS Code with Copilot. They authenticate through browser OAuth. Claude shows cards; Cursor, Claude Code and Codex get complete text; cards in ChatGPT and VS Code are not verified yet.

Does it work with ChatGPT?

Yes, through Developer mode, on ChatGPT plans that allow custom apps: in ChatGPT's Settings, turn on Developer mode, then create an app named ahel with Ahel's address as the server URL. We have not verified Ahel's cards in ChatGPT yet.

Why does the tool list never change?

Install a hundred servers and your client still sees the same tools: installed servers are reached through tools and use, never added to the list. A tool list that grows with every install breaks prompt caching, bloats every request, and makes clients that read the list once at connect time show stale tools. The 2026-07-28 MCP revision recommends a deterministic tool list for exactly this reason.

What can my AI actually reach?

Only what your account can already reach: your workspace's apps, the catalog, and the tools of the hosted MCP servers you have enabled. Key values never cross the connector. Nothing more, and nothing from anyone else's account.

Can it spend money?

Not without you on a write: with the confirm setting on (the default), every write your AI asks for shows a card first and runs only when you press it. A read can still cost money. A read from a paid vendor spends on your key the moment your AI makes it, and Ahel's knowledge queries, web search, hosted scripts, app actions and the models in the hosted chat are paid from your workspace balance at the prices on the pricing page. Spending from the balance stops at zero, and a failed knowledge query is never charged.