An MCP connection can fail because the server address is wrong, credentials have expired, the provider is temporarily unavailable, or the selected Hand is not ready. Needs attention means you should inspect the connection before using it.
Find the problem
- Open the Hands Console, select your Hand, and go to Integrations → Connectors.
- Filter by Needs attention, if that makes the problem easier to find.
- For a card marked Failed, choose ⋯ → View error information to find the reported failure stage and reason.
- Check the server address, provider status, transport, and expected authentication method. Never send passwords or tokens in a chat message.
Retry a failed setup
- Select Try again on the failed attempt.
- Review the saved non-secret settings. For a custom MCP connection you can correct the server address, transport, and chosen access.
- Re-enter any required bearer token, API key, or secret header value. Hands does not retain those values in the recovery draft.
- Reconfirm that you trust the server and choose Verify and connect.
- Follow the attempt’s progress in Connectors. Connection steps can update automatically; saved does not always mean ready.
To clear a completed failed or interrupted custom MCP setup, select Remove on that failed-attempt card. This discards its saved setup. You cannot use it to remove a successful existing connection; use Disconnect from that connection’s Settings instead.
Repair an existing connection
Open the connector’s Settings and choose the action that matches the status:
- Reauthenticate: if credentials expired or were revoked, sign in again with the service provider.
- Refresh: rediscover tools after a server change, when that option is available.
- Resume sync: continue an operation still in progress rather than starting a competing update.
- Resume: re-enable a connection that was deliberately paused.
- Revoke credentials / Disconnect: withdraw Hands access when you do not want to restore the service.
After recovery, inspect the current status and available tools under Settings → Capabilities. Confirm operation with a harmless read task before attempting a change.
Security and access: revoking a credential in Hands does not prove it was revoked at the provider. Revoke it there separately when necessary. Recovery actions vary by connection state, account and Hand runtime; not every control will appear for every account. For safer access choices, see Connect an MCP server securely.