Local daemon giving AI agents named locks, shared state, events, and a task queue over MCP.
Airlock MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Local daemon giving AI agents named locks, shared state, events, and a task queue over MCP.
Named resource locks, atomic shared state, presence, events, and a task queue for AI agents — exposed over a local HTTP MCP server that's always running, so any session, terminal, or CI job can coordinate with any other. Cross-platform Go daemon, SQLite-backed, with real blocking waits — no more poll loops.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Once Airlock is connected, these are the calls the assistant has available:
Verify — The Verify tool exposed by this serverLocks — wait_seconds is the coordination-by-default knob: pass it (up to 50) and lock_resource blocks server-side until the lock frees, instead ofPresence — The Presence tool exposed by this serverEvents — Events are generation-counted, not latched: pass back the generation you last saw and a signal that fired between calls is never missedTasks — A claim is a lease: if the claimant doesn't complete_task/fail_task within lease_seconds, the task auto-requeues for another consumer — no workYou will need one environment variable: AIRLOCK_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Airlock's toolset — Verify, Locks, Presence and 2 more — is a fair guide to whether it matches your workflow. It is maintained by adamorad; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Verify | The Verify tool exposed by this server. |
| Locks | wait_seconds is the coordination-by-default knob: pass it (up to **50**) and lock_resource **blocks** server-side until the lock frees, instead of returning locked:false immediately. The cap stays under Claude Code's 60s |
| Presence | The Presence tool exposed by this server. |
| Events | Events are **generation-counted**, not latched: pass back the generation you last saw and a signal that fired between calls is never missed. |
| Tasks | A claim is a **lease**: if the claimant doesn't complete_task/fail_task within lease_seconds, the task auto-requeues for another consumer — no work is lost to a crashed worker. The lease_token from claim_next_task is the |
| Variable | Description | Required |
|---|---|---|
| AIRLOCK_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.