InsForge
Manage InsForge BaaS—database, storage, edge functions, and deployments—from your agent without juggling dashboards.
Overview
InsForge is a MCP server for the Build phase that operates InsForge BaaS—database, storage, edge functions, and deployments—from your agent.
What is this MCP server?
- npm package @insforge/mcp v1.2.6 with stdio transport
- Tools cover database, object storage, edge functions, and deployments on InsForge
- Requires API_KEY and API_BASE_URL (project backend URL)
- Optional streamable-http remote at https://mcp.insforge.dev/mcp
- GitHub InsForge/insforge-mcp; BaaS-focused MCP, not a raw Postgres-only provisioner
- Package version 1.2.6
- 2 required environment variables (API_KEY, API_BASE_URL)
- 1 npm stdio package plus 1 optional HTTP remote
What problem does it solve?
Jumping between the IDE and InsForge consoles slows schema changes, uploads, functions, and deploy steps your agent could script.
Who is it for?
Solo builders on InsForge who want agent-driven backend and deploy workflows on a single BaaS stack.
Skip if: Projects on unrelated clouds only, or teams that refuse hosted BaaS API keys in the agent environment.
What do I get? / Deliverables
After configuring API_KEY and API_BASE_URL, your agent can drive InsForge resources and deployments from MCP tool calls.
- Agent-managed InsForge database and storage changes
- Edge function create/update workflows from the IDE
- Deployment actions coordinated through MCP tools
Recommended MCP Servers
Journey fit
How it compares
Full InsForge BaaS MCP, not a narrow database migration skill or generic Docker deploy script.
Common Questions / FAQ
Who is InsForge MCP for?
Developers building on InsForge who want Claude Code or Cursor to manage database, storage, edge functions, and deployments.
When should I use InsForge MCP?
Use it in Build while scaffolding or extending backend services and shipping iterations on InsForge-hosted apps.
How do I add InsForge MCP to my agent?
Install @insforge/mcp (npx) with stdio, set API_KEY and API_BASE_URL, or add the remote https://mcp.insforge.dev/mcp if your client supports streamable-http.