MCP servers · chaarangan

Stepgate: MCP server that runs gated YAML stepfiles one step at a time

An MCP server that runs YAML stepfiles, moving an agent to the next step only when mechanical gates pass.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

Stepgate is an MCP server that runs stepfiles, YAML files that declare inputs, the remote APIs and MCP servers a run may call, and an ordered list of steps. Each step names the output it must produce and the gates that check it, using JSON Schema, JSONLogic or HTTP verifiers. The agent sees one step at a time, the server makes the API calls and attaches credentials itself, and the run advances only when a step's gates pass. Mechanical steps build output from templates without the model, and an approve gate asks a person to confirm output before a later write step. Each run is recorded in a hash-chained ledger that `stepgate --verify` can check.

It suits procedures where a skipped step or an invented value has a cost, such as a cited research report, CVE triage, or a ticket written to Jira. It can also turn a markdown skill or runbook into a stepfile, so that its steps are enforced rather than left to the agent's judgement.

The server is added to an MCP client's configuration, naming stepfiles from the catalog or absolute paths to your own files. Nothing is installed on the client side beyond that entry, and no model key is needed, because the client's own model does the reasoning. The example market-research stepfile needs a Tavily API key.

Limitations and requirements

Requires an MCP client and Node.js 22.18 or later. Stepfiles can call only the remote APIs and MCP servers they declare, and requests to undeclared hosts are refused. Each declared service needs its own credentials, for example a Tavily API key for the market-research example.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    Stepgate

    Agents can't skip steps: runs gated stepfiles on the client's own model.

    v0.2.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026