Apps · Skills · Knowledge · One MCP link

The missing link for your AI.

Connect the apps, skills, and knowledge your AI is missing. One link serves them to Claude, Codex, Cursor, and every tool you use.

Start free Explore what’s possible

Free plan. No card needed.

Works withClaude Claude Code Codex Cursor VS Code

The problem

Delete the config sprawl.

Every client keeps its own config file. The gateway replaces the pile with one address.

5 clients5 config files

Claude Code~~~/.claude.json~~

Cursor~~~/.cursor/mcp.json~~

Codex~~~/.codex/config.toml~~

VS Code~~.vscode/mcp.json~~

Claude~~claude_desktop_config.json~~

With ahel1 link

Connected

https://mcp.ahel.ai

One config, read by every client
Keys sealed server-side, zero in files
Change it once, every AI follows

Works with

The tools your work already lives in.

Browse all apps

Discover

Three things your AI was missing.

01 · Apps

Connect the tools you already use.

SaaS vendors your AI can act on with your own key. Each app lists the actions ready for your AI, and ahel asks the missing questions before it runs one.

Browse apps

02 · Skills

Add reusable instructions for better work.

Code review, research, design, writing. Reviewed skill bodies served as a snapshot, so every tool follows the same procedure.

Browse skills

03 · Knowledge

Give your AI documents and data to work from.

Company records, sanctions lists, known exploited bugs, public contracts. Hosted by ahel, kept fresh, queryable without a single key.

Browse knowledge

The moat

Install a hundred servers. Your AI sees 19 tools.

Every other gateway’s tool list grows with each install, wrecking prompt caching and context. Ours is fixed. Installed servers are reached through tools and use, never appended. Nothing reconnects. Nothing slows down.

Other gateways

1,400+

tools after 100 installs

ahel

tools. Always.

explore
search
fetch
install
installed
switch
status
tools
use
list_actions
run_action
raw_request
run_script
skill_read

Claude CodePreview

> triage last night's Sentry errors, open Linear issues for the real ones and post a summary in #eng

use(sentry.list_issues, since="24h") → 14 issues

run_script(dedupe · drop known flaky · rank by users hit) → 3 real

use(github.search_code, "PaymentIntent") → checkout/stripe.ts:142

use(linear.create_issue × 3) ✓ ENG-482 · ENG-483 · ENG-484

use(slack.post_message, #eng) ✓ posted

4 apps, 6 calls, 0 keys in the prompt. Sentry, GitHub, Linear and Slack were all reached through the same 19 tools.

What it unlocks

Ask for the work, not the tool.

Your AI can test in a real browserfile the follow-up issuessearch and read the webwatch production errorskeep the docs up to datefill the spreadsheet

Once the gateway serves the tools, the prompt is the whole interface.

Security

Your keys never cross the link.

CredentialsPreview

GitHubsealedghp_xk91f2c8····f2c8

Anthropicsealed····9d41

Postgressealed····07be

Model traffic stays yours

Prompts and completions run directly between your clients and your model providers. The gateway serves tools and injects credentials server-side; it never sees a prompt.

Keys stay sealed

Envelope-encrypted at rest, masked in the UI, every decrypt audited.

No keys in your clients

Your AI clients connect through OAuth. The key itself stays in your encrypted credentials, out of every config file.

Nothing reads back

No endpoint returns a stored key. Store, replace, or delete: the response carries a status, never a value.

The full security picture

Batteries included

11 services, no keys needed.

A useful gateway before you add a single key. Web search, European company owners, sanctions, CVEs, public contracts. Operated by ahel. One click on.

Knowledge, in detail

Web Searchweb
Company Researchdata
Global Company Identities - GLEIFdata
Supplier Discoverydata
Market Researchdata
European Public Contract Notices - Collected Feeddata
Sanctions Entity Recordssecurity
OFAC Sanctioned Wallet Addressessecurity
Known Exploited Vulnerabilitiessecurity
Linked Account Checksecurity
Email and Address Checkdata

Teams

Start solo. Bring your team.

Invite a teammate and their AI gets the same apps and skills. Hand a session from your AI to theirs, with the claims labelled and the keys left behind.