Skip to main content

Connect your AI tool

Add Angareion to your AI tool in a few minutes. Angareion runs a hosted server your assistant connects to — no API key to paste, no software to install. You approve the connection once from your browser, and Angareion's memory tools show up inside your assistant.

Everything below uses one address — the Angareion MCP server URL:

https://mcp.angareion.com/mcp

You'll paste that into your AI tool's connector settings, then approve access. Jump to your tool:

Signing in is safe

When you connect, a browser window opens and asks you to approve access. You sign in with your Angareion username and password — your AI tool never sees them. You can revoke a connection at any time from your Angareion dashboard.

Claude​

Works with the Claude desktop app and Claude on the web.

  1. Open Claude. Click your account name and go to Settings.

  2. Go to Connectors → Add → Add custom connector.

  3. In the dialog, set the Name to Angareion and the Remote MCP server URL to:

    https://mcp.angareion.com/mcp

    Claude Add custom connector dialog with Name set to Angareion and the Angareion MCP server URL

  4. Click Add.

  5. Click Connect. A browser window opens to Angareion.

    Claude prompting to connect to the Angareion connector

  6. If prompted, log in with your Angareion username and password.

  7. Click Approve on the consent screen.

  8. Return to Claude — Angareion tools are now available in your conversation.

Claude Code​

These steps configure local Claude Code sessions. Claude Code on the web does not use MCP servers added by the local CLI.

  1. In a terminal, register Angareion at user scope so it is available in every local project:

    claude mcp add --transport http --scope user angareion https://mcp.angareion.com/mcp

  2. Start or restart Claude Code and enter /mcp.

  3. Select angareion, then choose Authenticate when prompted. Claude Code opens your browser. If it cannot, copy the authorization URL it displays into a browser on this computer.

  4. Log in to Angareion if prompted, name a new agent or choose an existing one, and click Approve.

  5. Return to Claude Code and enter /mcp again. Angareion should show as connected with its tools listed.

See Anthropic's Claude Code MCP documentation.

ChatGPT​

Add a custom MCP server from ChatGPT on the web. Workspace permissions and security restrictions control who can create and use it.

  1. Open Plugins, select +, then choose Add custom MCP server.

  2. Set the name to Angareion. Under Connection, enter the server URL below. Use Streaming HTTP and OAuth if those options are shown:

    https://mcp.angareion.com/mcp

  3. Leave static OAuth credentials blank. If the form asks how to register the client, choose Dynamic Client Registration (DCR). Angareion publishes OAuth discovery metadata and supports automatic registration.

  4. Review the connection warning and choose Create as a plugin.

  5. Find Angareion in your personal or workspace plugins and install it.

  6. Start a new conversation. Type @ in the prompt box and select the installed Angareion plugin. Ask it to retrieve your project context.

  7. When prompted to connect, sign in to Angareion in your browser, name a new agent or choose an existing one, and click Approve. Return to ChatGPT and confirm that an Angareion tool can run. ChatGPT may ask for confirmation when a tool creates or changes data.

See OpenAI's custom MCP server setup guide and skills and plugins guide.

Codex​

Codex is a first-class Angareion Connect target. The ChatGPT desktop app, Codex IDE extension, and Codex CLI share the same user-level MCP configuration. This is distinct from ChatGPT on the web.

  1. In ChatGPT desktop, open Settings → MCP servers → Add server. Set the name to Angareion, choose Streamable HTTP, and enter:

    https://mcp.angareion.com/mcp

    Save, then select Restart. If the server shows Authenticate, select it. If that control is absent, use the explicit login command below.

  2. Or, register Angareion from a terminal. Skip this if you already added it in desktop settings:

    codex mcp add angareion --url https://mcp.angareion.com/mcp

  3. Start the OAuth flow:

    codex mcp login angareion

  4. In ChatGPT desktop on macOS, codex may not be on your PATH. Use its bundled binary instead (again, omit the first line if the server is already configured):

    /Applications/ChatGPT.app/Contents/Resources/codex mcp add angareion --url https://mcp.angareion.com/mcp
    /Applications/ChatGPT.app/Contents/Resources/codex mcp login angareion

  5. In the browser, log in to Angareion if prompted, name a new agent or choose an existing one, and click Approve.

  6. Return to Codex and start a new task. In the CLI, enter /mcp to confirm Angareion is connected. The app and IDE extension read the same ~/.codex/config.toml configuration. A missing Authenticate button or Auth: Unknown label is not a reliable failure signal—invoke an Angareion tool to verify the connection.

  7. To add reusable memory, knowledge, handoff, specialist, and output workflows, choose one of these paths:

    • Recommended: install the signed Codex plugin bundle from the matching ang-v* release. It packages the skills and MCP server together. Do not combine it with a manually configured server of the same name.
    • Manual MCP already configured: run ang install skills --target codex for standalone skills in ~/.agents/skills. This does not configure or authenticate the MCP server. If you need to install ang first, run curl -fsSL https://github.com/angareion/releases/releases/latest/download/install.sh | ANG_SKIP_SKILLS=1 sh, then the ang install skills --target codex command above — the plain installer otherwise also registers the MCP connection for you (idempotent: it's a no-op if you already added it above).

See OpenAI's Codex MCP documentation and Skills documentation.

Gemini​

Google documents two custom MCP clients: Gemini CLI for self-service use and Gemini Enterprise for administrator-managed deployment. The consumer Gemini web app and Google AI Studio do not use this setup flow.

Gemini CLI​

  1. Register Angareion at user scope so it is available in every Gemini CLI project:

    gemini mcp add --transport http --scope user angareion https://mcp.angareion.com/mcp

  2. Start Gemini CLI and enter /mcp auth angareion.

  3. Complete the browser flow on the same computer. OAuth requires a local browser and callback, so it will not work from a headless container or an SSH session without browser forwarding.

  4. Log in to Angareion, name a new agent or choose an existing one, and click Approve.

  5. Return to Gemini CLI and enter /mcp. Angareion should show as connected with its tools listed.

See Google's Gemini CLI MCP documentation.

Gemini Enterprise​

Gemini Enterprise custom MCP data stores are a Preview feature configured by a Google Cloud administrator.

  1. Complete Google's prerequisites:

    • Override the organization policy that blocks custom MCP data stores.
    • Allow the mcp.angareion.com and angareion.com FQDNs for egress.
    • If project enforcement applies, add custom_mcp to the allowed data sources.
    • Grant the administrator Discovery Engine Editor (roles/discoveryengine.editor).

  2. Email support@angareion.com for a Gemini Enterprise OAuth Client ID registered to Google's fixed redirect URI. Angareion uses public-client PKCE for this flow, so you will not receive or enter a Client Secret.

    https://vertexaisearch.cloud.google.com/oauth-redirect

  3. In Google Cloud, open Gemini Enterprise → Data stores → Create data store.

  4. Search for Custom MCP Server, click Add MCP server, and choose OAuth 2.0.

  5. Enter these values, add the Client ID from Angareion support, turn on Enable PKCE Support, and leave Client Secret empty:

    MCP Server URL: https://mcp.angareion.com/mcp
    Authorization URL: https://angareion.com/authorize
    Token URL: https://angareion.com/token
    Scopes: mcp

  6. Click Verify Auth. Log in to Angareion, name a new agent or choose an existing one, click Approve, then return to Google Cloud and click Continue.

  7. Enter a clear MCP server description, continue, choose the connector multi-region, set the data connector name to Angareion, and click Create. Wait for its state to become Active.

  8. Open the new data store and choose Actions → Reload custom actions. Reauthenticate if asked, select the Angareion actions users may call, and click Enable actions.

  9. Attach the data store to the Gemini Enterprise app or agent your users will open.

See Google's Gemini Enterprise custom MCP documentation.

Perplexity Enterprise​

Remote custom connectors are a Perplexity Enterprise feature. Organization members can add one only when an administrator enables custom connectors.

  1. If you are not an administrator, ask one to enable Allow members to add custom connectors under the Enterprise connector permissions. An administrator can instead create and share an organization-wide connector.

  2. For an individual connector, open Account settings → Connectors.

  3. Click + Custom connector, then select Remote.

  4. Enter these settings:

    • Name: Angareion
    • Authentication: OAuth 2.0
    • Transport: Streamable HTTP
    • MCP Server URL:
    https://mcp.angareion.com/mcp

  5. Do not enter a Client ID or Client Secret. Angareion supports OAuth discovery and Dynamic Client Registration, so Perplexity can register automatically.

  6. Check the custom-connector risk acknowledgement, then click Add.

  7. Back on the Connectors screen, click the Angareion connector card to authenticate and enable it.

  8. Log in to Angareion, name a new agent or choose an existing one, and click Approve.

  9. Return to Perplexity and confirm the connector is enabled. You can now invoke Angareion from a Perplexity prompt.

See Perplexity's custom remote connector documentation.

Joule Work Desktop​

Early-access Skills validation

Joule Work Desktop can import the generated Angareion skill zip. Its import format is based on validated early-access skill packages, but end-to-end MCP execution is not yet marked verified because current workspace policy blocks custom MCP connections.

  1. Launch Joule Work Desktop. Click Extensions to open the extensions panel.

    Joule Work Desktop Extensions menu item

  2. Click + New → Add Connector.

    Joule Add Connector menu

  3. Set the Name to Angareion and paste the MCP URL into the URL field:

    https://mcp.angareion.com/mcp
    Joule Add Connector screen with the Angareion name and MCP server URL

  4. Click OK.

  5. Joule opens a browser window to Angareion. If prompted, log in with your Angareion username and password.

  6. Name your agent (or choose an existing one), then click Approve on the consent screen. Agent memories can be shared across sessions and LLMs.

    Joule Approve connection consent screen

  7. Return to Joule — Angareion tools are now available in your workspace.

If your workspace cannot add the remote connector​

Some Joule workspaces do not allow adding a remote MCP connector. As an alternative, Angareion provides a small local proxy. It runs on your own computer, listens only on your own machine, and forwards Joule's requests to the same Angareion server, so the same tools and the same agent are available. Your requests and their content still go to Angareion, so confirm this is permitted by your organization's policy before using it.

You need Joule Work Desktop, an Angareion account, and Node.js 18 or newer (run node -v to check; if the command isn't found, install the LTS version from nodejs.org and open a new terminal). There is no npm install.

1. Download both files​

Open the Angareion releases page, open the newest release, and under Assets download:

FileWhat it is
angareion-joule-local-proxy-vX.Y.Z.zipThe local proxy
angareion-skills-joule-vX.Y.Z.zipThe Angareion skill for Joule. Do not unzip it.

Each file also has a .sigstore.json signature, which is optional to use.

2. Unzip the proxy and open a terminal in its folder​

Unzip the proxy somewhere permanent. You get a folder called angareion-joule-local-proxy. On Windows, open it in File Explorer, click the address bar, type cmd, and press Enter. On macOS, open Terminal, type cd (with a space), drag the folder into the window, and press Enter.

3. Sign in once​

node server.js --login

Your browser opens to the Angareion sign-in page (the terminal also prints the address and a code, in case it does not; add --no-browser to skip opening it). Log in if prompted, check that the code matches, choose the agent this connection belongs to (or create a new one, for example "Joule agent"), and click Approve. You see only your own agents, the same screen as when you connect Claude or ChatGPT. Memories belong to the agent, so choosing the same agent your other tools use shares one memory across them. The terminal then says Signed in.

4. Start the proxy and leave it running​

node server.js --http

You should see listening on http://127.0.0.1:7731/mcp. Keep this window open while you use Joule. On Windows you can double-click start-angareion-proxy.cmd instead.

5. Add the connector in Joule​

Click Extensions, then + New → Add Connector. Set the Name to Angareion, the URL to http://localhost:7731/mcp, and Authentication to None. Click OK.

6. Import the skill​

In Extensions, open Skills and Import angareion-skills-joule-vX.Y.Z.zip.

7. Check that it works​

Ask Joule "What does Angareion remember about my current project?" or "Help me get started with Angareion." It should call an Angareion tool and answer from your memory.

Keeping it working​

  • The proxy must be running whenever you use Joule with Angareion. The README.md in the proxy folder explains how to start it automatically when you sign in to your computer, on Windows and macOS.
  • Sign-ins last about 30 days. When one lapses, Joule tells you to run node server.js --login again; the proxy does not need restarting.
  • node server.js --status shows whether you're signed in, and node server.js --logout forgets the sign-in on this computer. Revoke the connection in your Angareion dashboard to end it on the server immediately.
  • If something doesn't work, the troubleshooting table in the proxy folder's README.md covers the common causes: Node.js missing, the proxy not running, a lapsed sign-in, a port already in use, and a refused connection.

The proxy listens only on your own machine and rejects requests from web pages, but any program running as you can use it, and its sign-in is stored in a file in your user profile that only you can read.

Add reusable Angareion workflows​

The connector exposes tools. Angareion Skills add repeatable instructions for using those tools safely and consistently across memory, knowledge, handoff, specialist, and output tasks.

  • Codex: install the Angareion plugin bundle published with each ang-v* release. It packages skills and the remote MCP dependency together; do not combine it with a manually configured server of the same name. A manually configured Codex MCP server can instead use ang install skills --target codex for standalone skills only.
  • ChatGPT on the web: add and install the custom MCP plugin. It does not read local ang installs or local Codex plugins; reusable workflows require an Angareion plugin distributed through a ChatGPT marketplace.
  • Claude and Perplexity: download and extract the matching platform pack, then upload each included per-skill ZIP separately. Every inner ZIP has SKILL.md at its root.
  • Claude Code, Gemini CLI, Cursor, Windsurf, Cline, and GitHub Copilot: run ang install skills --target <target>. Plain ang install skills continues to target Claude Code.
    • Don't have ang yet? Install it — and the skill pack, recall hook, and MCP connection for your target client — with one command on Linux, macOS, or Git Bash (MINGW64) on Windows: curl -fsSL https://github.com/angareion/releases/releases/latest/download/install.sh | sh. Native Windows cmd.exe / PowerShell download the binary manually — see the CLI README.
  • Joule Work Desktop: register a connector first (the remote server, or the local proxy if remote connectors can't be added), then download angareion-skills-joule-vX.Y.Z.zip from the newest release on the releases page and import it under Extensions → Skills → Import (do not unzip it). It is a single angareion skill that routes to a reference guide per workflow, and it activates once the connector is connected. MCP execution remains unverified while workspace policy blocks the connector.
  • Gemini Enterprise: use the connector without an MCP-backed Skill until its Skills runtime permits custom MCP tools.

Cursor, Windsurf, Cline, and GitHub Copilot are compatibility clients; they do not receive dedicated Angareion Connect cards.

Any other MCP client​

This URL-only flow works only in clients that support remote MCP over Streamable HTTP and OAuth 2.1. A client that supports only local stdio servers must use the Advanced: Local Binary option on the Angareion Connect page.

  1. Open the client's custom connector or MCP server settings. Add a server named Angareion with this URL: 
    https://mcp.angareion.com/mcp
  2. Choose Streamable HTTP (sometimes labelled HTTP or Streaming HTTP) and OAuth 2.0/2.1 if those fields are shown. Do not choose legacy SSE or API-key authentication.
  3. Use automatic OAuth discovery and Dynamic Client Registration when supported. No Angareion API key, Client ID, or Client Secret is needed.
  4. Start the client's Connect, Authenticate, or first-tool-call flow.
  5. Log in to Angareion, name a new agent or choose an existing one, and click Approve.
  6. Return to the client and confirm Angareion is connected and its tools are visible.

If the client requires pre-registered credentials, cannot perform PKCE, or never opens an OAuth flow, it is not compatible with the URL-only setup. See the MCP authorization specification for the protocol requirements.

Confirm it worked​

Once you've approved the connection, you can confirm Angareion received it:

  1. Open your Angareion dashboard and go to Connect.
  2. Pick the agent you want to verify against and click Check connection.
  3. When Angareion sees the live session, it shows Connected · Active with your tool's name.

You can also just try asking your assistant to use a memory tool (below) — if it responds, you're connected.

Try asking​

Once connected, your assistant can reach Angareion in plain language. A few things to try:

  • "Remember that our Q3 launch messaging pillars are speed, trust, and simplicity."
  • "What did we decide about pricing last week?"
  • "Search my Angareion memory for the onboarding checklist."
  • "Save this thread so I can pick it up in another assistant later."

What Angareion adds to your assistant​

Connecting gives your assistant a set of memory and knowledge tools. They fall into two groups:

Recall — reads your memory and knowledge (safe, read-only):

What it doesTool
Search your memoriesmemory_search
Browse and open memoriesmemory_list, memory_get
Search and fetch across everythingsearch, fetch
List documents & knowledge sourcesdocument_list, knowledge_sources_list
List available specialistsspecialist_list
See saved session handoffshandoff_list
Find saved work productsoutput_list, output_get, output_search

Capture — writes to your memory and knowledge:

What it doesTool
Save a new memorymemory_create
Edit or remove a memorymemory_update, memory_delete
Link memories togethermemory_relate
Promote a memory to your teammemory_promote
Add a document or a web pagedocument_ingest, document_ingest_url
Save / resume a session handoffhandoff_save, handoff_resume
Load a specialistspecialist_load
Save or email a complete work productoutput_save, output_email
note

The exact tools available can vary with your plan and your organization's settings.

Troubleshooting​

My assistant doesn't see any Angareion tools

The connection probably wasn't approved. Reopen your tool's connector settings, remove the Angareion connector, and add it again — this time make sure you complete the browser approval step (Approve / Allow). Disconnecting and reconnecting resolves most connection issues.

The approval window never opened, or nothing happened after I added the URL

Client behavior differs. In Codex desktop, run codex mcp login angareion; on macOS, if codex is not on your PATH, run /Applications/ChatGPT.app/Contents/Resources/codex mcp login angareion in Terminal. For other tools, the approval window may open on the first tool call—ask your assistant to do something with Angareion (for example, "search my Angareion memory"). In every case, check that the URL is exactly https://mcp.angareion.com/mcp with no trailing spaces.

"Check connection" in the dashboard times out

The dashboard waits about two minutes for a live session. Make sure you finished the Approve step in your AI tool, then click Try again. If you have no agents yet, register one first — the check needs an agent to verify against.

I don't see Add custom MCP server in ChatGPT

Use ChatGPT on the web and open Plugins. A managed workspace can restrict custom MCP server creation and plugin use; ask your administrator whether the connection is permitted. Check OpenAI’s current custom MCP setup guide if your interface differs.

Gemini Enterprise asks for a client secret

Turn on Enable PKCE Support and leave Client Secret empty. Email support@angareion.com for the public OAuth Client ID registered to Gemini Enterprise's fixed redirect URI.

I don't see + Custom connector in Perplexity

Remote custom connectors require Perplexity Enterprise, and administrators disable member-created connectors by default. Ask your administrator to enable Allow members to add custom connectors or to create an organization-wide Angareion connector.

My tool isn't listed above

Any tool that supports remote MCP servers over OAuth works — follow the Any other MCP client steps. If your tool only supports a local (stdio) connection, use the Advanced: Local Binary option on the dashboard's Connect page instead.

Next step​

Connected? Head to the Quickstart to capture your first memory and recall it in a chat.