Agent-gate MCP Server

Local mandate gate and proof trail for AI agents that take consequential actions.

Local serverstdio

What is the Agent-gate MCP Server?

Agent-gate is an MCP integration. Local mandate gate and proof trail for AI agents that take consequential actions.

Packages and local setup

The published npm package is forge-agent-gate, version 0.1.5. Its declared MCP transport is stdio.

The package declares FORGE_API_KEY: Forge decision-API key (starts with fi_). Set this or FORGE_BEARER_TOKEN.; FORGE_BEARER_TOKEN: Alternative to FORGE_API_KEY: a Forge bearer token for the decision API.; FORGE_API_BASE_URL: Base URL of the Forge decision API. Defaults to the hosted Forge cloud.; FORGE_TENANT_ID (required): Tenant id stamped into every proof-trail record.; FORGE_RECORD_MODE: required = fail-closed (block if Forge cannot record); best_effort = execute anyway.; AGENT_GATE_MANDATE_PATH: Absolute path to the signed mandate (policy) JSON. Create it with forge-agent-gate init.; AGENT_GATE_KILL_FILE: If this file exists, every gated write is hard-blocked (master kill switch).; KALSHI_API_KEY_ID: Kalshi API key id. Only for the live Kalshi venue adapter; stays on your machine.; KALSHI_PRIVATE_KEY_PATH: Path to your Kalshi RSA private key. Only for the Kalshi venue adapter.; KALSHI_ENV: Kalshi environment: demo or prod. Only for the Kalshi venue adapter..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project website. This profile uses version 0.1.5 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
FORGE_API_KEYForge decision-API key (starts with fi_). Set this or FORGE_BEARER_TOKEN.Optional
FORGE_BEARER_TOKENAlternative to FORGE_API_KEY: a Forge bearer token for the decision API.Optional
FORGE_API_BASE_URLBase URL of the Forge decision API. Defaults to the hosted Forge cloud.Optional
FORGE_TENANT_IDTenant id stamped into every proof-trail record.Yes
FORGE_RECORD_MODErequired = fail-closed (block if Forge cannot record); best_effort = execute anyway.Optional
AGENT_GATE_MANDATE_PATHAbsolute path to the signed mandate (policy) JSON. Create it with forge-agent-gate init.Optional
AGENT_GATE_KILL_FILEIf this file exists, every gated write is hard-blocked (master kill switch).Optional
KALSHI_API_KEY_IDKalshi API key id. Only for the live Kalshi venue adapter; stays on your machine.Optional
KALSHI_PRIVATE_KEY_PATHPath to your Kalshi RSA private key. Only for the Kalshi venue adapter.Optional
KALSHI_ENVKalshi environment: demo or prod. Only for the Kalshi venue adapter.Optional