Lets an AI client interact with your API workspace data, rules and tools to automate API requests and browser traffic changes.
Also known as OpenHeaders/open-headers
- Stars
- 63
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 13, 2026
- License
- Apache-2.0
What is Open Headers MCP?
Open Headers lets an AI client interact with your API workspace data, rules and tools to automate API requests and browser traffic changes.
Summary generated from the project's README
About Open Headers MCP server
Automating API requests and modifying live browser traffic through an AI client is what open-headers enables. This MCP server allows developers to connect their existing AI subscriptions to their API workspace data, rules, and tools. It functions as a bridge between an AI agent and a local-first environment that manages HTTP, GraphQL, gRPC, and WebSocket communications.
Users can interact with a variety of protocols including MQTT, Socket.IO, and SSE. The system supports complex authorization methods like OAuth 2.0, AWS Signature v4, and JWT Bearer. Because it is local-first, your data remains on your machine unless you choose to sync via a self-hosted or remote server. The integration allows an AI to execute requests, manage collections, and utilize the browser interceptor to rewrite responses or inject JS and CSS into live traffic.
What you can do with it
- 1Automate complex API workflowsAn AI client can execute linked requests with specific conditions and extract live variable values from the responses.
- 2Simulate production scenariosUse live variables from API workflows to create realistic testing environments through the browser interceptor.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableopenheaders/open-headers is public and reachablegithub.com/openheaders/open-headers ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-10github.com/openheaders/open-headers ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOpen Headers
![]()
The open-source Enterprise API client in your browser. Team Collaboration. Browser Interceptor - modify live traffic.
Local-first: no account, no cloud, your data stays on your machine.
Website: openheaders.com · Docs: docs.openheaders.com Community: Discord · r/openheaders · Discussions
What it does
API Client — manage and execute requests
- Requests: HTTP, GraphQL, gRPC, MQTT, WebSocket, Socket.IO, SSE
- Structure: Collections > Folders > Requests
- Scripting: pre- and post-response scripts and assertions, with a package library
- Settings: execution and limits, connection, TLS and trust, redirects, cookies, session, session resilience
- Authorization: inherited through the structure, overridable per request: API Key, Basic Auth, Bearer Token, Digest Auth, Hawk, HTTP Message Signature, JWT Bearer, OAuth 1.0, OAuth 2.0, AWS Signature v4, Akamai EdgeGrid, ASAP (Atlassian)
- Specs: OpenAPI 3.1 (HTTP), Protobuf 3 (gRPC), AsyncAPI 3.0 (WebSocket, MQTT), GraphQL schema (GraphQL)
- Delegation: send from the browser extension, or run/delegate the request on the desktop app or the server
- Workflows: schedule multiple linked requests with AND/OR conditions and auto-refresh, then extract live variable values from the responses
- Variables: Workspace (global), Collection, Environment, Vault (secret), Live
Browser Interceptor — modify live browser traffic
- Rules: API HTTP request and response, headers, query params, JS/CSS, WebSocket, SSE, block, redirect, delay, auth challenge
- Structure: Collections > Folders > Rules
- Modify API HTTP responses: mock, or rewrite the server's; body as static data or dynamic JavaScript; optionally modify headers and override the status code
- Modify API HTTP requests: REST or GraphQL; body as static data or dynamic JavaScript
- Modify WebSocket messages and SSE events
- Modify headers, query params and URLs
- Inject JS and CSS
- Block and redirect requests
- Respond to auth challenges
- Variables: every rule reads the same variable scopes; Live variables filled by API Client workflows make prod-like scenarios possible
- DevTools panel: a custom Open Headers panel in the browser's DevTools, with enterprise design and features
Team Collaboration — manage shared workspaces
- Multi-workspace: your personal workspaces and the team's shared workspaces, side by side
- Backup and sync: through a local server you self-host or a remote server you join
- Server features: SSO, RBAC user management, audit logs
- Git integration: durable workspace history, embedded version control tools
- Concurrent multi-user editing: CRDT-flavoured writes for the workspace data
- Work offline: auto-sync when back online
Enterprise Platform — free, like it should be
- Tools: every major feature is embedded in its own Tool panel
- Modern UI: minimalist workbench canvas with two active sidebars and six dock regions
- Modern UX: drag and drop the Tools across the dock regions to group them
- One user interface: desktop app, web app and browser extension (workbench and browser DevTools panel)
- Embedded documentation: info popovers and a Docs Tool with diagrams and text, usable offline
- Git: version control and commit changes directly inside the desktop app
- Traffic: route the browser traffic to the desktop app and modify it there
- AI integration: use your existing subscriptions with the MCP server and automate interaction with your workspace data and Tools
Get started
Install the extension:
Install the desktop app:
Self-host your own server:
To build any app from a fresh clone, see Building each app in the developer guide.
Security & trust
- Security policy — how to report vulnerabilities, safe harbor for good-faith research
- Security whitepaper — the architecture behind the guarantees
- Wire transparency — every outbound call, byte for byte
- Privacy policy — data practices
- Extension permissions — why each browser permission is requested
Documentation
- docs.openheaders.com — quick starts, guides, the server book, command reference
- Architecture overview — the system map
- Developer guide — setup, builds, tests, CI
- Contributing — bug reports, DCO sign-off, feature policy
License
Open Headers is open source under the Apache License 2.0. Official branded binaries and store builds are distributed under the End User License Agreement. Every feature is included in the free tier — the software is identical on every plan, and paid plans exist only to add team seats beyond the free tier's six active users.
Open Headers MCP questions
Does Open Headers require an account or cloud storage?
No, it is local-first: no account, no cloud, and your data stays on your machine.
Can Open Headers modify live browser traffic?
Yes, its Browser Interceptor applies rules to modify requests, responses, headers, query params, WebSocket messages and SSE events.