AiMatch

MCP1

MCP1 puts MCP servers behind a managed gateway so engineering and other teams can connect AI clients through one URL. Admins control access by group and review recorded tool activity.

Visit MCP1 Compare alternatives Own this tool? Claim it
MCP1 screenshot

Who it's for

  • Engineering teams connecting clients such as Claude Code or Cursor to shared servers such as GitHub, Linear, and Sentry.
  • IT and security teams that need group-based access rules, audit records, and controls for destructive tools.
  • Teams using browserless pipelines or agents that need scoped, expiring keys to access a gateway.

How it fits your workflow

Create a workspace, install servers from the catalog or add remote servers by URL, and configure shared gateways. Administrators grant gateways to groups and can set full or read-only access or restrict individual servers and tools.

People connect clients that support remote MCP over HTTP to the gateway URL and authenticate with their own accounts. Clients without OAuth use a key; automation keys can be scoped to a gateway and servers and set to expire.

MCP1 checks calls against workspace policies and records them with details such as actor, client, gateway, latency, and outcome. Administrators can review analytics and export audit activity as CSV.

Pricing

Free: The Individual plan is free for one member and includes up to 3 gateways and 15 servers.

Individual

Free

  • · 1 member
  • · 3 gateways
  • · 15 servers
  • · Catalog server installation with one-click authentication

Team

$12 per member per month

  • · Up to 25 members
  • · 25 gateways
  • · 100 servers
  • · Groups, shared gateways, and per-tool rules

Enterprise

$29 per member per month

  • · Up to 1,000 members
  • · 500 gateways
  • · 1,000 servers
  • · Everything in Team

Prices checked on Nov 9, 2026 from the vendor's site. They can change; confirm before you buy.

Key features

Single gateway URL
Bundle multiple MCP servers behind one URL for a team, so compatible clients connect to one gateway rather than configuring each server separately.
Managed server installation
Install servers from the catalog or add a remote MCP server by URL. MCP1 says it manages server tokens, checks health, syncs tools, and applies configured rules.
Group-based access policies
Administrators can grant groups full or read-only access to shared gateways, restrict access to particular servers or tools, and require admin approval for destructive tools.
Personal gateways
Workspace members can create personal gateways that combine their own servers and tokens with workspace servers available to their groups.
Authentication and scoped keys
Humans authenticate with their own accounts. For clients without OAuth and for automation such as CI, MCP1 supports keys that can be scoped to a gateway and servers and set to expire.
Audit log and analytics
The service records tool calls, sign-ins, and workspace changes, including the actor, client, gateway, latency, and decision. Users can search activity, export audit logs as CSV, and view usage and server performance metrics.

Works with

  • AI clients that support remote MCP over HTTP
  • MCP servers

Limitations to know

  • The Individual plan is limited to 1 member, 3 gateways, and 15 servers.
  • The Team plan is limited to 25 members, 25 gateways, and 100 servers.
  • The Enterprise plan is limited to 1,000 members, 500 gateways, and 1,000 servers.
  • Clients need to speak remote MCP over HTTP to connect as described; clients without OAuth require a key.

Alternatives to consider

  • One portal for all your MCP servers

    Choose it if you want a single MCP endpoint with native OAuth and a Code Mode meta-tool interface, rather than MCP1's team groups, access policies, and audit controls.

  • Forth MCP

    Choose it if you need to expose local, NAT'd, or firewalled MCP servers through a secure URL, rather than manage team access to installed or remote servers.

Compare MCP1 side by side

Getting started

A client that speaks remote MCP over HTTP; clients without OAuth use a key.

  1. Create a workspace.
  2. Install servers from the catalog or add a remote MCP server by URL.
  3. Create a gateway and grant it to the appropriate groups with the desired access rules.
  4. Connect an MCP-compatible client to the gateway URL and sign in.

Frequently asked questions

What is an MCP gateway?

It is one endpoint in front of MCP servers. Clients connect once; the gateway authenticates people, applies rules, and forwards each call to the appropriate server.

What is the difference between a shared and a personal gateway?

Admins create shared gateways from workspace-installed servers and grant them to groups. A personal gateway belongs to one person, who selects their own servers and workspace servers available to their groups.

Which clients work with MCP1?

The page says MCP1 works with clients that speak remote MCP over HTTP, including Claude, Claude Code, Cursor, VS Code, ChatGPT, Codex, Windsurf, and Gemini. Clients without OAuth use a key.

Where do server tokens live?

MCP1 says workspace server tokens are sealed with AES-256-GCM and are not shown to humans.

What happens when someone leaves the workspace?

Removing someone from the workspace stops every client they approved from working. The page also says an individual client or key can be revoked.

Is MCP1 compliant with SOC 2, GDPR, HIPAA, and CCPA?

The page states that MCP1 is SOC 2, GDPR, HIPAA, and CCPA compliant. It says a DPA is available for every workspace and a BAA is available on Enterprise.

What does MCP1 cost?

Individual is free for one member. Team costs $12 per member per month and Enterprise costs $29 per member per month. The page says seats follow the member count.