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

# Welcome

> Aggregate, secure, and observe all your MCP servers behind a single endpoint.

## What is mcp1?

mcp1 is a control plane for the Model Context Protocol. Register any number of backend MCP servers — remote, local stdio, or LAN HTTP — and expose them to your clients through one authenticated, observable endpoint.

## Get started

<CardGroup cols={2}>
  <Card title="Backend servers" icon="server" href="/essentials/backend-servers">
    Register and namespace the MCP servers behind your aggregated endpoint.
  </Card>

  <Card title="API keys" icon="key" href="/essentials/api-keys">
    Create workspace-scoped credentials for your MCP clients.
  </Card>

  <Card title="Workspaces" icon="folder" href="/essentials/workspaces">
    Isolate servers, tools, keys, and traces per tenant.
  </Card>

  <Card title="Tool catalog" icon="wrench" href="/essentials/tool-catalog">
    Toggle individual tools on or off across all connected servers.
  </Card>
</CardGroup>

## Operate

<CardGroup cols={2}>
  <Card title="Request logs" icon="list" href="/essentials/traces">
    Search every call that has passed through the aggregated endpoint.
  </Card>

  <Card title="Health" icon="heart-pulse" href="/essentials/health">
    Check whether each connected backend is reachable.
  </Card>
</CardGroup>

## Guides

<CardGroup cols={2}>
  <Card title="Importing existing servers" icon="download" href="/guides/importing-existing-servers">
    Bulk-register the remote MCP servers already configured in Claude Code or Codex.
  </Card>

  <Card title="Bridge" icon="network-wired" href="/guides/bridge">
    Relay local stdio and LAN HTTP MCP servers into your workspace over an outbound WebSocket.
  </Card>
</CardGroup>