All docs

Connections and the BeyDock Hub

Set up MCP servers once, share them with every provider and account, and control and audit what agents can call.

Home › Connections is where you manage what your agents can reach: MCP servers, plugins and skills. It reads what your providers already have, showing names only and never secret values. It also adds BeyDock's own tools and the BeyDock Hub.

What is on the page

  • BeyDock is built in. It has two tool groups, Agents (see Delegation) and Workflows, each with an on and off switch. They work even when the Hub is off.
  • MCP Servers, Plugins and Skills are grouped by kind. Use the All, MCP, Plugins and Skills filter, and the device filter if you have SSH hosts.
  • The toolbar has Refresh, an undo button, Install Plugin and Add Server. With the Hub on, it also has Connect an App.

The BeyDock Hub

A provider's own MCP setup works only in that provider, and often only in one account. The Hub is a local process that holds the real connections. You set a server up once and every provider and account can use it. Agents see one server named beydock. Secrets live in the macOS Keychain.

The Hub is off by default. Turn it on under Settings › Connections › Use BeyDock Hub. Turning it off keeps your sign-ins.

Add a server

  1. Turn on Use BeyDock Hub in Settings › Connections first: servers are added to the Hub. Then click + (Add Server) on the Connections page.
  2. Choose Enter Manually or Paste JSON.
  3. Enter a Name and a tool prefix. Tools reach agents as prefix__tool_name, and the prefix can't be changed later.
  4. Choose the Type: Command, HTTP or SSE, and fill in the command or URL, plus Environment or Headers.
  5. For a Command server, choose the Scope: Workspace or Shared. Shared may let one project read another's files if the server works on folders.
  6. Under Available in, turn off any provider whose sessions shouldn't get this server's tools. A Command server can also Run on another device when you have more than one.
  7. Click Test Connection to check it.
  8. Review the preview and confirm. Nothing is added until you do. If the server needs a sign-in, BeyDock opens your browser once.

Move existing servers into the Hub

For a server that lives in a provider's own settings, open its row and click Move to Hub…. BeyDock shows exactly what will change. The original is turned off, never deleted. If a server has several copies, use Consolidate to Hub…, or Consolidate All to Hub… in the ⋯ menu. The undo button in the toolbar reverts the last move or change, and Move Back… on a Hub server restores the original.

Sessions that are already open pick up the change when they restart. Claude can refresh the Hub connection live.

Rules and Activity

On a Hub server, set Allow, Ask or Deny for each tool, or for all tools, for everyone or customized per provider, account, connection or connected app. Pause all, at the top of the page, denies every tool call through the Hub from all sessions and apps until you turn it off. Only servers in the Hub are covered by these rules.

Activity logs every tool call that goes through the Hub, on this Mac only. Results are never stored, only their size. In Settings › Connections you can choose Keep activity for, turn off Record arguments, and Clear Activity….

Several sign-ins for one server

A server can have more than one connection, such as two Notion workspaces. Each of your accounts uses one connection. You can also Expose all connections so one session can use several. Values go to the Keychain and are never shown again.

Use the Hub from other apps

Click Connect an App to use your Hub servers in Claude Desktop, Cursor, VS Code, Zed, Claude Code, Codex or any other MCP client. For Claude Desktop, Cursor, VS Code and Codex, Add to <App> writes the configuration for you, with a diff and a backup. For the others, use Copy Configuration. Each app gets its own token and a stricter policy. Read-only tools are allowed and everything else asks first.

By default the Hub runs only while BeyDock is open. Turn on Settings › Connections › Keep Hub running in the background to start a small helper at login, so other apps keep working when BeyDock is closed.

Plugins

Install Plugin runs the provider's own plugin command. Plugins belong to a provider and are shared by all of its accounts.