# Open Headers

> Documentation for Open Headers — the open-source DevToolkit for live browser traffic: rules, API client, network inspection, workspaces, and self-hosted sync.

## Docs

- [Open Headers documentation](https://docs.openheaders.com/index.md): The open-source DevToolkit for live browser traffic — rules, API client, network inspection, workspaces, and self-hosted sync.
- [Extension quick start](https://docs.openheaders.com/quickstart/extension.md): Install the Open Headers extension from your browser's store and put your first rule on live traffic.
- [Desktop quick start](https://docs.openheaders.com/quickstart/desktop.md): Install the Open Headers desktop app, understand the tray model, and pair it with the browser extension.
- [Server quick start](https://docs.openheaders.com/quickstart/server.md): Install the Open Headers Server, mint your first token, and connect a client — on your machine or your LAN — in about ten minutes.
- [MCP quick start](https://docs.openheaders.com/quickstart/mcp.md): Connect an AI agent to Open Headers over the Model Context Protocol — rules, requests, and workflows as tools.
- [Guides](https://docs.openheaders.com/guides/index.md): Task-shaped how-tos for rules, workspaces, variables, imports, and more.
- [Open Headers Server](https://docs.openheaders.com/server/index.md): The self-hosted back-end tier: what it is, what it serves, and where to find every operating task.
- [Install & service lifecycle](https://docs.openheaders.com/server/install.md): Install ohd, run it as a user service under launchd or systemd, and learn where configuration, state, and logs live.
- [LAN vs TLS proxy](https://docs.openheaders.com/server/lan-vs-tls.md): Decide how connections to the daemon are protected once it leaves loopback — cleartext on a trusted LAN, or TLS terminated at a reverse proxy.
- [Docker & Compose](https://docs.openheaders.com/server/docker.md): Run the Open Headers Server as a container: image, volume, ports, version pinning, and a Compose file.
- [Tokens & pairing](https://docs.openheaders.com/server/tokens-and-pairing.md): Mint the first client token, join clients, and understand the admission and rate-limit rules every route enforces.
- [Users, seats & SSO](https://docs.openheaders.com/server/users-sso.md): Manage the daemon's user directory, workspace grants, seat limits, local passwords, and OpenID Connect login.
- [Backup & restore](https://docs.openheaders.com/server/backup-restore.md): Take checksummed snapshots of the daemon's state and restore them safely.
- [Upgrade](https://docs.openheaders.com/server/upgrade.md): Move the server to the newest release with one command, or opt into unattended upgrades.
- [Observability](https://docs.openheaders.com/server/observability.md): The audit log, the /metrics snapshot, and the daemon's log format.
- [Troubleshooting](https://docs.openheaders.com/server/troubleshooting.md): Symptom → cause → fix for every dead end a self-hosted deployment can hit, with the daemon's error messages quoted verbatim.
- [Reference](https://docs.openheaders.com/reference/index.md): Command, configuration, and constants reference — generated from source.
- [API & MCP](https://docs.openheaders.com/api-mcp/index.md): The HTTP API reference and the MCP tool reference.

## OpenAPI Specs

- [openapi](https://docs.openheaders.com/api-reference/openapi.json)

## Optional

- [Changelog](https://openheaders.com/changelog)
- [GitHub](https://github.com/OpenHeaders/open-headers)