Skip to content

codex_mcp.md

Latest commit

 

History

History
79 lines (54 loc) · 2.68 KB

codex_mcp.md

File metadata and controls

79 lines (54 loc) · 2.68 KB
Raw
title Movi MCP For Codex
description Wire Movi MCP v1 into Codex when you want review-first file organization without giving an agent a direct execute shortcut.

Movi MCP For Codex

Movi already has a real Codex-friendly story today:

  • Category: review-first local AI file organizer
  • Hotness hook: stdio-first MCP for Codex
  • Outcome: let Codex inspect jobs, review queues, manifests, and dry-run previews without giving it a secret file-move shortcut

In plain language: Codex can help you understand and edit the plan, but it still cannot skip the same review-first safety gate a human uses.

Why Codex Is A Real Fit

Codex is a good fit for Movi right now because the repo already ships these real pieces:

  • Movi MCP v1 as a stdio-first local integration surface
  • review-safe tools for analyze.create, review_queue.get, manifest.get, manifest.patch_*, review_rule.*, and apply.preview
  • read-only docs and workflow resources that explain the current safety boundary

That means Codex is not being name-dropped as a fantasy partner. The connection exists because the MCP surface already exists.

What Codex Can Safely Do Today

Use Codex with Movi when you want it to:

  • inspect current runtime settings before creating work
  • launch a local analyze draft for a batch
  • read the review queue and copilot summary
  • patch manifest rows through the overlay only
  • preview review rules and apply them to the overlay
  • queue a dry-run apply preview

Think of it like asking a careful assistant to prepare the checklist, not giving that assistant the keys to drive the moving truck.

What Codex Cannot Do Today

Movi does not currently let Codex:

  • call a hidden apply.execute
  • move or rename files without review
  • bypass overlay -> resolved snapshot -> dry-run -> execute
  • act like a hosted remote automation platform

Minimal Wiring

Codex already ships a first-party MCP command surface, so the shortest current route is:

codex mcp add movi -- bash /absolute/path/to/movi-organizer/tooling/runtime/run_mcp_stdio.sh

If you want to inspect the saved MCP configuration or remove it later:

codex mcp list
codex mcp remove movi

The portable core is still just a stdio command. If you are wiring Movi into a Codex client surface that wants JSON instead of the CLI helper, use:

{
  "name": "movi",
  "command": "bash",
  "args": ["/absolute/path/to/movi-organizer/tooling/runtime/run_mcp_stdio.sh"]
}

If you install the Python package entrypoint, movi-mcp can be used instead of the shell wrapper.

What To Read Next