ahel
Start free

Apps Studio

Turn any API into an app inside your AI.

Paste an OpenAPI spec or an MCP server URL, pick a card for each action and activate. Your app gets its own MCP endpoint, and it answers through your ahel connector too. No MCP server to write.

Open Apps Studio

Early access. Free until 1 January 2027. Apps stay private to you or shared with your workspace.

What it is

One app, two ways into your AI.

Apps Studio is where you design, add, test and publish an in-chat app. ahel serves it, keeps its key in the vault and writes a text version of every card. Claude shows the cards.

  • Its own MCP endpoint

    https://mcp.ahel.ai/apps/<your-app>

    Every app you add answers at its own address. Add it to Claude as a custom connector, or to Cursor, Claude Code or Codex as a remote MCP server.

  • Your ahel connector

    https://mcp.ahel.ai

    The same app also answers through the one address your AI already has, next to the apps you connected from the catalog. It is one way in, not the only one.

Four steps

Design, add, test, publish.

  1. 01 Design

    Pick a card for each action.

    Paste an OpenAPI spec or an MCP server URL. For each operation choose list, detail, table, status, form or approval, and the fields it shows.

  2. 02 Add

    Check it, then activate.

    See each card drawn from a sample response. Activate, and the app answers at its own endpoint and in your ahel connector. Its API key sits in the vault and is added on our side.

  3. 03 Test

    Ask your AI.

    Add the endpoint to Claude and ask: Claude shows the card, and Cursor, Claude Code and Codex get the text version.

    Coming: host previews and a readiness check inside Studio.

  4. 04 Publish

    Keep it private, or share it with your workspace.

    Everyone in your workspace reaches a shared app through the same ahel connector, under the same vault and approval rules.

    Coming: a review step before an app goes live for everyone, and a submission kit.

Six cards

A card for every kind of answer.

Every card comes with a text version, generated for you, so an AI that draws no card still gets a complete answer.

  • List Result

    Rows from a result, each with a title, a line under it and a few details.

  • Detail Result

    One record: a title and the labelled fields you pick, with a link if you want one.

  • Table Result

    Rows with named columns, for results people compare.

  • Status Result

    Where a job stands: its state and progress, and it can check again until the job is done.

  • Form Before a call

    Asks for the values a call still needs, and nothing else.

  • Approval Before a call

    Shows the values before a change runs and waits for an answer.

Who it is for

Built for teams and developers.

For teams

Put your internal apps inside the AI your team already uses.

  • Turn the internal APIs your team already runs into apps people use from Claude, ChatGPT, Cursor, Claude Code and Codex.
  • The owner or a team lead adds apps. Each person signs in to ahel with their own account.
  • The app's keys stay sealed in one vault. Risky actions can wait for a yes on ahel.ai under an approval rule.
  • One log of calls, whichever AI made them.

For developers

OpenAPI or MCP in. MCP Apps out.

  • Your app answers at https://mcp.ahel.ai/apps/<your-app>, with tool annotations, _meta.ui and a ui:// card resource per the MCP Apps spec.
  • No framework, and no MCP server to host. Every result carries a text version, so an AI without cards still gets a full answer.
  • Your own server stays yours: run it under your own name and submit it to the Claude or ChatGPT directory yourself. ahel does not submit for you.

Where it stands

Early access, said plainly.

Works today
  • Design from an OpenAPI spec or an MCP server URL
  • Six cards, each with a generated text version
  • Its own MCP endpoint, and your ahel connector
  • Private to you, or shared with your workspace
Coming
  • Host previews and a readiness check
  • A review step before an app goes live for everyone
  • A submission kit for your own directory listing
Not offered
  • Public apps, open to anyone with an ahel account
  • ahel listing or submitting your app in a directory

Free until 1 January 2027.

FAQ

Questions about Apps Studio

What is Apps Studio?

Apps Studio is where you turn an OpenAPI spec or an MCP server into an in-chat app. You pick a card for each action, check it against a sample response and activate it. The app gets its own MCP endpoint and also answers through your ahel connector.

Do I need to write an MCP server?

No. Paste an OpenAPI spec, or the URL of an MCP server you already run. ahel serves the app's endpoint, keeps its API key in the vault and writes the text version of every card.

Which AIs show the cards?

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.

Add ahel to your AI

Who can use an app I add?

You alone, or everyone in your workspace: you choose private or shared. The owner or a team lead adds a workspace's apps, and each person signs in to ahel with their own account. Public apps are not available.

Can I list my app in Anthropic's or OpenAI's directory?

Yes, for your own endpoint, which you submit yourself under your own name; ahel does not list apps in either directory and does not submit for you. An MCP server you run is yours to list. An app's endpoint on ahel answers only to people in your workspace today, and whether a directory lists an endpoint hosted on ahel is the directory's call. No, for an app reached through the ahel connector: the directories do not accept apps that mainly pass calls through a third party.

What does it cost?

Apps Studio is in early access and free until 1 January 2027. The free plan needs no credit card.

Build your first in-chat app.

Early access. Free until 1 January 2027. Apps stay private to you or shared with your workspace.

Open Apps Studio