> ## Documentation Index
> Fetch the complete documentation index at: https://docs.barndoor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Local MCP servers

> For admins: turn on the MCP servers that run on each person's laptop, such as Shell, Filesystem, Git, and AWS CLI, and how they're governed.

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:

| | What it is | Set up |
| - | - | - |
| **Built-in** | Servers compiled into Bridge, such as Shell, Filesystem, Git, GitHub Local, AWS CLI, Kubernetes, and Docker. Every organization has them, switched off. | [Turn one on](#turn-on-a-built-in-server), below. |
| **Your own** | An MCP server your organization builds or chooses, signed with your key and pinned on laptops with MDM. | [Publish a local MCP server](https://docs.barndoor.ai/how-tos/barndoor-bridge/publish-local-mcp.md). |

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](#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](https://docs.barndoor.ai/how-tos/manage-policies.md). 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.

| Server | What it does | Needs on the laptop | Configuration |
| - | - | - | - |
| **Shell** | Runs shell commands. | A shell. | None. See [Shell](#shell). |
| **Filesystem** | Reads and writes files. | Nothing. | Each person sets **allowed paths** when they connect it. Otherwise, their home folder and temporary folders. |
| **Git** | Runs Git operations on local repositories. | `git` | None. |
| **GitHub Local** | Works with GitHub as the person. | A `GITHUB_TOKEN`, or a `gh` sign-in. | None. |
| **AWS CLI** | Runs AWS commands with the person's own profiles, so CloudTrail records them. Refuses interactive sessions, config writes, and commands that print credentials. | AWS CLI v2. | None. |
| **Kubernetes** | Works with Kubernetes clusters. | A kubeconfig. | Optional default context. |
| **CloudNative-PG** | Manages CloudNative-PG Postgres clusters in Kubernetes. | A kubeconfig. | None. |
| **ArgoCD** | Works with Argo CD applications. | An Argo CD server and token, from the Argo CD config or environment. | Each person can enter a server and token when they connect it. |
| **Docker** | Works with containers and images. | A running Docker daemon. | None. |
| **Terraform** | Runs Terraform. | `terraform` | None. |
| **PostgreSQL** | Queries PostgreSQL databases. | Nothing. | Read and write connection URLs, and the sign-in method. Write tools refuse to run without a write URL. |
| **gcloud CLI** | Runs `gcloud` commands. | `gcloud` | None. |
| **Google Cloud** servers: Observability, Storage, Backup and DR, Secret Manager, BigQuery, Resource Manager, IAM, Compute Engine, Artifact Registry, Pub/Sub | Work with that Google Cloud service. | Google Application Default Credentials (`gcloud auth application-default login`). | None. |
| **Playwright Browser Automation** | Drives a headless browser. | Internet access on first use, to download its browser. | None. |

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](https://docs.barndoor.ai/how-tos/barndoor-bridge/client-settings.md#shell) 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](https://docs.barndoor.ai/how-tos/data-control-center/mcp-policies.md) 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](https://docs.barndoor.ai/how-tos/read-mcp-usage-dashboard.md) 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

| What people see | Cause | Fix |
| - | - | - |
| The server isn't on the **Servers** tab or in `barndoor list` | It's off, the person hasn't connected it, or Bridge hasn't synced. | Check the server is enabled and, for **Users who connect it**, connected in **My Apps**. Then `barndoor sync`. |
| `This tool is blocked by policy.` | No policy grants the tool. | [Grant it in a policy](#turn-on-a-built-in-server). |
| `runs locally via barndoor-cli and is not executable through the platform router` | The call went through a hosted connection to Barndoor, not Bridge. | Launch the client from Bridge. Under **MCP only**, see [If people also have the hosted Barndoor connector](https://docs.barndoor.ai/how-tos/barndoor-bridge/mcp-only.md#if-people-also-have-the-hosted-barndoor-connector-in-claude). |
| A command-line tool isn't found, or a sign-in has expired | The tool the server uses, such as `aws` or `gcloud`, isn't installed or isn't signed in. | Install it, or sign in, on the laptop. |

For more, see [Monitor and troubleshoot](https://docs.barndoor.ai/how-tos/barndoor-bridge/monitor-and-troubleshoot.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.