MCP1
Start with MCP1

The MCP gateway for teams

One URL for every MCP server

Give every agent on your team the tools it needs, without handing out a single API key. Humans authenticate once, admins decide who can call what, and every call is on the record.

Start with MCP1Read the docs
  • Claude Code
  • Claude
  • Cursor
  • ChatGPT
  • Codex
  • Gemini
mcp1.com/moonbase/settings/audit

Audit log

Every call, sign-in and change, as it happens.

Human
EventStatus
github__search_codeOK
appwrite__list_rowsOK
stripe__create_refundBlocked
github__merge_pull_requestBlocked
sentry__resolve_issueBlocked
notion__searchOK
linear__create_issueBlocked

Support has read-only access to the Engineering gateway, so writes are blocked.

How it works

Set it up once. Every client follows.

No more pasting server tokens into every laptop. Admins install servers and share gateways; everyone else connects one URL.

Install your servers

From the catalog or any remote MCP server by URL. Their tokens stay sealed in MCP1, never on a laptop.

Share gateways with groups

Bundle servers behind one URL per team. Grant it to groups, fully or read-only, and hold any tool to fewer.

Everyone connects once

Claude, Cursor, ChatGPT and the rest add the URL and sign in with their own account. Their groups decide the rest.

A super agent

Your agent, with the whole company behind it

Through one gateway, your agent reaches support, feedback, code, errors, revenue and data, each under your own permissions. Ask a question that spans departments and get an answer you can act on.
  • Support
  • Feedback
  • Code
  • Reliability
  • Revenue
  • Data
Claude · connected to MCP1 6 servers
Should we ship the new pricing page this week?
  1. notion__search38 tickets mention the old pricing page this monthSupport
  2. linear__list_issues12 feature requests ask for annual billingFeedback
  3. github__search_pull_requestsPricing v2 is merged, behind a flagCode
  4. sentry__search_issuesNo open errors on /checkout in 7 daysReliability
  5. stripe__list_subscriptionsAnnual plans convert 2.3× better in the test cohortRevenue
  6. appwrite__list_rowsPricing page bounce rate is down 18% in the testData

Yes, ship it Thursday, annual plans first. The code is merged and checkout is clean, annual billing is the top request and converts 2.3× better, and the old page drives 38 support tickets a month.

6 tool calls across 6 departments · every call checked and recorded by MCP1

LNLevi van NoortFirst day at MoonbaseEngineering
  1. Invited to Moonbase09:02by Matej, as a developer
  2. Added to Engineering09:02GitHub, Linear, Notion and Sentry, open to the group
  3. Connected Claude Code09:04one URL, one authentication, no tokens to hand out

“How do we ship a change to the API?”

09:06

Open a PR against main; CI runs the contract tests, and merging deploys to staging. Production goes out on Thursdays from the release ticket, following the deploy runbook.

  • notion__search
  • github__get_file_contents
  • linear__list_issues

Onboarding

New teammates move fast from day one

Add someone to a group and their agent can reach everything that team knows. No access requests, no tokens passed around, no week of setup before they ship.
  • One invite, everything they needGroups carry the servers and tools a team uses, so joining a group is the whole setup.
  • The company’s knowledge in every chatRunbooks, code, tickets, dashboards and data answer their questions from the first hour.
  • Access that follows the org chartMove someone to another team and their tools move with them. Remove them and it all closes at once.

For teams

Every gateway, group and tool, decided

Admins set shared gateways and the groups that reach them. Everyone else gets a gateway of their own. Every call is checked against both.

Groups decide who reaches what

Grant a shared gateway to groups, fully or read-only. Limit servers and single tools to certain groups. Admins always get through; auditors read but never call.

A gateway of your own

Everyone can build their own: their personal servers with their own tokens, plus the workspace servers open to their groups.

Guardrails

Destructive tools need an admin. Members can be held to read-only. Everyone has a rate limit.

Keys for CI

For pipelines and agents without a browser. Made for one gateway, scoped to servers, set to expire, stored only as a hash.

An audit log of every call

Who called which tool, through which gateway and client, how long it took and what MCP1 decided.

Observability

See what your agents actually do

Every call through the gateway is recorded and measured. Admins see usage across the workspace, members see their own, and anyone can ask their agent about it.

  • Pay for what gets used

    See which servers and tools each team relies on. Drop the ones nobody calls and invest in the ones that work.

  • Catch problems early

    Success rate and p95 latency per server show a failing or slow server before anyone files a ticket.

  • Measure AI adoption

    Active humans by group and client show where agents took hold and which teams need a hand.

  • Prove what happened

    Who called what, from which client, on whose behalf, and whether policy allowed it. Export it as CSV.

UsageMoonbase Export CSV

Tool calls

32,937↑ 18%

Last 30 days

Success rate

97.4%↑ 0.6%

318 blocked · 538 failed

Active humans

86↑ 12

of 104 members

Latency

412 ms↓ 9%

p95 · median 168 ms

Calls

Per day
2k1k0
Oct 4Oct 14Oct 24Nov 2

Servers

Calls
  1. GitHub99% ok11,204
  2. Linear98% ok6,882
  3. Notion99% ok5,931
  4. Sentry91% ok4,316
  5. Stripe97% ok2,148
“Why did Sentry calls fail this week?”mcp1__search_audit

One-click setup

One gateway. Every server, managed.

Install a server in one click and MCP1 runs the rest: tokens sealed, health checked, tools synced and held to your rules. Your clients only ever see one URL.

149 servers, a catalog for every team

Engineering, product, data, support, sales, marketing, finance, operations and security each get their own catalog. Anything else, add by URL.

Browse the catalog

Security and compliance

Ready for your security review.

The gateway your agents call is certified, encrypted end to end and audited on every call, so your security team can sign off once.
  • SOC 2

    SOC 2

    Audited controls for security, availability and confidentiality.

  • GDPR

    GDPR

    EU data protection, with a data processing agreement for your workspace.

  • HIPAA

    HIPAA

    Safeguards for health data, with a BAA available on Enterprise.

  • CCPA

    CCPA

    California consumer privacy rights, honored for every member.

  • Encrypted everywhere

    Server tokens, OAuth grants and call arguments sealed with AES-256-GCM. TLS on every endpoint.

  • Hosted in the EU

    Your workspace and audit log live in Frankfurt.

  • A record of every call

    Who called which tool, from which client and gateway, and whether it was allowed.

  • Backups and recovery

    Regular encrypted backups and a tested business continuity plan.

  • Tested from outside

    Regular third-party penetration tests and dependency scans.

Pricing

Free for one. Per member for teams.

Start on your own for free. Move to Team when you want shared gateways for your groups.

Individual

For one human wiring up their own agents.

Free

  • 1 member
  • 3 gateways
  • 15 servers
  • Every catalog server, one-click auth
  • Policies and audit log
Start free

Team

Most teams

For teams sharing gateways with groups.

$12per member / month

  • Up to 25 members
  • 25 gateways
  • 100 servers
  • Groups, shared gateways and per-tool rules
  • Usage analytics and audit export
Start with Team

Enterprise

For organizations running MCP at scale.

$29per member / month

  • Up to 1,000 members
  • 500 gateways
  • 1,000 servers
  • Everything in Team
  • IP allowlists for gateways
  • Invoiced billing on request
Contact sales

FAQ

Questions

What is an MCP gateway?

One endpoint in front of your Model Context Protocol servers. Clients connect to it once; it authenticates humans, applies your rules and forwards each call to the right server.

What’s the difference between a shared and a personal gateway?

Admins make shared gateways from the workspace’s installed servers and grant them to groups. A personal gateway belongs to one human, who picks its servers: their own, with their own tokens, and workspace servers open to their groups.

Which clients work with MCP1?

Any client that speaks remote MCP over HTTP: Claude, Claude Code, Cursor, VS Code, ChatGPT, Codex, Windsurf and Gemini among them. Clients without OAuth use a key.

Where do server tokens live?

In MCP1, sealed with AES-256-GCM. Humans never see the workspace’s tokens, and nobody else can use a personal server’s.

What happens when someone leaves?

Remove them from the workspace and every client they approved stops working. You can also revoke a single client or key.

Is MCP1 compliant with SOC 2, GDPR and HIPAA?

Yes. MCP1 is SOC 2, GDPR, HIPAA and CCPA compliant. A DPA is available for every workspace and a BAA on Enterprise.

What does it cost?

Individual is free for one human. Team and Enterprise are billed per member each month, and seats follow your member count.

Give your team one URL

Create a workspace, install your servers and share a gateway. It takes a minute.

Start with MCP1Read the docs