Open-source · Self-hosted · Sovereign

All your MCP servers.
One endpoint.

Self-host an autonomous MCP gateway. Bring your own LLM, run fully offline (with a local LLM), and keep every byte on your infrastructure. AGPLv3.

AGPLv3 · Bring your own LLM · Run fully offline (with a local LLM)
Se
J
Fi
Dr
Sb
Dd
Hs
Gr
gh
N
#
S
Pg
L
One MCP endpoint /mcp/sse
Any MCP client
Claude Cursor Cline Mistral
Own
Your registry, your servers
0+
Curated starter pack
Air-gap
Run fully offline
AGPLv3
Free, self-host, no limits
The MCP sprawl problem

Every server, every device, every credential

As soon as a team adopts more than a couple of MCP servers, configuration sprawl and access risk explode. BigMCP collapses it into one governed gateway you run yourself.

✕

Without BigMCP

  • ×Install & update MCP servers on every device
  • ×Configure credentials separately, everywhere
  • ×No access control over who runs which tool
  • ×Zero visibility into who used what, when
  • ×Re-do the whole setup for each new teammate
✓

With BigMCP

  • ✓One governed endpoint for every connected tool
  • ✓Credentials encrypted at rest (Fernet) — User › Org › Server
  • ✓RBAC across 4 roles, scoped per Tool Group
  • ✓Immutable, HMAC-signed audit logs
  • ✓Self-hosted: your infrastructure, your rules
How it works

From scattered servers to one governed URL

View as
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
claude_desktop_config.json
{
  "mcpServers": {
    "bigmcp": {
      "url": "https://acme.bigmcp.cloud/mcp/sse",
      "headers": {
        "Authorization": "Bearer mcphub_sk_••••"
      }
    }
  }
}
Your registry

Your registry + a curated marketplace

Declare your private MCP servers. Or pick from a curated 180+ starter pack — npm, GitHub, Glama, Smithery. All in one search, behind one URL.

gh
GitHub
N
Notion
#
Slack
S
Stripe
Pg
PostgreSQL
L
Linear
Se
Sentry
J
Jira
Fi
Figma
Dr
Drive
Sb
Supabase
Dd
Datadog
Hs
HubSpot
Gr
Grist
aws
AWS
▲
Vercel
Cf
Cloudflare
gh
GitHub
N
Notion
#
Slack
S
Stripe
Pg
PostgreSQL
L
Linear
Se
Sentry
J
Jira
Fi
Figma
Dr
Drive
Sb
Supabase
Dd
Datadog
Hs
HubSpot
Gr
Grist
aws
AWS
▲
Vercel
Cf
Cloudflare
Cf
Cloudflare
▲
Vercel
aws
AWS
Gr
Grist
Hs
HubSpot
Dd
Datadog
Sb
Supabase
Dr
Drive
Fi
Figma
J
Jira
Se
Sentry
L
Linear
Pg
PostgreSQL
S
Stripe
#
Slack
N
Notion
gh
GitHub
Cf
Cloudflare
▲
Vercel
aws
AWS
Gr
Grist
Hs
HubSpot
Dd
Datadog
Sb
Supabase
Dr
Drive
Fi
Figma
J
Jira
Se
Sentry
L
Linear
Pg
PostgreSQL
S
Stripe
#
Slack
N
Notion
gh
GitHub
Starter pack

Connect public servers in one click

Add Gmail, Linear, Notion or Slack straight from the curated starter pack — credentials auto-detected.

Custom

Build custom tools on your stack

Wire BigMCP to Grist, Airtable, a Notion database or your internal API. Ship custom MCP tools for your team's widgets — tasks, projects, dashboards.

Sovereign

Run fully sovereign

Your private registry only, a local LLM (Ollama, vLLM), and air-gap mode on. Nothing leaves your network.

Platform

Everything a team needs to run MCP in production

Custom server management

Register from any source — npm, pip, GitHub, Docker, HTTP, local binary. Auto-discovery via tools/list. Team vs personal visibility.

Selective exposure

Tool Groups with PRIVATE / ORG / PUBLIC visibility, plus scoped API keys exposing only the tools you choose.

Auth & security

OAuth 2.0 + PKCE, JWT, MFA/TOTP, API keys (bcrypt), credentials encrypted at rest with Fernet.

Multi-tenant by design

Organization isolation with 4-tier RBAC and hierarchical credentials. Unlimited users and orgs.

Custom MCP registry

Declare your private MCP servers and keep them entirely inside your network. Air-gap compatible, full sovereignty.

AI orchestration

Natural language to workflow, a composition lifecycle, and durable steps that survive crashes and restarts.

Durable workflows · Phase B-1

Compositions that survive crashes & restarts

A resumable executor persists every step in Postgres. Promote a validated composition and it becomes a first-class MCP tool. Five suspending step types pause and resume cleanly:

Plus non-suspending steps transform (LLM JSON extraction) and foreach (fan-out over a list) — shipped in 2.5.

01elicitPause mid-flight for human input
02wait_untilClock-driven resume at a future time
03wait_callbackHMAC-protected webhook resume
04subcompositionCall another composition, suspend until it ends
05approvalCross-user gate, four-eyes by default
Governance

Full control over who sees what

Four roles, hierarchical credentials, and immutable audit logs with HMAC-SHA256 integrity. Run a hardened, closed deployment with the marketplace disabled and custom servers only.

User › Org › Server credentialsHMAC-signed audit trailClosed registry modeAir-gap modeOAuth 2.0 + PKCE
OwnerFull control of the org, billing & members
AdminManage servers, groups, keys & policies
MemberUse assigned Tool Groups, run tools
ViewerRead-only visibility into the catalogue
How we compare

Compared, on the axes that matter to a sovereign deployment

We don't claim to be the only answer. Where BigMCP is built to win is autonomy — you choose the LLM, you hold the data, and you run the infrastructure. No proprietary lock-in, no per-seat gate.

CapabilityBigMCPAnthropic CloudClosed SaaSDIY
Self-host (AGPLv3)✓—SaaS only✓
Choose your own LLM (BYOL)✓Claude onlyvendor lock-in✓
Air-gap support✓——depends
Data residency controlfullvendorvendorfull
Custom MCP serversunlimitedvendor cataloguevendorunlimited
Built-in RBAC + audit✓partialpaid tierbuild
Durable workflows✓ B-1—paid tierbuild
No vendor lock-in✓ AGPLv3proprietaryproprietaryyour code
Sovereign by default

Nothing leaves your network

Self-host BigMCP with your own LLM. Everything else stays inside your network. Built for sensitive data, regulated industries, and sovereign deployments.

Public internet no outbound traffic
Your network · VPC
BigMCP gatewayone governed URL
Local LLMOllama · vLLM
Private registryyour MCP servers
Data planePostgres · Redis · Qdrant
White-label · Make it yours

Your BigMCP. Your brand.

Ship a gateway your teams recognize as yours. Set a custom instance name, drop in your logo, and pick a primary color — on your own domain, in your own palette. No "powered by", no compromise.

#D97757 — — recolors the entire page live. Scroll up and watch.
acmemcp.bigmcp.cloud
Sign in
● Internal MCP gateway
All your tools.
One endpoint.
Get started
instance_name

One URL for every tool your agents need

Free and open source under AGPLv3. No user limits, no license keys. Self-host in minutes or try the live demo.

AGPLv3 · Self-host · BYOL