-
Notifications
You must be signed in to change notification settings - Fork 0
Using Forge from Claude and Codex
Forge is a Model Context Protocol (MCP) server. Register it once, and Claude Code or Codex can call its tools live and keep working with the results — no copy-pasting from a terminal.
# Claude Code
claude mcp add forge -- npx -y @unleashwp/forge@latest mcpFor Codex, add an MCP server to your config with:
command = "npx"
args = ["-y", "@unleashwp/forge@latest", "mcp"]
The server is named forge and runs over stdio. npx @latest means it always fetches the current published version.
Prefer no npm at all? In Claude Desktop, install the
.mcpbbundle instead (see Installation). It bundles the code and prompts for credentials on install.
"Give me the WordPress 7.1 release changelog for July 15–22, as a post."
The agent picks the right tool, fills in the dates and milestone, and drafts the post grounded in the real PRs and tickets.
| Tool | What it returns |
|---|---|
get_changelog |
The release-post changelog for a date window (markdown / post / json). |
show_changelog |
Opens an interactive changelog panel inside the conversation. |
list_milestones |
Release milestones, from the Gutenberg wp/x.y branches. |
list_branches |
Branches for a repo (gutenberg or core). |
open_forge |
Opens the full Forge app as a window in the conversation. |
Forge also ships skills — reusable AI instructions served as MCP prompts:
-
write_release_post— teaches the agent to draft a release post from the changelog data while respecting the grounding rule (every highlight traces to a real PR or ticket).
List them from the CLI with ai-forge skills, or print one with ai-forge skills write_release_post.
open_forge and show_changelog render the actual Forge React UI as a sandboxed window inside Claude Desktop / Codex — the same interface you get in the browser, but with no browser involved. The window talks back to Forge over the MCP connection.
Ask for "deep" or "full ticket text" and the agent adds --deep. That enriches each change with its Trac ticket description — if the wordpress.org cookie connector is set. Without it, Forge degrades gracefully to summaries and says so. See Connectors.
Whatever the surface, the rule holds: every highlight must trace to a real PR or ticket the tool returned. Forge never invents features and never estimates counts — it hands the agent real numbers and links, and the agent should keep the prose tied to them.