MCP.Market

Forge MCP server

by frmoded·io.github.frmoded/forge-mcp·v0.2.0

MCP server + tools for the Forge E-- generative-music authoring loop (compile / run / commit).

B83/100grade B
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

0 stars31 downloads/wk

Reviews

Write one

Nobody has reviewed Forge MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Forge MCP tools (14, 5 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • _forge_commit_recipe
  • _forge_compile_recipe
  • _forge_create_directorywrite action
  • _forge_create_notewrite action
  • _forge_delete_notewrite action
  • _forge_get_run_resultwrite action
  • _forge_list_vaults
  • _forge_read_note
  • _forge_read_note_catalog
  • _forge_read_notes_in_vault
  • _forge_register_vault
  • _forge_rename_note
  • _forge_run_recipewrite action
  • _forge_unregister_vault

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan27 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Forge MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Tools
14
the typical server has 7
Tools that change things
36%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
31
more than 19% of 12,191 servers with a package

What its tools let an agent do: 9 read · 5 change

Install Forge MCP in Claude Code, Cursor or VS Code

claude mcp add forge-mcp -- uvx forge-recipe-mcp
Add to Cursor

What the publisher says

From the Forge MCP repository's README, as published. We do not edit it. Read it on GitHub

forge-mcp

Author, compile, run, and commit generative-music E-- Recipes directly from any MCP-capable agent (Claude Desktop, Cursor, …). forge-mcp exposes the Forge E-- library note catalog + vault as an MCP server and closes the authoring loop end-to-end: the agent picks a chip from the catalog, drafts a Recipe, verifies it parses, runs it in a sandbox, previews the artifact, and commits the finished Recipe to a vault note. All 6 tools ship today.

[library note catalog] → [compile] → [run] → [commit] → [vault note with recipe_version bump]

Install into Claude Code

Fastest path — Claude Code spawns forge-mcp as a stdio subprocess. Full walkthrough at docs/claude-code-install.md.

# 1. Install from PyPI (https://pypi.org/project/forge-recipe-mcp/)
pip install forge-recipe-mcp

# 2. Fetch your Bearer once and export
export FORGE_MCP_BEARER=$(jq -r '.transpileServiceToken' \
  ~/forge-vaults/bluh/.obsidian/plugins/forge-client-obsidian/data.json)

# 3. Register with Claude Code
claude mcp add forge-mcp \
  -e FORGE_MCP_BEARER=$FORGE_MCP_BEARER \
  -e FORGE_TRANSPILE_URL=https://forge.thecodingarena.com \
  -e FORGE_VAULT_PATH=$HOME/forge-vaults/bluh \
  -e FORGE_MCP_TRANSPORT=stdio \
  -- forge-mcp

# 4. Start Claude Code and ask "list the notes in my forge music library."

Install (other clients)

Full walkthrough (Claude Desktop config, forge-transpile Bearer acquisition, verification smoke, troubleshooting): docs/install.md.

Quick paths:

# From source (pip + editable install for development)
pip install -e ".[dev]"
python -m forge_mcp.server

# Docker
docker build -t forge-mcp:latest .
docker run --rm -p 8765:8765 \
    -e FORGE_TRANSPILE_URL=https://forge.thecodingarena.com \
    -e FORGE_VAULT_PATH=/path/to/your/vault \
    forge-mcp:latest

Environment:

  • FORGETRANSPILEURL — base URL of the forge-transpile service. Default: http://localhost:8000.
  • FORGEVAULTPATH — local vault directory for forgereadnotesinvault + forgecommitrecipe. Default: ~/forge-vaults/bluh.
  • FORGEMCPHOST — host to bind. Default: 0.0.0.0.
  • FORGEMCPPORT — port to bind. Default: 8765.
  • FORGEMCPBEARER — dev fallback only. Per-request Bearer extraction is the primary path (CW-MCP-1-B); this env var only fires when the incoming request has no Authorization header. Do NOT set in production.

Claude Desktop config

Add to ~/Library/Application Support/Claude/claudedesktopconfig.json:

{
  "mcpServers": {
    "forge-mcp": {
      "url": "http://localhost:8765/mcp",
      "headers": {
        "Authorization": "Bearer <your-forge-transpile-token>"
      }
    }
  }
}

Get your Bearer:

jq -r '.transpileServiceToken' \
    ~/forge-vaults/bluh/.obsidian/plugins/forge-client-obsidian/data.json

Tools

Read (no side effects):

  • forgereadnote_catalog({domain?}) — list Forge library notes; every entry carries the E-- signature the agent needs to Call it.
  • forgereadnotesinvault({filter?}) — list vault notes with a hasrecipe + recipeversion summary. Backed by a local filesystem walk (CW-MCP-2-E).

Author (deterministic — no LLM, no vault write):

  • forgecompilerecipe({source}) — Recipe → Python. Returns compiled source + unresolved slot count, OR a structured parse error with line/column (per drain CW-recipe-parser-line-info).
  • forgerunrecipe({source, domains?}) — compile + execute in a resource-limited server sandbox. Returns a short preview + a run_id; artifacts (MusicXML / MIDI / PNGs) accessible via the forge-artifact:// resource.
  • forgegetrunresult({runid}) — fetch full stdout/stderr + artifact manifest of a previous run. 7-day TTL, per-Bearer isolation.

Commit:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Forge MCP: common questions

Is Forge MCP server safe?
Mostly: it is graded B (83/100). Read the Forge MCP safety report
How do I install Forge MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Forge MCP need an API key?
Yes. The registry entry asks for FORGE_MCP_BEARER.
Is Forge MCP maintained?
The last commit was 40 days ago (2026-09-24). The latest release is v0.2.0.
How does Forge MCP compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); tools 14 (the typical server has 7); tools that change things 36% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.