MCP server for InsForge BaaS — database, storage, edge functions, and deployments
InsForge turns your coding agents into full-stack builders, letting them add backend features like auth, databases, file storage, serverless functions, and LLMs to your apps in seconds.
This repo is Model Context Protocol server for Insforge.
Please visit the main Insforge repository for:
Use the InsForge installer to automatically configure MCP for your client:
# Claude Code
npx @insforge/install --client claude-code --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Cursor
npx @insforge/install --client cursor --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Windsurf
npx @insforge/install --client windsurf --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Cline
npx @insforge/install --client cline --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Roo Code
npx @insforge/install --client roocode --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Trae
npx @insforge/install --client trae --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Install dev version for testing
npx @insforge/install --client cursor --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130 --dev
Replace:
your_api_key with your InsForge API keyhttp://localhost:7130 with your InsForge instance URL (optional, defaults to localhost:7130)If you prefer to manually configure your MCP client, add this to your MCP settings file:
{
"mcpServers": {
"insforge": {
"command": "npx",
"args": [
"-y",
"@insforge/mcp@latest"
],
"env": {
"API_KEY": "your_api_key",
"API_BASE_URL": "http://localhost:7130"
}
}
}
}
For detailed setup instructions, see the Insforge Documentation.
If you are contributing to this project or running it locally:
# Install dependencies
npm install
# Run unit tests
npm run test
# Run linter (static analysis)
npm run lint
# Auto-format code
npm run format
# Build the package
npm run build
Apache License 2.0 - see the LICENSE file for details.
Part of the Insforge project.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @insforge/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-insforge-insforge-mcp": {
"command": "npx",
"args": [
"-y",
"@insforge/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@insforge/mcpnpmInsForge works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.