Skip to main content

Connect apps, MCP servers, and APIs to Buzz

Use Connections & access in Workspace settings to let Buzz, Workflows, and Snippets work with your other tools.

Written by Ellen Kajca

Connections let Buzz read data from your other tools and do work in them. You can use a connection in Buzz chat, in Workflows, and in Buzz Snippets.

You add and manage all connections on one page: Connections & access.

Open Connections & access

  1. Click your avatar in the top-right corner.

  2. Under Workspace, click Settings. Make sure Workspace is selected at the top of the settings menu.

  3. Under AI, select Connections & access.

Note: The old link to personal Buzz AI connections now opens this page.

The page has these parts, from top to bottom:

  • Connect your apps — one-click sign-in to popular apps

  • Let Buzz read your apps without asking — a workspace safety setting

  • MCP Connections — tool servers that use the Model Context Protocol

  • API Connections — REST APIs, with Trusted domains at the bottom

Which type of connection do I need?

Type

Use it when

How you sign in

App (Connect your apps)

The app is in the list, for example Slack, Gmail, Google Drive, Microsoft 365, HubSpot, or Notion.

One click. You sign in with your own account.

MCP connection

The tool gives an MCP server URL. An MCP server gives Buzz a ready-made set of tools.

Auto, OAuth, API key in headers, or none.

API connection (REST)

The tool has a REST API but no MCP server. Buzz calls the API endpoints directly.

Auto, OAuth, API key in headers, or session (cookie login).

Tip: Start with Connect your apps. If your app is not in the list, add an MCP connection. If the app has no MCP server, add an API connection.

Connect an app in one click

  1. In Connect your apps, click the app. To see all apps, click the last pill (for example + 88 more apps) and search for the app.

  2. Sign in to the app and allow access.

  3. When you return to Hive, the app shows a check mark.

If the pill shows Finish sign-in, the sign-in is not complete. Click the pill and sign in again.

An app connection starts as private (Only me). Each person in the workspace signs in with their own account.

If the app is not in the list, click Add a custom server to add it as an MCP connection.

Workamajig: Workamajig opens a form, not a sign-in page. Enter the Server URL, the API access token, and the User token, then click Save credentials. To make a company token in Workamajig, go to Admin/Manager → System setup → Connections → API.

Add an MCP connection

  1. In MCP Connections, click New MCP Connection.

  2. Enter a Server Name. You can also add a Description.

  3. Enter the Server URL, for example https://mcp.example.com/mcp.

  4. Select the Authentication Type (see the table below).

  5. Under Who can use this server?, select Only me or Everyone in workspace.

  6. Save the connection. With Auto, the button is Create & Connect. If the server uses OAuth, sign in to the provider when Hive asks.

Authentication Type

What it does

Auto (recommended)

Hive finds out if the server uses OAuth and starts the sign-in for you.

None

For public servers that need no sign-in.

Headers (API Key)

Enter the headers as JSON, for example your API key. Hive encrypts and stores them. You cannot change the headers later. To change them, delete the connection and add it again.

OAuth

Click Discover to fill in the OAuth settings. If discovery fails, enter the client ID, client secret, scopes, authorization URL, and token URL from the provider.

Choose which tools Buzz can use

Each MCP connection gives Buzz a set of tools.

  1. Expand the connection in the list.

  2. Hover over a tool to see if it only reads data or if it can change something.

  3. Click a tool to turn it off. A tool that is off shows with a line through it. Buzz, Workflows, and Snippets cannot use it.

Use Test to check that the connection works. Use the switch on the row to turn the full connection on or off.

Only the connection owner can turn tools or the connection on or off. If you own the connection and OAuth sign-in is not complete, click Click to connect OAuth.

Add an API (REST) connection

  1. In API Connections, click New Connection.

  2. Enter a Connection Name, for example "Stripe API".

  3. Enter a Description. Buzz reads the description to decide when to use the connection, so say clearly what the API is for.

  4. Enter the Origin URL. This is the base address of the API, for example https://api.example.com.

  5. Optional: add a Documentation URL. This helps Buzz call the API correctly.

  6. Select the Authentication Type (see the table below).

  7. Under Who can use this connection?, select Only me, Specific people, or Everyone in workspace.

  8. Click Create Connection (or Create & Connect with Auto).

Authentication Type

What it does

Auto (recommended)

Hive finds the OAuth settings and starts the sign-in. If it cannot find them, select another type.

Headers (API Key)

Click Add Header and enter the key and value. For a bearer token, use the key Authorization and the value Bearer <your token>.

OAuth

Click Discover, or enter the OAuth settings from the provider. Then sign in.

Session (cookie login)

For APIs that use a login request and a cookie. Enter the login path, the cookie names, and the login credentials.

How sharing and sign-in work

  • The person who adds a connection is its owner. Only the owner can edit a connection (name, URL, sign-in, sharing, on/off, and MCP tools) or delete it.

  • Only a workspace admin can mark a connection as trusted.

  • Other people can use a shared connection, but they cannot change it.

  • A shared OAuth connection uses the owner's account for everyone. Only the owner can complete the OAuth sign-in. If Buzz shows Ask the connection owner to authorize, contact the owner.

  • Share a connection only if it is correct for other people to act with that account. For a personal account, select Only me. For team work, use a shared team or service account.

Use connections in Workflows and Snippets

Snippets

  • When Buzz builds a snippet that uses an outside tool, it attaches the connection to that snippet version. The snippet can use only the connections that are attached to it.

  • A snippet can use only connections that are turned on and that the person who runs it can use. For a workflow, this is the workflow owner. A snippet cannot use MCP tools that are turned off.

  • When you import a snippet from the library, select a connection for each item under Required connections. You cannot import the snippet until you select all of them.

For more about snippets, see Using Buzz Snippets.

Workflows

  • A workflow runs as its owner. Its Give Buzz a job and Run a snippet steps use the connections that the workflow owner can use.

  • Before you turn on a workflow, make sure the owner can use each connection it needs. Share the connection with the owner, or ask the owner to add it.

  • Workflow steps do not ask for approval. They read and change data in connected apps without asking, so turn on a workflow only when it is ready.

  • When Buzz tests a workflow or snippet, it usually reads data and simulates changes. Some tests can still send real requests to a connected app. Use test accounts or sample data while you set up a workflow.

For more about workflows, see Buzz Workflows and Create a workflow with Buzz.

Let Buzz read your apps without asking

This setting applies to work Buzz does on its own, such as meeting follow-ups and campaigns. It controls if Buzz must ask before it reads data from a connected app during that work. In that work, Buzz always asks before it changes anything.

This setting does not apply to workflows. Workflow steps read and change data in connected apps without asking.

Under Which apps, select one option:

  • Every app — Buzz can read any connected app without asking.

  • Trusted apps only (default) — Buzz reads trusted connections without asking. It asks for all other apps.

  • None — Buzz asks before it reads any app.

To trust a connection, select Trusted apps only. Then open the ⋯ menu on an MCP or API connection and select Trust for lookups. The connection shows a Trusted badge.

Only workspace admins can change this setting and trust connections.

Trusted domains

Buzz can download files from trusted domains without asking. This list applies to everyone in the workspace.

  1. Expand API Connections and find Trusted domains at the bottom.

  2. Enter a hostname, for example downloads.example.com.

  3. Click Add. To remove a domain, click its trash icon.

Troubleshooting

You see

Do this

An app pill shows Finish sign-in

Click the pill and complete the sign-in.

OAuth not connected or Owner must connect OAuth

The connection owner must sign in to the provider from Connections & access.

Could not detect authentication

Select the Authentication Type that the provider's documentation gives.

A workflow fails at a connection step

Make sure the connection is on and that the workflow owner can use it.

A snippet says a connection is not allowed for this snippet version

Ask Buzz to update the snippet to use that connection, then publish the new version.

A snippet says an MCP tool is disabled for this server

Ask the connection owner to turn the tool on in MCP Connections.

Safety note: Connect Buzz only to tools and endpoints that your organization approves. Follow your company's security policies for outside integrations.

Related Articles
Did this answer your question?