Generate MCP ServerLABSCO SUMMARY
A starting point, not a finished product.
The value is the three templates plus the two "how do I wire this up" answers, which is exactly the friction of a first MCP server. It has not been renamed off its placeholder package identifier, which tells you where it sits: a scaffold you run locally rather than something you install from a registry.
What it is
A small generator that produces new MCP servers for Smithery. Three templates are included — Basic, with one example tool; Web Search; and Database, wired for PostgreSQL — so the starting point matches what you are building rather than being an empty folder.
What you get
Three tools: one generates a new MCP server from the configuration you give it, one returns the integration config for Cursor IDE, and one returns the steps for deploying to Smithery.
Requirements
Node.js and npm. Clone the repository and run npm install; the server speaks stdio and starts with node src/index.js. The README's Cursor entry runs @your-username/mcp-forge through Smithery, a placeholder that was never published, so point your client at node and the full path to src/index.js in your clone instead.
Setup effort
Build from source — git clone https://github.com/chromewillow/mcp-forge
USE CASES
01
Starting a new MCP server without copying one by hand
Generate it from the template that matches what you're building.
02
Getting a fresh server into Cursor
Ask for the integration config rather than working out the JSON shape.
03
Publishing what you built
Get the Smithery deployment steps alongside the generated code.
3 tools
Listed in project docs. Your client may show a different list.
Get Cursor IntegrationDeploy to SmitheryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. The documentation gives only descriptive names (Generate MCP Server, Get Cursor Integration, Deploy to Smithery), not the identifiers your client will display.
Requires
node on PATH
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/chromewillow/mcp-forge
cd mcp-forge
npm installAdd it to your MCP client yourself: the README's only client configuration runs a Smithery package, @<YOUR_USERNAME>/mcp-forge, that was never published. The server speaks stdio and its start script is node src/index.js, so configure your client to launch node with the full path to src/index.js in your clone.
