Hands
Use cases
Apps
Insights
Handbook
Pricing
NL
Sign in Get started with Hands
MCP connectors

MCP connectors for the AI you already use

Give your Hand a controlled path to external tools through MCP. Choose a server from the catalogue or add your own public HTTPS remote MCP server with the authentication it requires.

87 MCP connectors

The tools you can use depend on the MCP server and the account or key you connect.

How MCP connections work

One Hand, the AI client you prefer, and only the tools you connect.

An MCP connector is a remote server that exposes tools to a compatible AI client. Hands gives each Hand its own runtime and workspace; the connected MCP server determines which tools and provider access are actually available.

Use a compatible AI client

Connect your Hand to a supported AI client through MCP, so the same workspace and connected tools remain available without rebuilding the working environment for every conversation.

See how AI connects to a Hand

Bring your own MCP server

Add a public HTTPS remote MCP server when the service you need is not in the catalogue. Depending on that server, setup can require a bearer token, API key or custom headers.

Plugins and Connectors are different

Hands-managed Plugins use a managed connection flow. MCP Connectors are remote servers you connect through MCP. Choose the route that matches the integration you actually need.

Compare Plugins and MCP Connectors
Access and permissions

Connect only the access your Hand needs.

An MCP connection can use the permissions of the account or key you provide. Hands can only limit those permissions where the connection supports it. Choose accounts, keys and headers with no more access than this Hand needs.

Start with one useful connection

Start with the MCP connections the task actually needs.

Get started with Hands