Free, local check before an AI agent acts: your rules return ACT, BLOCK or ESCALATE.
Connect Runs on your machine
claude mcp add abe -e ABE_POLICY=<ABE_POLICY> -e ABE_RESOLVER=<ABE_RESOLVER> -e FLOW_API_KEY=<FLOW_API_KEY> -- uvx abe-ai==0.2.3
{
"mcpServers": {
"abe": {
"command": "uvx",
"args": [
"abe-ai==0.2.3"
],
"env": {
"ABE_POLICY": "<ABE_POLICY>",
"ABE_RESOLVER": "<ABE_RESOLVER>",
"FLOW_API_KEY": "<FLOW_API_KEY>"
}
}
}
}
{
"mcpServers": {
"abe": {
"command": "uvx",
"args": [
"abe-ai==0.2.3"
],
"env": {
"ABE_POLICY": "<ABE_POLICY>",
"ABE_RESOLVER": "<ABE_RESOLVER>",
"FLOW_API_KEY": "<FLOW_API_KEY>"
}
}
}
}
{
"servers": {
"abe": {
"type": "stdio",
"command": "uvx",
"args": [
"abe-ai==0.2.3"
],
"env": {
"ABE_POLICY": "<ABE_POLICY>",
"ABE_RESOLVER": "<ABE_RESOLVER>",
"FLOW_API_KEY": "<FLOW_API_KEY>"
}
}
}
}
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 |
|---|---|
ABE_POLICYRequired | Absolute path to your abe-policy.yaml (create one with: uvx abe-ai init) |
ABE_RESOLVEROptional | Set to flow to send escalations to Flow (needs FLOW_API_KEY). Default: none, nothing leaves your machine. |
FLOW_API_KEYOptional, secret | Flow Resolver key (fjp_live_...), only with ABE_RESOLVER=flow. https://fjp.flowinfo.co/credits |
Details
| Package | [email protected] (PYPI, stdio) |
| First published | 13 Oct 2026 |
| Last updated | 13 Oct 2026 |
| Registry name | io.github.flowinfosystems-index/abe |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
