InsForge

io.github.InsForgePublished by GitHub account InsForgev1.2.6Updated Oct 24, 2026

MCP server for InsForge BaaS — database, storage, edge functions, and deployments

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

InsForge MCP server that lets a coding assistant add and manage backend features — database, storage, edge functions, auth and deployments — in an InsForge BaaS

What you can do
Manage InsForge backend projects: databases, file storage, serverless edge functions and deployments, as described in the registry entry and README. Add backend capabilities such as auth, databases, file storage, serverless functions and LLMs to apps from a coding agent. Connect either to the hosted remote endpoint or run the npm package locally over stdio. The README does not list individual tools; it points to the main InsForge repository for available tools and usage examples.
When to use it
Use it when you are building an app on InsForge and want a coding assistant to create or change backend pieces — tables, storage buckets, functions, auth or deployments — without leaving the chat. Not useful if you do not already have an InsForge project or instance.
Requirements
An InsForge project or self-hosted instance. The API_BASE_URL environment variable (the InsForge backend URL, defaulting to localhost:7130 per the README) and the API_KEY secret environment variable. OAuth authentication is declared. The local option needs Node.js to run the npm package @insforge/mcp; a remote endpoint is also offered.
Before you install
The server holds an InsForge project API key (API_KEY) that grants access to your backend; keep it out of shared configs and logs. Its purpose is to create and change backend resources such as databases, storage, functions and deployments, so assistant actions can modify or delete live project data. The README's installer examples pass the key on the command line.

Installation

In SourceWeft

  1. Open InsForge in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.InsForge%2Finsforge-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "insforge": {
      "type": "http",
      "url": "https://mcp.insforge.dev/mcp"
    }
  }
}

README

Insforge MCP Server

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.

[Insforge Server MCP server]

📖 Documentation

Please visit the main Insforge repository for:

  • Installation and setup instructions
  • Configuration guide
  • Available tools and usage examples
  • API documentation
  • Contributing guidelines

🚀 Quick Start

Automated Installation (Recommended)

Use the InsForge installer to automatically configure MCP for your client:

bash
# Claude Codenpx @insforge/install --client claude-code --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Cursornpx @insforge/install --client cursor --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Windsurfnpx @insforge/install --client windsurf --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Clinenpx @insforge/install --client cline --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Roo Codenpx @insforge/install --client roocode --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130# Traenpx @insforge/install --client trae --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130
# Install dev version for testingnpx @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 key
  • http://localhost:7130 with your InsForge instance URL (optional, defaults to localhost:7130)

Manual Installation

If you prefer to manually configure your MCP client, add this to your MCP settings file:

json
{  "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.

🛠️ Development

If you are contributing to this project or running it locally:

bash
# Install dependenciesnpm install
# Run unit testsnpm run test
# Run linter (static analysis)npm run lint
# Auto-format codenpm run format
# Build the packagenpm run build

📄 License

Apache License 2.0 - see the LICENSE file for details.

Part of the Insforge project.

Source: README.md at commit 094a1f3

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.6LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts