About agent-gate
Local mandate gate and proof trail for AI agents that take consequential actions.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y forge-agent-gateFORGE_API_KEYSecretForge decision-API key (starts with fi_). Set this or FORGE_BEARER_TOKEN.FORGE_BEARER_TOKENSecretAlternative to FORGE_API_KEY: a Forge bearer token for the decision API.FORGE_API_BASE_URLBase URL of the Forge decision API. Defaults to the hosted Forge cloud.FORGE_TENANT_IDTenant id stamped into every proof-trail record.FORGE_RECORD_MODErequired = fail-closed (block if Forge cannot record); best_effort = execute anyway.AGENT_GATE_MANDATE_PATHAbsolute path to the signed mandate (policy) JSON. Create it with `forge-agent-gate init`.AGENT_GATE_KILL_FILEIf this file exists, every gated write is hard-blocked (master kill switch).KALSHI_API_KEY_IDSecretKalshi API key id. Only for the live Kalshi venue adapter; stays on your machine.KALSHI_PRIVATE_KEY_PATHSecretPath to your Kalshi RSA private key. Only for the Kalshi venue adapter.KALSHI_ENVKalshi environment: demo or prod. Only for the Kalshi venue adapter.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.