Skip to main content
The Connections catalog contains hosted integrations and a custom MCP option. In both cases, connect the service first, then configure scope and permissions.

​
Hosted integrations

Hosted integrations use the service’s authorization flow so you can grant access without sharing an account password with a Righthand. Depending on the service, Righthand completes that flow through an integration provider such as Composio or Pipedream. Use a hosted integration when the service appears in the catalog. During authorization:
  • Sign in to the exact account you intend to connect.
  • Review the access the provider requests.
  • Complete any administrator approval required by your organization.
  • Return to Righthand and assign the connection to the intended Righthands.

​
Custom MCP servers

MCP (Model Context Protocol) lets a Righthand use tools exposed by a compatible server. Choose MCP (Custom) in the connection catalog, then provide:
  • The MCP server URL.
  • An optional display name.
  • Authentication requested by the server, if any.
Righthand probes the server and follows the authentication method it advertises. The flow may finish without authentication, redirect you through OAuth, or ask for authentication headers such as an API key or token.
Connect only MCP servers you trust. The tools and data available to a Righthand are determined by the server as well as by the permissions you configure in Righthand.
Authentication headers are verified against the server and stored encrypted. They are not shown to the Righthand.

​
GitHub for a Righthand developer account

The GitHub control under an individual Righthand’s Manage area uses a personal access token, not the general connection catalog. Follow Setting Up GitHub for that flow.

​
Which option should I use?

If the service is not in the catalog and does not expose a compatible MCP server, contact support@humans.righthand.ai before sharing credentials by another method.