mcp-airlock
Rank #4,947io.github.Shalimov04/mcp-airlock
Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit
What you can do with mcp-airlock
mcp-airlock is a Model Context Protocol (MCP) server published by Shalimov04. It ranks #4,947 of 163,719 active servers on MCP Toplist, and its repository has 15 GitHub stars. mcp-airlock is listed across 2 registries — Official MCP and Glama, with 2 tracked versions. It was first listed on Sep 14, 2026 and most recently updated on Sep 16, 2026.
Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.
What mcp-airlock can and cannot do
Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.
What you need before using mcp-airlock
The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.
Declared by Glama, last synced Oct 30, 2026. Not independently verified by MCP Toplist.
- AIRLOCK_JWT_SECRET · optional
- AIRLOCK_SECRET · optional
Connect mcp-airlock and confirm it works
claude mcp add mcp-airlock -e "AIRLOCK_JWT_SECRET=<your AIRLOCK_JWT_SECRET>" -e "AIRLOCK_SECRET=<your AIRLOCK_SECRET>" -- uvx mcp-airlock --policy "<policy.yaml>" --upstream "<http://127.0.0.1:8080/mcp>" --env prodReplace each placeholder with your own value before saving.
[mcp_servers.mcp-airlock]
command = "uvx"
args = ["mcp-airlock", "--policy", "<policy.yaml>", "--upstream", "<http://127.0.0.1:8080/mcp>", "--env", "prod"]
[mcp_servers.mcp-airlock.env]
AIRLOCK_JWT_SECRET = "<your AIRLOCK_JWT_SECRET>"
AIRLOCK_SECRET = "<your AIRLOCK_SECRET>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"mcp-airlock": {
"command": "uvx",
"args": [
"mcp-airlock",
"--policy",
"<policy.yaml>",
"--upstream",
"<http://127.0.0.1:8080/mcp>",
"--env",
"prod"
],
"env": {
"AIRLOCK_JWT_SECRET": "<your AIRLOCK_JWT_SECRET>",
"AIRLOCK_SECRET": "<your AIRLOCK_SECRET>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"mcp-airlock": {
"command": "uvx",
"args": [
"mcp-airlock",
"--policy",
"<policy.yaml>",
"--upstream",
"<http://127.0.0.1:8080/mcp>",
"--env",
"prod"
],
"env": {
"AIRLOCK_JWT_SECRET": "<your AIRLOCK_JWT_SECRET>",
"AIRLOCK_SECRET": "<your AIRLOCK_SECRET>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"servers": {
"mcp-airlock": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-airlock",
"--policy",
"<policy.yaml>",
"--upstream",
"<http://127.0.0.1:8080/mcp>",
"--env",
"prod"
],
"env": {
"AIRLOCK_JWT_SECRET": "<your AIRLOCK_JWT_SECRET>",
"AIRLOCK_SECRET": "<your AIRLOCK_SECRET>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"mcp-airlock": {
"command": "uvx",
"args": [
"mcp-airlock",
"--policy",
"<policy.yaml>",
"--upstream",
"<http://127.0.0.1:8080/mcp>",
"--env",
"prod"
],
"env": {
"AIRLOCK_JWT_SECRET": "<your AIRLOCK_JWT_SECRET>",
"AIRLOCK_SECRET": "<your AIRLOCK_SECRET>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"mcp-airlock": {
"command": "uvx",
"args": [
"mcp-airlock",
"--policy",
"<policy.yaml>",
"--upstream",
"<http://127.0.0.1:8080/mcp>",
"--env",
"prod"
],
"env": {
"AIRLOCK_JWT_SECRET": "<your AIRLOCK_JWT_SECRET>",
"AIRLOCK_SECRET": "<your AIRLOCK_SECRET>"
}
}
}
}Replace each placeholder with your own value before saving.
After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.
What changed, and when this was checked
- First listed
- Sep 14, 2026
- Latest version published
- Sep 16, 2026
- Version history
- 2 versions tracked (below)
- Requirements evidence
- Declared by Glama, last synced Oct 30, 2026. Not independently verified by MCP Toplist.
- Profile checked
- Not yet — purpose, capabilities and requirements above come from registry data only
- Ranking data as of
- Oct 30, 2026
- Official MCP ↗listed since Sep 15, 2026 · still listed
- Glama ↗listed since Sep 15, 2026 · still listed
Do you maintain mcp-airlock? to correct or enrich this profile.
Available versions (2)
| Version | Published |
|---|---|
| 0.2.0 | Sep 16, 2026 |
| 0.1.0 | Sep 14, 2026 |
Ranks ahead of 158,772 of 163,719 servers on MCP Toplist.
Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.Shalimov04%2Fmcp-airlock)<a href="https://mcptoplist.com/server/io.github.Shalimov04%2Fmcp-airlock"><img src="https://mcptoplist.com/badge/io.github.Shalimov04%2Fmcp-airlock.svg" alt="MCP Toplist: Top 5% of 163,719" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Frequently asked questions
- Who maintains mcp-airlock?
- mcp-airlock is maintained by Shalimov04, which publishes 1 MCP server (2 total versions) tracked on MCP Toplist.
- Is mcp-airlock listed on the Official MCP Registry?
- Yes — mcp-airlock is listed on the Official MCP Registry, alongside Glama.
- How many versions does mcp-airlock have?
- MCP Toplist tracks 2 versions of mcp-airlock, most recently published on Sep 16, 2026.
- Where can I find the source code for mcp-airlock?
- The source code for mcp-airlock is hosted at github.com/Shalimov04/mcp-airlock.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.