Log inSubmit server
Insforge MCP logo

Insforge MCP

by InsForge

Connects coding agents to InsForge auth, PostgreSQL, storage, functions, and LLM-backed application infrastructure.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Insforge MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "insforge-insforge-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@insforge/install"
      ],
      "env": {
        "API_KEY": "YOUR_VALUE_HERE",
        "API_BASE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

InsForge/insforge-mcp MCP server connects AI coding agents to the InsForge backend platform. It exposes backend capabilities for authentication, PostgreSQL databases, file storage, serverless functions, and LLM features through MCP. The package runs through npx and uses an API key plus an InsForge instance URL to reach the target backend. Reach for it when an agent needs to create or manage full-stack application infrastructure through InsForge.

Use cases

  • Build full-stack applications with an AI coding agent
  • Manage InsForge authentication from an agent workflow
  • Work with PostgreSQL-backed application data
  • Add file storage and serverless functions
  • Configure InsForge for supported MCP clients

Key features

  • InsForge authentication access
  • PostgreSQL database capabilities
  • File storage support
  • Serverless function support
  • LLM-related backend capabilities
  • npx-based MCP installation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

19/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @insforge/install (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars38Stargazers on the source repository.
npm downloads364Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Insforge MCP works

What InsForge/insforge-mcp does

InsForge/insforge-mcp MCP server lets compatible coding agents work with backend services provided by InsForge. The supported backend areas include authentication, PostgreSQL database functionality, file storage, serverless functions, and LLM-related capabilities. It is intended for agents building or extending full-stack applications rather than for connecting directly to an unrelated database service.

The repository is the MCP component of the broader InsForge project. Installation, API details, usage examples, and the complete configuration guidance are maintained in the main InsForge repository and its documentation.

How it works

The MCP client starts the package with npx and passes connection settings through environment variables. The server uses the supplied API key to authenticate with InsForge and the API base URL to identify the instance it should contact. If no custom base URL is provided, the documented default is http://localhost:7130.

A typical manual configuration registers @insforge/mcp@latest as the command package. The same connection model can be configured automatically with the InsForge installer for supported clients. The repository also provides development commands for installing dependencies, running tests, linting, formatting, and building the package.

Setup and configuration

InsForge/insforge-mcp MCP server requires an InsForge API key. Set API_KEY to that value and set API_BASE_URL to the InsForge instance URL when the default local address is not appropriate.

The documented installer supports Claude Code, Cursor, Windsurf, Cline, and Roo Code. For example, an installation command can specify a client and pass both environment variables:

Terminal
npx @insforge/install --client cursor --env API_KEY=your_api_key --env API_BASE_URL=http://localhost:7130

Manual setup uses an MCP configuration entry with npx, the -y flag, and @insforge/mcp@latest. Replace the example API key with a real credential. The installer also has a development option for testing a dev version. Consult the InsForge documentation for client-specific configuration and the full setup process.

Tools and capabilities

The available capability areas described by the project are:

  • Authentication for application users
  • PostgreSQL-backed database features
  • File storage
  • Serverless functions
  • LLM capabilities

These areas provide the backend building blocks that an agent can use while working on a full-stack application.

Limitations and notes

The repository README delegates detailed installation instructions, configuration references, API documentation, tool examples, and contribution guidance to the main InsForge repository. It also does not describe deployment behavior, authentication scopes, database schema operations, storage limits, or function runtime details.

The examples use a local InsForge URL, but the configuration accepts a different API base URL for another instance. An API key is required in the shown setup. The project is licensed under Apache License 2.0.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Insforge MCP

InsForge/insforge-mcp is an MCP server that connects AI coding agents to the InsForge backend platform. Its main tools cover authentication, PostgreSQL databases, file storage, serverless functions, and LLM capabilities, allowing agents to build and manage full-stack application infrastructure through an InsForge instance.

Install it with the InsForge installer or add @insforge/mcp@latest to your MCP client configuration. The installer accepts a client name and API_KEY and API_BASE_URL environment values; manual setup uses npx with the same variables.

Yes, Cursor is supported by the documented installer. Run npx @insforge/install with --client cursor and provide API_KEY and API_BASE_URL; the base URL defaults to http://localhost:7130 when omitted.

API_KEY is required in the documented setup, and API_BASE_URL identifies the InsForge instance. API_BASE_URL can be omitted when using the default local endpoint, http://localhost:7130.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewInsforge MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/insforge-insforge-mcp?style=directory)](https://allmcps.com/mcp/insforge-insforge-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/insforge-insforge-mcp"><img src="https://allmcps.com/api/badge/insforge-insforge-mcp?style=directory" alt="Insforge MCP on AllMCPs" /></a>