Uno MCP
MCP troubleshooting
Resolve connection, permission, and execution issues.
| Symptom | What to do |
|---|---|
| Sign-in opens but access is unavailable | Finish Uno verification and onboarding; check for a waitlist message. |
| OAuth never completes | Check that the client supports HTTP MCP, OAuth, its callback URL, and PKCE. |
| Wrong workspace | Revoke the connection in Uno and reconnect with the intended workspace. |
| Connection stopped after a permission update | Revoke and reconnect to review the current consent. |
| Tool returns 401 | Authenticate again; the token or grant may have expired or been revoked. |
| Tool returns 403 | Check your current workspace membership and role. |
| Session is ready but no work appears | Inspect conversation status; a ready environment does not prove a turn was accepted. |
| Advanced creation produced an idle session | Include body.initialConversation.message when execution is intended. Inspect existing messages before recovery. |
| Mutation timed out | Check persisted status, then retry with the same key and identical arguments. |
| Steering says unsupported | The runtime needs an upgrade; do not cancel work or resend it as a duplicate message. |
| Steering accepted but no delivery | Check get_conversations_steering by request ID; acceptance and delivery are separate. |
| Result too large | Use pagination and narrower filters. |
| Temporary 429 or 5xx response | Retry later with backoff; preserve operation keys for mutations. |
Inspect before retrying
Use get_conversations_status, get_conversations_activity, and get_conversations_messages to understand the current work. Follow safe retries instead of generating another request ID after an uncertain response.
Connection or server availability
The hosted endpoint is https://api.uno.engineering/mcp. Configure the exact path and use OAuth. Ordinary Uno tokens, workspace API keys, and internal sandbox tokens are not substitutes for hosted MCP authorization.