The MCP gateway that pins every tool, holds risky calls for approval, and enforces egress policy.
Connect Runs on your machine
claude mcp add hangar -e MCP_CONFIG=<MCP_CONFIG> -- uvx mcp-hangar==2.36.6{
"mcpServers": {
"hangar": {
"command": "uvx",
"args": [
"mcp-hangar==2.36.6"
],
"env": {
"MCP_CONFIG": "<MCP_CONFIG>"
}
}
}
}{
"mcpServers": {
"hangar": {
"command": "uvx",
"args": [
"mcp-hangar==2.36.6"
],
"env": {
"MCP_CONFIG": "<MCP_CONFIG>"
}
}
}
}{
"servers": {
"hangar": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-hangar==2.36.6"
],
"env": {
"MCP_CONFIG": "<MCP_CONFIG>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
MCP_CONFIGOptional | Path to config.yaml declaring the upstream MCP servers and policy. Without it Hangar reads ./config.yaml, else ~/.config/mcp-hangar/config.yaml (written by `mcp-hangar init`), and refuses to start if neither exists. |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 12 Nov 2026 |
| Last updated | 12 Nov 2026 |
| Registry name | io.mcp-hangar/hangar |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.