An MCP connection enables your Hand to call tools on another server. A curated MCP connector may provide its own server settings; a custom MCP server requires you to provide them. Only connect to a service and operator you trust.
Before connecting
Select a ready, supported Hand. For a custom server, obtain its public HTTPS URL and ask the provider whether it uses Streamable HTTP or SSE. Check whether authentication requires no credentials, a bearer token, an API key, or custom headers. Never paste credentials into chat or published examples.
Connect the server
- Open the Hands Console, select your Hand, and go to Integrations → Connectors.
- Select a listed connector, or select + to add a custom MCP server.
- For a custom connection, enter a recognizable Connection name, the Server URL, and the transport supported by the server.
- Under Authentication, choose None, Bearer token, API key header, or Custom headers, as directed by the provider. Enter any secret only in its dedicated credential field.
- Expand Access and review Read only versus Read and write. Prefer Read only where Hands can verify provider-documented read tools. That option is not available for every server; the form may initially select Read and write.
- Read the confirmation identifying the server and requested access. Check the trust box only when you agree, then select Verify and connect.
With Read and write, review the action rules immediately after connecting: writable tools may initially be Automatic.
A curated connector may lock or supply some of these fields. Provider-specific authorization can take place in a separate interface.
Verify and manage your connection
Discovery may take multiple steps. A Connecting progress card or a saved setup is not proof the server is ready. Return to Connectors, check the current status, and open Settings → Capabilities to inspect the access level and enabled tool counts. Start with a safe read action.
For a Read and write connection, go to Action rules to choose whether each supported non-read tool is blocked, requires approval, or may run automatically. See Approve or automate MCP tool actions. A per-tool setting cannot grant access beyond the connection’s scope.
When available in Settings, use Pause, Refresh, Revoke credentials, or Disconnect to change or end access. Revoking credentials in Hands does not necessarily revoke them at the provider. For failed setup, see Recover a failing MCP connection.
Availability: the endpoint, provider authorization, selected Hand, and its runtime must all support the connection. Even a previously connected server is checked again when tools are used.