Pythe

MCP troubleshooting

Fixes for the usual snags: a 401, an app not bound to a workspace, no plan yet, paused employees, credits, and clients that cached old discovery.

Updated 2026-10-13

You seeWhyFix
“Reconnect Pythe and sign in again.”The token is missing or expired, or the client was disconnected.Reconnect in your client and sign in.
“This app is not bound to a Pythe workspace. Disconnect it and connect again.”There is no ready workspace binding for this app.Disconnect the app in your client (and on the Deploy page) and connect again, choosing a workspace.
“This workspace does not have an operating plan yet.”The company has not finished onboarding.Finish onboarding in Pythe. get_plan_build shows if a build is running or failed.
“The plan changed or is no longer accessible. Nothing was updated.”Someone saved a newer plan after you read it.Call get_operating_plan again, then retry.
pausedThe employee is paused.Resume them from Team in Pythe.
employeesThe plan has no AI employees.Employees are on Base and Premium.
insufficient_creditsOut of credits.Check get_credit_balance. Credits refill monthly on paid plans.
“That mission was not found or is ambiguous.”The milestone id or title did not match exactly one task.Use the exact id from get_operating_plan.
A client that never shows toolsIt cached old discovery metadata.Restart the client. Claude Code: claude mcp remove pythe and add it again.
HTTP 429 from the REST gatewayOver 60 calls a minute for that key.Wait 60 seconds.
HTTP 401 on /mcp with no tokenExpected: it is the OAuth challenge.Nothing to fix. The client should start the sign-in.

Check it works

  1. Ask the client: “Use Pythe to show my operating plan.” You should see your milestones.
  2. On the Deploy page, check the app appears under Connected apps with the right workspace.
  3. For a REST key, run the diagnostics action. It reports whether the workspace and context are ready.

Related

·