For AI agents: the complete documentation index is available at https://mfeflow.github.io/mfeflow/llms.txt, the full documentation bundle is available at https://mfeflow.github.io/mfeflow/llms-full.txt, and this page is available as Markdown at https://mfeflow.github.io/mfeflow/guide/agents-and-mcp.md.

Use mfeflow from a coding agent

mfeflow mcp starts an MCP server on stdin and stdout. A coding agent that speaks MCP can then read your project, check it, and plan changes with mfeflow's own commands. It is part of the CLI, so there is nothing else to install.

Warning

Available from the release after 0.8.0. Until then npx -y mfeflow mcp does not have the command.

The tools run the same code as the CLI, in the same process, in --json mode. They do not start a shell or a child process, and the answers match what you get on the command line.

Install

Claude Code:

claude mcp add mfeflow -- npx -y mfeflow mcp

Codex:

codex mcp add mfeflow -- npx -y mfeflow mcp

Cursor, in .cursor/mcp.json:

{
  "mcpServers": {
    "mfeflow": { "command": "npx", "args": ["-y", "mfeflow", "mcp"] }
  }
}

VS Code, in .vscode/mcp.json:

{
  "servers": {
    "mfeflow": { "type": "stdio", "command": "npx", "args": ["-y", "mfeflow", "mcp"] }
  }
}

Tools

Every tool takes cwd, the absolute path of the project (a folder inside it works too). Every tool also takes response_format: concise is the default, detailed returns the full CLI document. Answers come back as structured data with a text copy, and the text is cut at 40,000 characters with a note when it is cut.

ToolDoesChanges anything
mfeflow_inspect_projectReads mfeflow.json: apps, features and versions, topology, repo kind, bundlerNo
mfeflow_search_featuresLists features from mfeflow and your registries, with optional search textNo
mfeflow_validateChecks mfeflow.json, every mfeflow.app.json and every registry entryNo
mfeflow_doctorRuns the doctor checks, never --fix. Optional against: a public https URL, or a file inside the projectNo
mfeflow_registry_statusWhat each environment serves, the version before it, and driftNo
mfeflow_explain_errorGives the title, fix and docs link for an MFEFLOW_Exxx code, or finds codes in a logNo
mfeflow_planPlans init, add_feature, add_remote or upgrade as a dry run. Returns plan_id, a summary and the diffNo, it only remembers the plan
mfeflow_plan_diffReads a plan's diff one page at a time, so you can see all of itNo
mfeflow_apply_planApplies a plan by id, after you confirmYes, writes files
mfeflow_registry_planPlans a promote or a rollback as a dry run. Only with --allow-registry-writesNo
mfeflow_registry_applyRuns that plan against the registry host. Only with --allow-registry-writesYes, changes what visitors get

Planned and applied changes do not install packages. Run pnpm install yourself afterwards.

How changes are kept safe

  • Plan, then apply. The agent cannot write by calling one tool. mfeflow_plan runs the command with --dry-run and shows the diff. Only mfeflow_apply_plan with the returned plan_id writes, and the agent should show you the diff first.
  • You can read the whole diff. mfeflow_plan returns the first page of a long diff and says how many pages there are (diff_pages). mfeflow_plan_diff returns the others. Lists of written files come with a count, and a cut never drops plan_id.
  • A plan expires after 10 minutes and can be applied once. It is held in the server's memory, so restarting the server drops every plan.
  • A changed file stops it. The plan records the SHA-256 of every file it touches, including files it would skip, and of mfeflow.json. It also records where symlinks lead and which files were absent. If any of them changed, or a file it meant to create now exists, the apply is refused. Make a new plan.
  • A registry feature is checked again. add_feature repeats the dry run when you apply, and refuses if the changes or their content differ from what was planned.
  • Registry plans pin versions. A rollback with no version is stored as a rollback to the version the dry run found. A promote or rollback records the version it moves and what the target serves. The apply repeats the dry run and refuses if either changed, for example because someone deployed in between.
  • A plan belongs to one folder. Applying it from a different cwd is refused.
  • Registry writes are off by default. mfeflow_registry_plan and mfeflow_registry_apply exist only when the server starts with --allow-registry-writes. Add the flag to the command in your client config if you want them.
  • Registry tools use only the configured host. They take no host argument. They read registry.host from mfeflow.json and say so if it is not set. mfeflow_doctor treats against like a shell address from a committed file: no credentials, no private or loopback hosts, and a file must be inside the project folder.
  • Tokens come from the environment. The server reads the same variables as the CLI (MFEFLOW_S3_ENDPOINT, AWS_ACCESS_KEY_ID and the rest). No tool takes a token or a password as an argument, and a host with credentials in it is rejected.
  • A plan id is not a login. Anyone who can talk to the server can apply a plan. The server runs as you, on your machine, over stdio.
  • The server never asks you. It has no prompt of its own, so the confirmation has to come from your client. Set it to ask before mfeflow_apply_plan, mfeflow_registry_apply and mfeflow_registry_plan (in Claude Code, leave them out of the allowed tools so each call asks).

The hints on each tool (readOnlyHint, destructiveHint) are set honestly, but they are hints for the client. The safety comes from the plan and apply steps above. A registry plan can only check the project files; it cannot check what is on the remote host, so the apply runs the CLI's own guards (create-only uploads, index compare-and-swap) against it.

Try it

Ask your agent: "Add a remote called reviews, then run doctor." You should see it call mfeflow_plan, show you the diff for reviews, wait for your yes, call mfeflow_apply_plan, then call mfeflow_doctor.

To see the raw protocol without an agent:

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"hand","version":"1"}}}' \
  '{"jsonrpc":"2.0","method":"notifications/initialized"}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' | npx mfeflow mcp

The second reply lists the tools. The server ends when its input closes.