Hoop

Connect Hoop to Codex

Add Hoop’s MCP server to Codex, authorize your workspace in the browser, and verify the connection. You won’t need to create or copy a Hoop API token.

Before you start

Direct Hoop OAuth requires Codex CLI 0.147.0 or newer. Check with codex --version, or update Codex Desktop if its bundled CLI is older. You also need a Hoop account with access to a workspace. Read and write is the default access level; you can choose read only during authorization.

Ask Codex to set up the connection

Recommended

Paste this prompt into Codex. Codex will check for an existing configuration, add Hoop only when it is safe to do so, and start browser authorization.

Setup promptOAuth · no tokens
Connect this Codex installation to Hoop's production MCP server at https://super.hoop.app/api/mcp using OAuth. Do not request or use a Hoop API token.

First run `codex --version`. Direct Hoop OAuth requires Codex CLI 0.147.0 or newer. If this installation is older, stop and tell me to update Codex before continuing. Do not disable issuer validation or suggest an API token as a workaround.

Then run `codex mcp get hoop` to check whether an MCP server named `hoop` already exists.

- If no `hoop` server exists, run `codex mcp add hoop --url https://super.hoop.app/api/mcp` once. This command may detect OAuth and open the browser automatically. If it does, wait for that flow to finish and do not also run `codex mcp login hoop`.
- If `hoop` exists at https://super.hoop.app/api/mcp, use `codex mcp list` to inspect its authentication state. If it is already authenticated, do not start another OAuth flow. If it is unauthenticated and no Hoop browser flow is already open, run `codex mcp login hoop` once.
- If `hoop` exists with a different URL, stop and explain the conflict without changing it.

Pause while I sign in to Hoop, confirm my workspace, choose Read and write, and approve access. After the browser returns, verify the saved URL with `codex mcp get hoop` and the authentication state with `codex mcp list`.

If the callback fails, report the diagnostic and stop instead of automatically starting another authorization. For `Authorization server response missing required issuer`, tell me to update to Codex CLI 0.147.0 or newer. After I confirm the problem is resolved, offer `codex mcp login hoop` as one explicit retry; do not weaken issuer validation.

After authentication succeeds, tell me to restart Codex and start a new chat so the Hoop tools load. Do not claim the tools are available in this existing chat.

Codex will pause while the browser is open. Sign in to Hoop, confirm your workspace, choose an access level, and select Allow access. Then return to Codex.

Set up from Codex Desktop

Use this path if you would rather add the server through settings.

  1. 1

    Open MCP settings

    Open Settings → MCP servers, then select Add server.

  2. 2

    Add the Hoop server

    Enter hoop as the name, choose Streamable HTTP, and use this URL:

    https://super.hoop.app/api/mcp
  3. 3

    Complete one authorization

    Save the server. If Hoop opens in your browser, complete that flow and do not also select Authenticate. If no browser opens, select Restart, then select Authenticate once.

  4. 4

    Start a new chat in Codex

    Begin a new chat after authentication so the Hoop tools are loaded.

Set up from the terminal

First confirm that the CLI is 0.147.0 or newer:

codex --version

Check whether Hoop is already configured:

codex mcp get hoop
  • No Hoop server exists: run codex mcp add hoop --url https://super.hoop.app/api/mcp once. It may open OAuth automatically. If it does, finish that flow and do not also run login.
  • The correct server exists but is unauthenticated: if no Hoop authorization is already open, run codex mcp login hoop once.
  • The correct server is authenticated: do not start another authorization.
  • The saved URL is different: stop and resolve the configuration conflict before continuing.

When authorization is complete, run codex mcp list to confirm Hoop is authenticated. Then restart Codex and start a new chat.

Verify the connection

In a new chat in Codex, ask:

Use Hoop to show my authenticated workspace context, then list the tasks I should focus on.

The response should identify the same workspace you approved and list only tasks you can access. Codex still follows your normal tool-approval settings for writes.

Troubleshooting

Authorization server response missing required issuer

Update to Codex CLI 0.147.0 or newer, confirm with codex --version, then run codex mcp login hoop once as an explicit retry. Keep issuer validation enabled; an API token is not a workaround for this OAuth compatibility error. See the official Codex CLI docs.

A server named “hoop” already exists

Run codex mcp get hoop. If it already uses https://super.hoop.app/api/mcp, check codex mcp list and run login only when it is unauthenticated and no authorization is already open. If it points elsewhere, decide whether to rename or remove that configuration before continuing.

I closed or denied the browser flow

Wait for the failed command to exit, then run codex mcp login hoop once when you are ready to retry.

I used the wrong Hoop account

Sign out of Hoop in the browser, then start authentication again from Codex.

Authentication worked, but tools are missing

Restart Codex and begin a new chat. MCP tools are loaded when a chat starts.

Manage or revoke access

Connected MCP clients appear in your Hoop app. Revoking Codex ends its OAuth access and requires authorization before it can connect again.

Manage connected clients →