hivy
Documentation
DocumentationConnections and skills

Custom MCP servers

Connect a remote MCP server, choose whose credential it uses, and attach its tools to the right teams or agents.

Add a remote Model Context Protocol server when Hivy's connection catalog doesn't cover the tool you need. Hivy supports Streamable HTTP and HTTP/SSE endpoints; it does not run a local stdio server.

Start with the ownership boundary

Personal server

You own the endpoint and its credential. Attach it only to agents you use.

Organization server

Admins own the endpoint, choose its identity policy, and grant it to teams or named agents.

Video placeholder

Add and test a custom MCP server

Add an HTTPS Streamable HTTP endpoint, choose a safe demo authentication method, test its health, and attach it to one agent. Do not record real credentials.

Add the endpoint

  1. 01

    Name the server

    Use the product or job people will recognize in an agent's tool list.

  2. 02

    Enter its remote URL

    Public endpoints must use HTTPS. Pick Streamable HTTP unless the server uses HTTP/SSE transport.

  3. 03

    Choose authentication

    Save the credential through the form; Hivy never needs it in a skill, prompt, or team environment variable.

  4. 04

    Test before granting access

    A health check confirms that Hivy can reach the server and finish its protocol handshake.

Image placeholder

MCP endpoint, authentication, and access

Capture the MCP server row expanded with transport, authentication status, health, and team or agent assignments visible. Use a demo endpoint.

Choose whose identity the server uses

No authentication
For a public endpoint or one protected by its network.
OAuth
Each member signs in, or admins configure one organization identity.
Bearer token
Hivy sends a private token in the Authorization header.
Custom header
Hivy sends an API key under the header name you provide.
OAuth client credentials
A shared machine identity for organization servers and unattended work.

Per-member identity keeps outside permissions tied to the person who starts the work. An organization identity gives authorized agents one credential that admins maintain, which also fits scheduled runs without a person present.

Personal servers are available in chats you start and schedules you own. Use an organization server for Slack, webhook, or other runs that start without your personal session.

Grant the smallest useful scope

A personal server attaches to selected agents. For an organization server, admins can grant the server to a team or attach it directly to an agent, then remove either assignment without deleting the endpoint.

The server's own authorization still applies after Hivy grants access. A tool cannot reach resources that its saved external identity cannot reach.

Review team access

Re-test after endpoint or credential changes

A saved server can report healthy, degraded, unavailable, or not checked. Fix authentication first when sign-in expired; fix the URL or remote service when Hivy cannot connect at all.