@restforge-dev/mcp-server
OfficialProvides tools for setting up, validating, and interacting with MySQL databases as the backend for RESTForge projects, including schema introspection and endpoint generation from database tables.
Generates PM2 ecosystem configuration files and start/stop scripts for managing the RESTForge server process, and checks server status under PM2 mode.
Provides tools for setting up, validating, and interacting with PostgreSQL databases as the backend for RESTForge projects, including schema introspection and endpoint generation from database tables.
Validates connectivity to a Redis instance during the RESTForge project setup phase as part of the configuration validation.
Provides tools for setting up, validating, and interacting with SQLite databases as the backend for RESTForge projects, including schema introspection and endpoint generation from database tables.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@restforge-dev/mcp-serverGenerate a CRUD endpoint for the customer table"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@restforge-dev/mcp-server
MCP (Model Context Protocol) server for the RESTForge framework. Exposes RESTForge capabilities to AI Agents (Claude Desktop, Cursor, Claude CLI, and other MCP clients) so agents can operate RESTForge through natural language without manually invoking CLI commands.
Requirements
Node.js >= 18
npm >= 9
For full setup workflow: PostgreSQL / MySQL / Oracle / SQLite, RESTForge license key
Installation
npm install -g @restforge-dev/mcp-serverAfter installation, the restforge-mcp command is available in PATH.
Quick Start
1. Verify Install
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | restforge-mcpOutput should list 29 tools across the health_*, setup_*, codegen_*, and runtime_* domains.
2. Register with MCP Client
Claude CLI (user scope, applies to all projects):
claude mcp add --transport stdio --scope user restforge -- restforge-mcpCursor (.cursor/mcp.json in project root):
{
"mcpServers": {
"restforge": {
"command": "restforge-mcp"
}
}
}Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"restforge": {
"command": "restforge-mcp"
}
}
}3. Use via Natural Language
In your AI client chat, type prompts like:
Setup a new RESTForge project at
d:/projects/api-testwith PostgreSQL on localhost:5432, licenseXXXX-XXXX-XXXX-XXXX
Generate a CRUD endpoint for the
customertable
Run my RESTForge server (the agent generates a launcher script for the user to execute)
The agent orchestrates the appropriate tools to fulfill the request end-to-end.
Available Tools
29 tools organized by domain. AI agents call these via the MCP protocol; end users do not invoke them directly.
Health Domain (1 tool)
Tool | Description |
| Smoke test MCP transport. Returns |
Setup Domain (9 tools)
Tool | Description |
| Create a new project folder for RESTForge |
| Install |
| Generate skeleton config and sample payloads via |
| Write |
| Read current values from |
| Update individual fields in |
| Validate license and connections to database, redis, and kafka |
| Get JSON schema of all 63 parameters available in |
| Get raw |
Codegen Domain (13 tools)
Tool | Description |
| List all tables in the project's database (live introspection) |
| Describe columns, primary key, and foreign keys of a specific table |
| Generate payload JSON from a database table |
| Validate payload JSON structure and constraints |
| Validate dashboard payload structure |
| Diff payload JSON against the database schema |
| Sync payload JSON with the database schema |
| Scaffold an endpoint module from a payload spec |
| Scaffold a dashboard module from a payload spec |
| Validate a SELECT or WITH (CTE) SQL statement via EXPLAIN against the live database |
| Get the field validation catalog (for grounding payload constraints) |
| Get the query declarative catalog (for grounding query JSON) |
| Get the dashboard widget catalog (for grounding dashboard config) |
Runtime Domain (6 tools)
Tool | Description |
| Scan |
| Scan |
| Validate config + check PID file + check port availability before launch |
| Check if launcher files ( |
| Generate |
| Detect if the server is running (host or PM2 mode) with optional HTTP health probe |
Runtime principle: AI agents never start, stop, or restart the server directly. The runtime tools only generate launcher scripts that the user executes themselves, so the running server lives independently of the AI session.
Compatibility
This MCP server works with any MCP client that supports the stdio transport, including but not limited to:
Claude Desktop
Claude CLI (Claude Code)
Cursor
Windsurf
Cline (VS Code extension)
Continue (VS Code/JetBrains extension)
Zed
The model used (Claude, GPT, Gemini, etc.) depends on the client configuration. Tool selection accuracy is best with frontier models that have mature tool-calling support.
Repository
License
MIT — see LICENSE.md.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/restforge/restforge-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server