Skip to main content
This page is for admins. Some tools need to run on each person’s laptop rather than in Barndoor’s cloud: reading local files, running git or aws, talking to a local Docker daemon. Bridge runs these as local MCP servers, under the same policies, approvals, data protection, and audit as your remote servers. There are two kinds: Local servers run only in sessions Bridge launches. A claude.ai connector or other hosted route to Barndoor lists them but can’t run them.

Turn on a built-in server

1

Turn the server on

In MCP Servers, open the server, select Configure, and switch Enabled on. If it isn’t listed, or you want a second copy with different configuration, go to MCP Servers → Add MCP Server, choose the Local filter, and select Add New on it.Set Who gets it:
  • Users who connect it (the default): each person turns it on with Connect in My Apps.
  • Everyone: every Bridge in your organization runs it, with nothing for people to do.
Fill in Configuration if the server has any; see Built-in servers.
2

Grant it in a policy

Barndoor refuses every tool no policy grants. In the Access Control Center, create a policy for the server and set each tool to Always Allow, Needs Approval, or Off; see Manage policies. Set tools that change things, such as writes, deletes, and deploys, to Needs Approval, so people approve each call after seeing exactly what it will do.
3

Check it on a laptop

Bridge picks the server up on its next sync, within about five minutes, or right away with barndoor sync. It then appears on the Bridge window’s Servers tab and in barndoor list. People start a new session to get it; a session that’s already open keeps the servers it started with.

Built-in servers

Each server uses what’s already on the laptop and the person’s own sign-ins: their AWS profiles, kubeconfig, Google credentials, or gh login. It reaches only what that person can already reach. Bridge also has a few internal tools that are always on and don’t appear in MCP Servers: memory across sessions, session management, skills, and small utilities such as base64 and JSON formatting.

Shell

Bridge’s Shell server is separate from the client’s own shell, such as Claude Code’s Bash. Client settings decide which one a session uses:
  • Native (the default): the client uses its own shell.
  • Through Barndoor: the client’s own shell is removed and it runs commands with Bridge’s Shell server, so every command is checked by policy and audited. Make sure the Shell server is on for everyone those sessions are for, for example with Who gets it set to Everyone, or they have no shell at all.
Deny command patterns in client settings apply to Bridge’s Shell server as well as the client’s own shell.

How local servers are governed

  • Policy and approvals work as they do for remote servers. A tool set to Needs Approval asks the person in every client before it runs.
  • Data protection: MCP data protection policies scan local tool calls, and can redact or block them. If Bridge can’t get a verdict, the call is refused.
  • Audit: each call appears in the audit log and on the MCP Usage Dashboard under the server’s name.
  • Nothing else runs. Under Models and MCP, Bridge launches each client with Barndoor as its only MCP server, so a local server someone adds to Claude Desktop, or a plugin’s, doesn’t load.

When a local server doesn’t work

For more, see Monitor and troubleshoot.