Troubleshooting AI agent connections

The agent can't sign in

If your AI app shows a sign-in error, or keeps asking you to connect:

Start the connection again from your AI app. In Claude Code, type /mcp, choose the Metaintro connection and sign in again.
Make sure you sign in to the Metaintro account you want the agent to use.
On the Metaintro page that opens, select Connect. If you see "This link has expired", go back to your AI app and start again.
Check the address you added. It should be exactly https://www.metaintro.com/api/mcp, or https://www.metaintro.com/api/mcp/org/<org-slug> for an organization. Get started in Settings > Agents, or on the My AI agents tab of your organization's settings, shows the right address with a button to copy it.

If you connected with a personal key, the agent may see: "Sign in through your AI client, or send a Metaintro personal API key…". This means the key is missing, mistyped, expired or disconnected. Keys last 90 days. In Settings > Agents, open the Other apps tab under Get started, select Create an API key, and update your app's setup.

In Codex, run codex mcp login metaintro. In Pi, run pi mcp login metaintro. For an organization, use its connection name, such as metaintro-<org-slug>. With the pi-mcp-adapter extension, sign in inside Pi with /mcp-auth metaintro instead. To see whether the app is connected, run codex mcp list or pi mcp list.

The agent can read but can't make changes

If the agent reports insufficient scope, or says it can't make changes, it is connected as Read only: Agents you've connected shows Read only next to it. Disconnect it and connect it again. With an API key, choose Read and act under What it may do. When you sign in through your app, check that the Metaintro page lists making changes for you before you select Connect.

If the message says "This credential cannot use the MCP server", the key was created without agent access. Select Create an API key on the Other apps tab in Settings > Agents, or sign in again through your AI app and allow access.

"Organization keys name no person to act as"

Organization API keys (mi_org_…) can't be used with AI agents. An agent always acts as one person, so every change is recorded under someone's name. Use a personal key from Settings > Agents, or sign in through your AI app.

"You aren't on this organization's staff"

An organization's connection (/api/mcp/org/<org-slug>) only works for people with a staff role in that organization. If you see this message:

Check the organization name in the address.
Ask an admin of the organization whether you have a staff role. Only staff see the My AI agents tab in the organization's settings.
For your own job search, use the personal address https://www.metaintro.com/api/mcp.

"This connection only reaches…"

Each organization's connection works only in that organization. If the agent tries to work with a different organization, it is refused. Add a separate connection from the My AI agents tab in the other organization's settings.

The agent can't find case manager tools

The personal connection only reaches your own job search. To work with an organization's members, connect to that organization's address. See Using AI agents as a case manager.

"Too many calls from this key. Try again in N seconds."

To keep Metaintro fast for everyone, each connection has per-minute limits on reads, changes, Cabinet requests and assistant conversations. Wait the number of seconds shown, then try again. If it keeps happening, ask your agent to make fewer, larger requests.

"Too many requests" or "Metaintro is temporarily unavailable" usually clears within a minute.

An action is waiting for approval

If the agent says an action is waiting for approval, it's not stuck. Approve or decline it under Waiting for your approval in Settings > Agents, or on the My AI agents tab in your organization's settings if it came through that organization's connection. Requests lapse after 7 days. See Approving what your AI agent does.

An action failed after you approved it

If you see "Approved, but the action failed", ask your agent to check the request. It can read the reason with its request status tool (get_action_request). Common reasons:

The record changed in the meantime. Ask the agent to read it again and retry.
The agent was disconnected before you approved, so nothing ran.
You no longer have access to what the action needed.

The agent says a record changed

Some changes check that the agent has the latest version of a record. If someone else edited it first, the change is refused so nothing is overwritten. Ask the agent to read the record again and retry.

Disconnect or reconnect an agent

Go to Settings > Agents, or the My AI agents tab in your organization's settings.
Find the agent under Agents you've connected and select its delete (trash) button.
Confirm with Disconnect.

It stops working at once, everywhere. To use it again, connect it again from your AI app.

For AI agents: check the connection

Work through these in order:

Call whoami. If it works, the connection is fine. Note which connection it is and the approval setting.
If you get a sign-in error, ask the person to sign in again (/mcp in Claude Code, codex mcp login metaintro in Codex, pi mcp login metaintro in Pi (or /mcp-auth metaintro inside Pi with the pi-mcp-adapter extension)). Check that the address is exactly https://www.metaintro.com/api/mcp.
If a change is refused for insufficient scope, the connection is Read only. Tell the person and don't retry.
If you are told to try again in a number of seconds, wait that long before the next call.
If a change is refused because the record changed, read it again and retry with the new version.