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

# Fleet (Servers)

> Manage your docked MCP servers from the Fleet page.

The **Fleet** page is where you manage all your docked MCP servers — both local stdio servers and remote HTTP servers.

## Adding a Server

1. Click **Dock Ship** at the top of the page
2. Fill in the server details:
   * **Name** — A unique identifier for the server
   * **Command** — The executable to run (for stdio servers), or **URL** for remote HTTP servers
   * **Arguments** — Command-line arguments
   * **Environment Variables** — Key-value pairs. Use `vault:SECRET_NAME` to reference secrets stored in the [vault](/guides/vault)
3. Click **Save** to dock the server

<Tip>
  For the fastest setup, use the [Native Fleet](/desktop/marketplace) on the Scout page to dock pre-configured servers with one click.
</Tip>

## Managing Servers

Each server card shows its name, command (or URL for remote servers), status, and a toggle switch to enable or disable it.

| Action            | Description                                                             |
| ----------------- | ----------------------------------------------------------------------- |
| **Toggle switch** | Enable or disable the server. Disabled servers are not synced to hosts. |
| **Remove**        | Permanently undock the server from Harbor                               |
| **Tool Filters**  | Expand a server to discover its tools and configure allow/block lists   |
| **Edit Args**     | Modify the server's arguments or extra args                             |

## Remote Servers

Servers docked with a URL (instead of a command) are remote HTTP MCP servers. These are indicated with a globe icon. Remote servers connect over HTTP/SSE and support `vault:` references in headers for authentication.

## Tool Filtering

Expand any running server to see its available tools. You can:

* **Search** tools by name
* **Block** individual tools to hide them from hosts
* **Allowlist** specific tools to expose only those
* Set **per-host overrides** so different hosts see different tools

## Fleet-Managed Servers

Servers shared via [team fleet sync](/guides/team-sync) are distinguished by status badges on their cards:

| Badge      | Color | Meaning                                                                      |
| ---------- | ----- | ---------------------------------------------------------------------------- |
| `fleet`    | Blue  | Server is managed by the shared fleet and matches the last-pulled definition |
| `modified` | Amber | Server definition has drifted from the fleet since the last pull             |

A `modified` badge means you have edited the server locally. Harbor skips it on the next `harbor crew pull` to protect your changes. To resolve, either accept the upstream version (`harbor undock <name>` then `harbor crew pull`) or share your version with the team (`harbor crew push <name>`).

## Syncing to Hosts

<Note>
  Syncing is **automatic**. When you dock, undock, toggle, or modify a server, Harbor immediately pushes the updated fleet to all linked hosts. No manual sync step needed.
</Note>