Gatewerk runs on your own machine — the client starts it, so there is no endpoint to ping. 52 installs a week from npm. Last commit 16 Aug 2026.
The open-source review layer for AI agents. Work done for humans is decided by humans.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
: "${SSH_KEY:?CLOUD_SSH_KEY is unset. Add it to docker/.env.cloud, e.g. ~/.ssh/your_key}"
<script src="https://challenges.cloudflare.com/turnstile/v0/api.js" async defer></script>
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp -e 'GATEWERK_API_KEY=<GATEWERK_API_KEY>' -- npx -y @gatewerk/mcp{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@gatewerk/mcp"
],
"env": {
"GATEWERK_API_KEY": "<GATEWERK_API_KEY>"
}
}
}
}[mcp_servers.mcp]
command = "npx"
args = ["-y", "@gatewerk/mcp"]
env = { GATEWERK_API_KEY = "<GATEWERK_API_KEY>" }{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@gatewerk/mcp"
],
"env": {
"GATEWERK_API_KEY": "<GATEWERK_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gatewerk/mcp"
],
"env": {
"GATEWERK_API_KEY": "<GATEWERK_API_KEY>"
}
}
}
}Put your own value in place of
<GATEWERK_API_KEY> (Gatewerk API key (gwk_...). Generate one at your Gatewerk instance under Settings → API Keys).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
GATEWERK_URL (Base URL of your self-hosted Gatewerk instance (e.g. https://api.gatewerk.com). Defaults to http://localhost:3100), GATEWERK_REVIEWER (Reviewer email used as decision attribution. When set, decisions made through the MCP server are attributed to this reviewer instead of the API key identity).
Alternatives to Gatewerk
same job, measured the same wayThe open-source talent graph for humans and AI agents. Find developers.
The open-source governance layer for AI agents. Byte-identical run receipts, 40+ adapters, air-gap.
Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve.
Verified, sourced, real-time intelligence layer for AI agents.
Source-traced evidence research for AI agents. We organise the evidence; you decide.
Open guestbook for AI agents: read messages and leave a human-reviewed message.
A local intelligence layer for AI coding agents. Maps your repos, matches the open-source frontier.
The Open Context Layer for Data Agents
Gatewerk — questions
Answers built from our own checks of this server.