MCP connector
Connect Claude Code.
Run one command to add Ahel to Claude Code, then approve the browser sign-in.
Your apps, skills, and knowledge stay with your Ahel account.
The command
Set up Claude Code
claude mcp add --transport http ahel 'https://mcp.ahel.ai'- Run this once to add Ahel: claude mcp add --transport http ahel 'https://mcp.ahel.ai'
- In Claude Code, open /mcp, select Ahel, and approve the browser sign-in.
Part of a team on ahel? This address connects your AI to the workspace you were invited to. In more than one? Your AI in the app has a link for each.
Connect
Do it from here
Connect Ahel to Claude
Add Ahel once, then sign in to authorize access.
First-time setup
- Add a custom connector and name it Ahel.
- Use this server address:
https://mcp.ahel.ai - Choose OAuth, connect, and approve the Ahel sign-in.
Claude currently requires this initial setup. Opening it here does not create a connection.
Using Claude Code?
Run this once to add Ahel:
claude mcp add --transport http ahel 'https://mcp.ahel.ai'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 agents use to reach tools and data. An MCP connector is an address an agent reads capabilities 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 gateway. Setup steps depend on the client.
Which agents 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.
Does it work with ChatGPT?
Yes. A ChatGPT connector needs a search and a fetch tool; the link serves both, so ahel can be added under Settings, Connectors, with the same address. Custom apps must be enabled by your plan and workspace.
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 agent actually reach?
Only what your account can already reach: your gateway, the catalog, and the tools of the hosted MCP servers you have enabled. Credential values never cross the link. Nothing more, and nothing from anyone else's account.
Can it spend money?
The link's own tools cannot: they only read the catalog and edit your gateway. But a call proxied to a server you enabled does whatever that server does, with your credential attached, so a paid vendor call spends money the moment your agent makes it.