Troubleshooting

No sign-in page opened

Connect again. In Claude Code, run /mcp and choose unbranch. In Claude, choose Connect on the connector. In other clients, use the client’s own login action for the server.

The agent cannot see the project

Ask the agent which account and projects it sees; it calls whoami. Two causes are common:

• Another account. You signed in with a different unbranch account. Disconnect the client under Account → Security → Connected apps and connect again.
• Not on the project. Being on the team is not enough; you must be assigned to the project. Ask a project owner or team admin to add you. See Teams, projects and access.

Two sets of unbranch tools

This happens when a chat connector and a repository server point at different addresses, or when two servers under different names point at unbranch. Keep one, or point both at the same address. In a repository, a local server named unbranch takes precedence over the one in .mcp.json.

Checking a repository’s setup

npx @unbranch/kit@latest doctor

It checks the files, that the server answers, whether another MCP server clashes, and whether the skills are installed. Each failed check says what to run.

Refusals an agent may report

What it says	What to do
Rate limit exceeded (429)	Wait a minute and try again; nothing else is wrong. An API key, for example, is limited to 120 requests per minute.
Credits exhausted (402)	The team’s monthly model credits are spent. Waiting does not help: only a team owner or admin can upgrade, and the pool refills on the first of the month. Writing drafts still works; checking and sending do not.
Proposal audit unavailable (503)	The model had a bad minute. Check or send again.
Project not found (404)	The connection cannot reach that project. See above.

Every refusal names what to do next. Nothing is quietly trimmed or half-written.