InsForge MCP Server
MCP server for the InsForge backend: the agent creates tables, buckets and edge functions and ships the app from the editor
- 38 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The `run-raw-sql` tool executes any SQL with the project key's rights and can delete data
- The agent creates and deletes buckets and starts deployments, changing the project's live resources
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/insforge-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The `run-raw-sql` tool executes any SQL with the project key's rights and can delete data
- The agent creates and deletes buckets and starts deployments, changing the project's live resources
This is third-party code. Review the repository files before installing.
What it does
InsForge is a backend platform with a database, file storage, edge functions and deployments. The MCP server in this repository connects an agent to it: the agent reads table schemas and backend metadata, runs raw SQL, creates and deletes buckets, writes and updates functions, starts deployments and reads container logs. The agent also pulls platform and SDK documentation and fetches the project's anonymous key through dedicated tools. That lets it build against the current API description and not lean on the model's outdated guesses. The server runs two ways. Locally, npx @insforge/mcp starts it with the project key and backend URL in environment variables. The remote option at https://mcp.insforge.dev/mcp is listed in the MCP registry's server.json and signs in through OAuth.
Who it is for. Developers who build apps with Claude Code, Cursor, Windsurf or Cline and want the agent to handle the database, files and deployment on a single backend.
Good fit when
- The prototype is just starting and the agent has to create tables, an upload bucket and a first edge function
- A container crashes after a deploy and the agent needs the logs to find the cause
- The agent writes client code and must check it against the current InsForge SDK docs
- The database schema has to be checked or adjusted mid-development through SQL
Not a fit when
- The app lives on another backend: the tools work only with an InsForge project
- The database holds production data and the project key is too broad: SQL runs without extra safeguards
- You only need the platform documentation: it can be read on the site with no project access
Example request
Create a notes table with title and body fields, a bucket for attachments and a function that clears old notes.MCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
API_KEYrequired, secret- InsForge project API key
API_BASE_URL- Backend URL, defaults to a local instance on port 7130
Limitations
You need an InsForge project: an ik_ API key and the backend URL. The URL defaults to a local instance at http://localhost:7130 and is replaced for a cloud project. The npx @insforge/install installer writes the server into the configuration of Claude Code, Cursor, Windsurf, Cline, Roo Code, Codex or Trae.
The `run-raw-sql` tool executes any SQL with the project key's rights, while bucket deletion and deploys change live resources. The README gives no detailed tool list or API version and points to the documentation in the main InsForge repository.
How to disable. Remove the insforge entry from the MCP client settings and restart the client. Rotate the project key in the InsForge dashboard if needed.
FAQ
How do I connect InsForge to Claude Code or Cursor?
Copy the command from the Connect button in the project dashboard or build your own: npx @insforge/install --client claude-code --env API_KEY=... --env API_BASE_URL=.... Use cursor, windsurf, cline, roocode, codex or trae in place of claude-code.
How do I configure the server by hand?
Add an insforge block under mcpServers with the npx command and the arguments -y @insforge/mcp@latest, and pass API_KEY and API_BASE_URL in env. The default URL points at a local backend, so replace it with the project URL for the cloud.
What can the agent do with the database?
Read a table schema with `get-table-schema`, check backend metadata with `get-backend-metadata` and run SQL with `run-raw-sql`. The last tool is not limited to reads, so the project key decides what the agent can change.
Does the server have a remote mode?
Yes, the MCP registry's server.json lists https://mcp.insforge.dev/mcp with the streamable-http transport. The repository implements OAuth, project selection and access token handling for it.
What tools exist besides the database?
Buckets: `create-bucket`, `list-buckets`, `delete-bucket`. Edge functions: `create-function` and `get-function`. Deployment: `create-deployment` and `get-container-logs`. Documentation: `fetch-docs`, `fetch-sdk-docs` and `get-anon-key`.
Discussion
No questions or reviews yet.
Related
MCP serversFireCMS Cloud MCP server: an agent reads Firestore data, infers collection schemas and manages the project's users.
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
Apollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
mcp-graphql: MCP server for GraphQL APIs
mcp-graphql
Two GraphQL tools for MCP clients: the agent fetches your API schema and runs queries against a single endpoint
Rebase MCP server: the agent edits the schema, documents and users of a Postgres backend, with writes limited to localhost
An MCP server and plugin for agents that generate web APIs from OpenAPI, AsyncAPI, GraphQL, gRPC and SQL specs on a Rust core.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| InsForge MCP Server (this card) | yes | API key | 38 | |
| Supabase MCP Server | yes | OAuth | 3,008 | the Supabase backend on PostgreSQL |
| Appwrite MCP server | yes | OAuth | 72 | the Appwrite backend with its own API |
| Neon MCP Server | yes | OAuth | 663 | managed Postgres only, with no functions or deployment |
README in short
The README mostly points to the main InsForge repository for instructions and tool descriptions. It adds a quick start with the installer for six clients, manual setup and development commands for tests, lint and build.