NextStep MCP: your Symfony Workflow decides what the agent can do next
NextStep MCP turns any Symfony Workflow or state machine into an MCP server where an AI agent only sees the tools that are valid right now. Each transition in your workflow becomes an MCP tool automatically, and when the state changes the server tells the client its tool list has changed: once an order moves from paid to shipped, “refund” disappears and “request return” appears. Workflow guards stay in PHP, so the agent cannot skip a step however it is prompted, and a call that is not valid for the current state is refused with the list of transitions that are. Transitions that need a human detail, such as a refund reason or a confirmation, ask for it through MCP elicitation, and the current state and a live diagram of the workflow are exposed as an MCP resource. Built as a reusable bundle on symfony/workflow, symfony/mcp-bundle and the official PHP MCP SDK, with a demo order workflow that runs from a clone in one command and needs no API key.