Install
$ agentstack add mcp-skunpro-react-forge ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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 () |
License
MIT
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: skunpro
- Source: skunpro/react-forge
- License: MIT
- Homepage: https://github.com/skunpro/react-forge/releases/latest
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.