> ## Documentation Index > Fetch the complete documentation index at: https://docs.ainomos.ch/llms.txt > Use this file to discover all available pages before exploring further. # Connect your AI apps > Connect a personal AI app such as Claude Code, Cursor or VS Code to Ainomos, and manage or withdraw its access. A personal app is an AI app you use as yourself, such as Claude Code, Cursor, VS Code, Codex or OpenCode. Once connected, it asks Ainomos instead of guessing: it gets answers with sources, looks up decisions and checks planned actions against your rules. The app sees exactly what you are allowed to see, never more, and its work leaves evidence like yours does. Apps connect through MCP, the Model Context Protocol: the open standard AI apps use to connect to Ainomos. You do not need to know how it works. Each app's setup steps in Ainomos give you the address and the configuration, already filled in for your installation. Who can do this: everyone with an Ainomos account. Platform admins decide which apps are listed. ## Open Personal apps In the navigation, open **Connections**, then **Personal apps**. * On the left, **Personal apps ยท every room** lists the apps you have connected. A connection is yours, not a room's, so it reaches every room you can open. * On the right, **Connect an app** shows the apps your organisation lists. Each card shows the app's name, the badge **Per person**, what it is for, and where it runs: **On your computer** or **From its cloud**. Apps you already connected carry **Connected**. When you have connected at least one app, select **Connect an app** in the list to get back to the cards. ## How connecting works Every app follows the same pattern: **1. Pick the app** Select its card. The right side shows the steps for that app, numbered, with everything to copy. **2. Add Ainomos to the app** Paste the address or the configuration, run the command, or use the install button, depending on the app. **3. Sign in and say yes once** The app opens the Ainomos sign-in in your browser. Sign in as yourself and confirm what the app may do. Most apps register themselves at this first sign-in. **4. Check it** The app now shows under **Personal apps**. Ask it something about one of your rooms. What you agree to: the app may read and ask in every room you can open, and propose decisions as you. It cannot do more than you can. ## Steps for each app > [tab] Claude Code CLI > > 1. **Add Ainomos in a terminal**: copy the command and run it. The address is already filled in. > 2. Run `/mcp` in Claude Code, sign in and say yes once. The sign-in opens in your browser. > > On an installation that uses your company's own certificate, a step in between sets your shell to trust it. Your IT department gives you the file. > [tab] Codex CLI > > 1. **Add Ainomos in a terminal**: copy the command and run it. > 2. **Sign in from the terminal**: run the sign-in command. It opens the sign-in in your browser, Codex registers itself, and you confirm once what it may do. > > If your company uses its own certificate, your IT department installs it on your computer. > [tab] OpenCode > > 1. **Add the server to opencode.json**: paste the configuration into opencode.json in your project, or into the global OpenCode configuration for every project. > 2. **Sign in from the terminal**: the command opens the sign-in page. OpenCode registers itself. > 3. **Check the connection**: the list command shows the server as connected. > [tab] Cursor > > * **For organizations (recommended): Team MCP server**. If your Cursor plan has Team MCP, a Cursor team admin adds the address once in the Cursor dashboard. Every team member then has it. Each person still signs in as themselves. > * **For individuals: Home MCP**. Select **Add to Cursor**, or paste the configuration into mcp.json. Approve once; the connection survives restarts. > > Team MCP and Cursor's cloud agents need an installation that is reachable from the internet. Cursor on your computer works either way. > [tab] VS Code > > Select **Install in VS Code**, or paste the configuration into mcp.json. Sign in and confirm when VS Code asks. > [tab] Claude Desktop and claude.ai > > Copy the **MCP URL of this installation**. In Claude, open Settings, then Connectors, add a connector and paste the address. Sign in and confirm. > > Claude Desktop and claude.ai connect from Anthropic's cloud. An installation that is only reachable inside your company network cannot be reached this way; use Claude Code CLI instead. > [tab] Hermes > > Select **Add to Hermes Desktop**, or add the configuration block to the Hermes configuration file. A single command also adds the server and registers the app. Then sign in, and run the test command to check the connection. > [tab] Custom app > > For any other app that speaks MCP: > > 1. **Paste the address into your app**, where it adds an MCP server or a connector. > 2. **Or paste this configuration**, for apps set up from a file. > 3. **Sign in and say yes once**. The app then shows under **Personal apps**. An app your organisation listed itself has its own card, marked "Listed by your organisation. Signs in as you." It shows the steps and configuration a platform admin wrote for it, with the address already filled in. If the app uses a client ID, the steps show it under **Client ID**. A client ID is not a secret. ## If your app cannot register itself Some apps, and some installations, cannot sign up on their own. The sign-in then stops with an error about the client. Ask a platform admin to list the app under **Personal apps**. It then gets a client ID, which you paste into your app next to the address. You still sign in as yourself. See [Organisation apps](https://docs.ainomos.ch/apps/organisation-apps.md#the-connections-settings). ## Your connections Select an app under **Personal apps** to see its connection. Each row shows since when it is connected, when it was last used, and its status, for example **Active**. A connection the platform does not track shows **Not in the register**. The detail shows: * **This week**: **Answers** and in how many rooms, **Last used** and in which room, and **Proposals sent** to the Inbox. * **Last uses**: what the app did, when and in which room, each with an **Evidence** link to the record. * **What this app may do**, and the date you said yes. * **Details**: your consent, the status in the register, the permissions granted and the client ID. If your organisation stops listing an app, your existing connection keeps working, but nobody can connect it again. ## Withdraw access **1. Select the app** Under **Personal apps**, select the app. **2. Withdraw** Select **Withdraw access**, then confirm with **Withdraw**. Withdrawing takes back your consent for that app in every room. A session the app already has may run until its sign-in expires. The next time the app connects, it has to ask for your consent again. To cut off an app at once for everyone, a platform admin disables it under **Settings**, **Connections**. ## Related * [What connected apps can do](https://docs.ainomos.ch/apps/what-apps-can-do.md) * [Organisation apps](https://docs.ainomos.ch/apps/organisation-apps.md) * [Audit log](https://docs.ainomos.ch/privacy/audit-log.md) * [Inbox](https://docs.ainomos.ch/chat/inbox.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.