About React Forge
React Forge is an MCP server in the AI category: zed MCP server extension for ecosystem-aware React component scaffolding (tests/stories/barrels) with impact estimation.
Install
git clone https://github.com/skunpro/react-forgeThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Tools (5)
react_forge_ecosystem_planplans scaffolding, optionally applies it (`dryRun: false`), returns impact by default
Parameters not published.
react_forge_file_importsshows relative imports in a file and their resolved targets
Parameters not published.
react_forge_find_dependentsreturns direct and transitive dependents for a file within a project root
Parameters not published.
react_forge_import_graph_statsreturns import graph stats (file count, edge count, ignored directories)
Parameters not published.
react_forge_list_source_fileslists JS/TS source files under a project root (with ignores and limits)
Parameters not published.
Ask AI
Ask AI about React Forge
Powered by Claude · Grounded in docs
Security checks
- ✓README presentThe repository ships documentation.
5 checks have not been run yet.
README
React Forge (MCP Server Extension for Zed)
React Forge is a Model Context Protocol (MCP) server packaged as a Zed extension. It helps you scaffold and maintain component ecosystems in React projects with a plan-first workflow.
The recommended install method is via Zed’s Extensions UI. The source code is public for transparency and contributions, but end users should install through Zed rather than cloning the repository.
Core Features
- Plan scaffolding for a component (tests, stories, barrel exports)
- Apply the plan and return per-action statuses
- Estimate impact using a local import graph (direct and transitive dependents)
Installation
Zed Extensions
Install the extension from Zed (Extensions view). After installation, go to Agent Panel → Settings → Context Servers and ensure react-forge shows “Server is active”.
Local Development
Use Zed: Extensions → Install Dev Extension, then select this repository folder.
Using the Tools
In the Agent chat, ask the model to call a tool by name and provide arguments. Examples below are shown as structured input; paste them into chat and adjust paths.
Plan only (dry run):
Call react_forge_ecosystem_plan with:
projectRoot: "E:\\path\\to\\my-app"
componentFile: "src/components/Button.tsx"
exportName: "Button"
barrelFile: "src/components/index.ts"
include: { test: true, story: true, barrel: true }
computeImpact: true
dryRun: true
Apply changes:
Call react_forge_ecosystem_plan with the same arguments, but set dryRun: false. Return the applied array.
Available Tools
react_forge_ecosystem_plan: plans scaffolding, optionally applies it (dryRun: false), returns impact by defaultreact_forge_find_dependents: returns direct and transitive dependents for a file within a project rootreact_forge_list_source_files: lists JS/TS source files under a project root (with ignores and limits)react_forge_file_imports: shows relative imports in a file and their resolved targetsreact_forge_import_graph_stats: returns import graph stats (file count, edge count, ignored directories)
Configuration (Optional)
React Forge does not require configuration. Zed exposes optional settings:
logLevel:"off"or"debug"ignoredDirNames: extra directory names to ignore during scansmaxResults: default cap for dependent graph resultsimpactMaxResults: cap used for impact computation
Development
cargo fmt --check
cargo check
cargo clippy -- -D warnings
Contributing
Contributions are welcome. Please open an issue describing the problem or feature, then submit a pull request.
Contributors
| Contributor | Contact |
|---|---|
| skun (hello@skun.pro) |
License
MIT
README copy captured when this server was indexed; it may lag the repository. The original is authoritative.