Skip to content

MCP Servers

MCP (Model Context Protocol) servers give the agent tools: query an internal recon API, look something up in your asset inventory, open a ticket. Servers you add here are pushed to every member’s Desktop.

Members’ Desktop apps never receive the server’s real address or credential. Desktop only gets a path on your instance. When the agent calls a tool:

  1. Desktop sends the call to your instance, signed in as the member.
  2. Your instance checks the member still belongs to the organization, adds the stored credential, and forwards the call to the real server.
  3. The response goes back the same way.

So you can rotate or revoke the credential in one place, removing a member cuts off their tool access along with everything else, and a lost laptop doesn’t leak your API keys.

Every tool call is recorded in the change log as mcp_server.tool_called with the member, server and tool name. Arguments and results aren’t recorded.

  1. Under Add a server, fill in:
    • Name: what members will see, such as Acme Internal Recon API.
    • URL: the server’s HTTP-transport MCP endpoint, such as https://tools.acme.internal/mcp. It must be reachable from your instance.
    • Auth header name: the header the server expects. Defaults to Authorization.
    • Credential: the header’s full value, such as Bearer sk-.... Leave blank for a server that needs no authentication.
  2. Click Add server.

New servers are Pushed immediately and appear in members’ Desktop within 10 minutes, with an org badge.

  • The switch on each card sets Pushed or Off. Turning it off asks you to confirm, then removes the server from members’ Desktop at their next refresh and disconnects it.
  • Expand Edit to change the name, URL, header name or credential. Leave Credential blank to keep the current one. The card only ever shows configured or none, never the value.
  • Delete server removes it from the instance and every member’s Desktop.

Members can switch an org server off on their own machine, but they can’t edit or remove it.

The Allow members’ own MCP servers switch at the top decides whether members may also add MCP servers of their own in Desktop. Flipping it either way asks you to confirm.

  • Allowed (the default): members can add personal servers alongside yours.
  • Blocked: Desktop hides the option to add a server and disconnects any personal servers members already added. Your pushed servers and Hacker Sidekick’s built-in server keep working. If you switch back to Allowed, members’ personal servers reconnect.

Block personal servers when you need every tool the agent can reach to be one you’ve approved.