Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

mcp-airlock

by Shalimov04version 0.2.0i★ 15iRuns on your computerRepository ↗
Registry nameio.github.Shalimov04/mcp-airlock

How to install

What it does

Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit

  • Connects Runs on your computer
  • Account or key Needs AIRLOCK_JWT_SECRET, AIRLOCK_SECRET
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity14/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score26/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install mcp-airlock. Follow https://mcp.popnx.com/i/shalimov04-mcp-airlock.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server mcp-airlock for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "airlock": { "command": "uvx", "args": [ "mcp-airlock", "--policy", "--upstream", "--env", "prod" ], "env": { "AIRLOCK_JWT_SECRET": "your-value", "AIRLOCK_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AIRLOCK_JWT_SECRET, AIRLOCK_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the mcp-airlock tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a mcp-airlock key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  4. Paste these settings and save the file

    {
      "mcpServers": {
        "airlock": {
          "command": "uvx",
          "args": [
            "mcp-airlock",
            "--policy",
            "--upstream",
            "--env",
            "prod"
          ],
          "env": {
            "AIRLOCK_JWT_SECRET": "your-value",
            "AIRLOCK_SECRET": "your-value"
          }
        }
      }
    }

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Quit Claude and open it again

  6. Try it

    Use mcp-airlock and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using mcp-airlock or shows a mcp-airlock tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect mcp-airlock yet

mcp-airlock runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect mcp-airlock

  • You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)
  • You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
  • You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server mcp-airlock for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user airlock --env AIRLOCK_JWT_SECRET=your-value --env AIRLOCK_SECRET=your-value -- uvx mcp-airlock --policy --upstream --env prod 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AIRLOCK_JWT_SECRET, AIRLOCK_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the mcp-airlock tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a mcp-airlock key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  4. Paste this command and press Enter

    claude mcp add --scope user airlock --env AIRLOCK_JWT_SECRET=your-value --env AIRLOCK_SECRET=your-value -- uvx mcp-airlock --policy --upstream --env prod

    Replace “your-value” with your key before pressing Enter

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Type /mcp in Claude Code

    You should see mcp-airlock listed as connected

  6. Try it

    Use mcp-airlock and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using mcp-airlock or shows a mcp-airlock tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server mcp-airlock for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "airlock": { "command": "uvx", "args": [ "mcp-airlock", "--policy", "--upstream", "--env", "prod" ], "env": { "AIRLOCK_JWT_SECRET": "your-value", "AIRLOCK_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AIRLOCK_JWT_SECRET, AIRLOCK_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the mcp-airlock tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a mcp-airlock key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open Cursor’s MCP settings file

    ~/.cursor/mcp.json

    Paste these settings, fill in the empty values and save

    {
      "mcpServers": {
        "airlock": {
          "command": "uvx",
          "args": [
            "mcp-airlock",
            "--policy",
            "--upstream",
            "--env",
            "prod"
          ],
          "env": {
            "AIRLOCK_JWT_SECRET": "your-value",
            "AIRLOCK_SECRET": "your-value"
          }
        }
      }
    }
  4. Fill in your key

    In the mcp-airlock settings, AIRLOCK_JWT_SECRET, AIRLOCK_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in Cursor in Agent mode

  6. Try it

    Use mcp-airlock and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using mcp-airlock or shows a mcp-airlock tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

You need a mcp-airlock key (create it on the maker’s site) · Install Python (uv) on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server mcp-airlock for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "airlock": { "type": "stdio", "command": "uvx", "args": [ "mcp-airlock", "--policy", "--upstream", "--env", "prod" ], "env": { "AIRLOCK_JWT_SECRET": "your-value", "AIRLOCK_SECRET": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For AIRLOCK_JWT_SECRET, AIRLOCK_SECRET, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the mcp-airlock tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Sign up and create a mcp-airlock key

    Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.

    How to get a key is in the maker’s README below

  3. Open VS Code’s MCP settings file

    MCP: Open User Configuration

    Paste these settings, fill in the empty values and save

    {
      "servers": {
        "airlock": {
          "type": "stdio",
          "command": "uvx",
          "args": [
            "mcp-airlock",
            "--policy",
            "--upstream",
            "--env",
            "prod"
          ],
          "env": {
            "AIRLOCK_JWT_SECRET": "your-value",
            "AIRLOCK_SECRET": "your-value"
          }
        }
      }
    }
  4. Fill in your key

    In the mcp-airlock settings, AIRLOCK_JWT_SECRET, AIRLOCK_SECRET is empty; add your key and save

    Paste the key only into the app’s field, never into a chat or to anyone

  5. Open the AI chat in VS Code in Agent mode

  6. Try it

    Use mcp-airlock and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using mcp-airlock or shows a mcp-airlock tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use mcp-airlock💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user airlock --env AIRLOCK_JWT_SECRET=your-value --env AIRLOCK_SECRET=your-value -- uvx mcp-airlock --policy --upstream --env prod

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "airlock": {
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--policy",
        "--upstream",
        "--env",
        "prod"
      ],
      "env": {
        "AIRLOCK_JWT_SECRET": "your-value",
        "AIRLOCK_SECRET": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "airlock": {
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--policy",
        "--upstream",
        "--env",
        "prod"
      ],
      "env": {
        "AIRLOCK_JWT_SECRET": "your-value",
        "AIRLOCK_SECRET": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "airlock": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--policy",
        "--upstream",
        "--env",
        "prod"
      ],
      "env": {
        "AIRLOCK_JWT_SECRET": "your-value",
        "AIRLOCK_SECRET": "your-value"
      }
    }
  }
}

Values you fill in

  • AIRLOCK_JWT_SECRET secret required env
    HS256 secret for verifying bearer tokens (or set AIRLOCK_JWKS_URL for OIDC)
  • AIRLOCK_SECRET secret required env
    Key for signing confirmation tokens; set it when running more than one replica

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
33/wk
Connection
Runs on your computer
Transport
streamable-http
Latest versioni
0.2.0
Categoryi
Other
Published to registryi
Sep 16, 2026
Code last changedi
Nov 7, 2026
Maker
Shalimov04
Packages
pypi: mcp-airlock
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Shalimov04, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 12 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for mcp-airlock@0.2.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/shalimov04-mcp-airlock.svg)](https://mcp.popnx.com/en/servers/shalimov04-mcp-airlock)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 97% of the other 20749 servers in this category
  • Published to the registry more recently than 39% of the other 20749 servers in this category
  • Basic checks equal to or better than 99% of the other 20749 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is mcp-airlock safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: AIRLOCK_JWT_SECRET, AIRLOCK_SECRET

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 12 days ago, and the latest version (0.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
mcp-airlock
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyYesNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

mcp-airlock

Краткий обзор по-русски

mcp-airlock is a proxy you put between an AI agent and an MCP server when the server can do things you don't want an agent doing on its own. It speaks the 2026-07-28 revision of the protocol (the stateless one: no session, no initialize, one POST per request) and adds the parts the protocol leaves to you: who is allowed to call what, dry runs by default, a human in the loop for dangerous calls, an audit trail and tracing.

It is deliberately small. There is no UI, no policy language beyond flat YAML, no MCP SDK of its own. The whole proxy is one Starlette app plus a few helper modules.

How a call goes through

The agent sends a normal tools/call to the proxy instead of the server. The proxy:

  1. Works out who is calling. That comes from a JWT (Authorization: Bearer) or, if you run it behind a gateway that already did the authentication, from an X-Airlock-Principal header. It is never taken from the request body. No principal, no call. A name that is blank or has whitespace around it is no principal either, from either source: trimmed, alice would be alice.
  2. Looks the tool up in the policy. Tools that are not listed are refused. Listed tools have a risk tier per environment, so the same delete_service can be free in dev and gated in prod.
  3. Depending on the tier:
  • L0 (read) goes straight through.
  • L1 (suggest) always goes through with dry_run: true, whatever the agent asked for.
  • L2 (confirm) goes through with dry_run: true first, and the result comes back to the agent as input_required with a description of what would happen and a signed requestState. When a person says yes, the agent repeats the call with that state and the proxy executes it for real, once. Repeating it again is refused.
  • L3 (auto) goes through as sent.
  1. Checks the blast radius: how many objects one call touches (the length of a list argument you name in the policy) and how many a principal has touched in the last hour or day.
  2. Forwards the call, cuts the response down to the output cap if it is too big, and marks anything in it that smells like a prompt injection. Marking only; it does not change what the agent gets to see.
  3. Writes two audit records, one before the upstream call and one after, whatever happened. The JSONL file gets each one before the proxy goes on; the Postgres table, when there is one, is written from a queue a moment later.

Refusals come back as tool results with isError: true, not as protocol errors, so the model sees why and can do something else. Every tools/call result, a pending one included, carries the verdict and the rule that produced it in _meta. The io.mcp-airlock/ keys there are the proxy's alone: any the upstream puts into a result, one of its content blocks, a tools/list answer or a tool in it are removed before the proxy adds its own, and any the client sends are removed before the call is forwarded.

The proxy accepts three methods: tools/call as above, tools/list and server/discover. A tools/list answer is cut down to the tools the policy lists for the caller (the number of hidden tools is in _meta["io.mcp-airlock/hidden_tools"]), then checked against the pins and scanned for injection phrases. Any other method is refused with METHOD_NOT_FOUND.

Protocol-level answers
  • Missing principal: HTTP 401 / -32011 (PRINCIPAL_REQUIRED) when there is no JWT and no trusted X-Airlock-Principal header.
  • Unproxied method: HTTP 404 / -32601 (METHOD_NOT_FOUND) for anything but tools/call, tools/list and server/discover. A legacy initialize has no _meta envelope and gets HTTP 400 / -32602 instead.
  • Order: protocol rejections (-32700, -32600, -32602, -32020, all HTTP 400, and -32601/404) are answered before the missing-principal 401, so an unauthenticated client can tell a malformed request from a refused one. These cover the 2026-07-28 _meta envelope and the Mcp-Method/Mcp-Name header checks.
  • Forwarded `requestState`: one without the al1. prefix is forwarded as upstream state, so a token that lost its al1. prefix is treated as a new call.

Installing

From PyPI, as a tool or a package:

uvx mcp-airlock --help

pip install mcp-airlock

Three features are extras, so the base install stays small:

ExtraBringsNeeded for
postgrespsycopg, psycopg-poolAIRLOCK_STORE_DSN, AIRLOCK_AUDIT_DSN, airlock-audit query --dsn
otlpthe OTLP HTTP span exporterOTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
regexgoogle-re2a where rule with regex
uvx --from 'mcp-airlock[postgres,otlp,regex]' mcp-airlock ...

pip install 'mcp-airlock[postgres,otlp,regex]'

A DSN without the postgres extra stops the proxy at startup with that hint. An OTLP endpoint without the otlp extra is a startup warning (an error under --strict) and the proxy runs without exporting. A policy with a regex rule does not load without the regex extra and says to install it. google-re2 ships wheels for glibc 2.27+ Linux, macOS and Windows, but none for musl (Alpine).

The container image ghcr.io/shalimov04/mcp-airlock includes all three extras. It listens on 0.0.0.0:9000, runs as a non-root user and has /data as its working directory, so audit.jsonl lands there. The user is uid 65532, so a host directory bind-mounted at /data has to be writable by that uid (chown 65532 ./data), or the start stops with a Permission denied message for the audit file. Each release is tagged with its version and its major.minor (X.Y.Z and X.Y).

From a checkout, uv sync --all-extras installs everything including the test tools.

Running it

The released version, no clone needed:

AIRLOCK_TRUST_PRINCIPAL_HEADER=1 uvx mcp-airlock --policy policy.yaml --upstream http://127.0.0.1:8080/mcp --env prod

The same as a container:

docker run --rm -p 127.0.0.1:9000:9000 -e AIRLOCK_TRUST_PRINCIPAL_HEADER=1 \

-v $PWD/policy.yaml:/data/policy.yaml \ --add-host=host.docker.internal:host-gateway \ ghcr.io/shalimov04/mcp-airlock:0.4 --policy policy.yaml --upstream http://host.docker.internal:8080/mcp --env prod

AIRLOCK_TRUST_PRINCIPAL_HEADER=1 takes the caller from an X-Airlock-Principal: alice header, which is fine on a laptop; anywhere shared use a JWT instead (see Environment variables). With no identity set, every call is 401.

--add-host gives Docker Engine on Linux the host.docker.internal name that Docker Desktop provides by itself. The upstream has to listen on an address the container can reach, not only on 127.0.0.1, and a host firewall may need to allow traffic from docker0; --network host with --upstream http://127.0.0.1:8080/mcp sidesteps both.

The image has a HEALTHCHECK that asks http://127.0.0.1:9000/healthz with python every 30 seconds (the image has no curl), ignoring any HTTP_PROXY. If you pass --port, or a --host bound to a specific non-loopback address, override it with --health-cmd or a compose healthcheck:. Its --start-interval needs Docker Engine 25+ (older ones ignore it). Kubernetes ignores the check: point a liveness probe at /healthz and a readiness probe at /readyz, as the Helm chart does.

From a checkout:

uv sync --all-extras

uv run pytest uv run python demo.py

The demo starts a fake upstream with a handful of tools on port 9001 and the proxy on 9000, walks through the interesting cases (refused tool, forced dry run, confirmation, replay, blast radius, output cap, injection marking) and leaves the audit log and spans in examples/.

The short version, recorded against that same fake upstream. An agent tries to delete a production service, gets a dry run and a confirmation prompt instead, the confirmation works exactly once, and a poisoned read result comes back flagged:

docs/make_demo_gif.py re-records it (uv run --with pillow python docs/make_demo_gif.py).

docs/clients.md shows how to point Claude Code and Cursor at the proxy, what the agent sees when a call is refused or held for confirmation, and which clients have been tested with the confirmation prompt.

Against a real server:

uv run mcp-airlock --policy policy.example.yaml --env prod \

--upstream http://127.0.0.1:9001/mcp --audit audit.jsonl

There are ready-made policies for the GitHub, Grafana, Kubernetes and Postgres MCP servers in examples/policies/. They were written against the servers' source at a pinned commit, so check them against your actual server before trusting them:

uv run airlock-policy lint examples/policies/github.yaml

uv run airlock-policy diff examples/policies/github.yaml --upstream http://127.0.0.1:8080/mcp --env prod

lint needs no network. It reports a tool without tiers (no_tiers, an error), a write tool without a description (no_description), a count_arg that relies on the global blast radius (blast_radius_default), a where rule for an environment no tier mentions (where_env_unknown) and an environment no tool covers (env_unused); --env adds environments that must be covered. A policy without environment lints with the first --env (or AIRLOCK_ENV) as its environment, the way the proxy would run it; without either it is an error. diff and pin take --env, then AIRLOCK_ENV, then the policy's own environment. A policy that cannot be read or does not validate is ERROR invalid in all three commands, and an upstream that does not answer tools/list like an MCP server is ERROR upstream. diff asks the server itself (not the proxy, which hides unlisted tools) for tools/list and tells you which allowlisted tools the server no longer has (missing_upstream, an error), which L1/L2 tools have no dry_run argument (no_dry_run), which where rules name an argument that is not in the schema (where_unknown_arg) and which server tools the policy does not mention (not_allowlisted). With --pins it also checks the pins. Both exit 1 when any finding is an error.

In Kubernetes

There is a small Helm chart in charts/mcp-airlock/ (Deployment, Service, a ConfigMap for the policy, a Secret for the keys, probes on /healthz and /readyz, a hardened security context). There is no chart repository, so install it from a checkout:

helm install airlock charts/mcp-airlock \

--set upstream=http://my-mcp-server:8080/mcp --set environment=prod \ --set-file policy=policy.yaml

The values are documented in charts/mcp-airlock/values.yaml. The points that matter:

  • Identity. By default the chart creates a Secret with a random AIRLOCK_JWT_SECRET and keeps it across upgrades. Read it with kubectl get secret airlock-mcp-airlock -o jsonpath='{.data.AIRLOCK_JWT_SECRET}' | base64 -d and sign HS256 tokens with sub and exp. Anyone who can read Secrets in the namespace (or the Helm release Secrets) can mint any principal. For JWKS set env.AIRLOCK_JWKS_URL and env.AIRLOCK_JWT_AUDIENCE, and set generateJwtSecret=false so no unused secret is generated. For a trusted gateway header set generateJwtSecret=false and env.AIRLOCK_TRUST_PRINCIPAL_HEADER=1, and make sure only the gateway can reach the Service: the chart ships no NetworkPolicy.
  • Credentials go in `existingSecret`, never in `env`. That covers AIRLOCK_UPSTREAM_AUTH, `AIRLOCK_APPROV

Only the beginning is shown; read the rest in the repo