Connecting your own AI app

How does an AI app sign in, what can it reach, and how is it cut off?

Any account holder can sign an AI app into a module over MCP (Model Context Protocol), with no admin step; the app acts as that account, with every action logged. Keep in mind: Hosted apps such as Claude can connect only if the module has a public HTTPS address, which whoever runs the instance must provide.

In the module's Connected Apps settings, one button opens Claude's form for adding a custom connection, already filled in. You confirm it, then sign in to your module and choose allow or cancel. Keep in mind: Claude can reach a module only at a public, secure web address. If yours does not have one, the page gives you a ready-made request to send to your instance's host.

Partial: The same settings page walks you through adding the module to ChatGPT as a custom connection. You paste its address into ChatGPT and sign in to your module. Then you install the new connection before using it. Keep in mind: A working ChatGPT connection has been reported from internal testing, but the full flow has not yet been independently verified. Your ChatGPT workspace must allow custom connections. The module also needs a public, secure web address.

Developers can add a module to Claude Code, or to another AI app that supports the same kind of connection. They use the address and ready-made setup text shown in the module's settings, then sign in from that app. Keep in mind: The settings page spells out the sign-in steps only for Claude Code.

A connected app acts exactly as your account. It can read and change only what you can, so it has admin powers only if you are an admin. Keep in mind: A connection reaches the module you connected and the modules inside it that you can enter. It never reaches the module above it or any module beside it.

Your app's own AI and account, such as your Claude plan, do the thinking. The module's own AI service is not used for your app's reasoning. Keep in mind: The module's own AI service is still used when your app asks one of the module's bots (AI assistants that live in the module). It is also used when your app runs a search by meaning (finding files by topic, not exact words). The app's own conversation stays in the app, but any message it posts into the module is stored in the module.

AIEUS does not pause the app for approval, so your app's own confirmation prompts are the safeguard. Every action the app takes in the module goes into the module's audit log, a who-did-what record admins can read. Keep in mind: Admins can see exactly what the app asked the module to do, such as text it wrote, plus a short summary of the result. Values that look like passwords, tokens or keys are blanked out automatically. This may not catch every secret.

AIEUS has no list of connected apps. Removing a connection inside Claude does not cancel the sign-in Claude holds. To cut off every app, change your password, or have an admin reset it and then choose a new one. Keep in mind: Otherwise an app can keep renewing its sign-in, with no overall limit. Each renewal is good for up to 30 days. AIEUS rechecks your account on every request, so either step reaches every app on its next action. If an admin disables your account, apps are only paused until it is re-enabled.