/

MCP Gateway

MCP GATEWAY

The MCP gateway that gives AI agents access, not unlimited access

Connect AI agents to every MCP server and enterprise tool through one gateway, with per-tool permissions, enforced policies and a complete audit trail.

Trusted by teams operating AI in production

  • Thales logo
  • bunq logo
  • NOC*NSF logo
  • Capgemini logo
  • Helloprint logo
  • Vattenfall logo
  • Moss logo
  • hear logo
  • Yoco logo

Tool sprawl

MCP tool sprawl: every new connection widens what agents can reach

Every new tool connection expands what agents can reach, change and expose. Without centralized control, permissions become fragmented and accountability disappears.

AI agents connecting directly to many MCP servers and tools without central control

How it works

How the MCP gateway works: one control point for every MCP server

Define which agents and teams can access which tools, and exactly what they are allowed to do.

AI agents reaching MCP servers and tools through the Orq.ai MCP gateway with per-team permissions

Sovereignty and compliance

Enterprise control. European sovereignty.

Govern tool access with European deployment options, centralized audit evidence and infrastructure suited to regulated environments.

01-europe-data-residency

EU entity, EU cap-table

No US parent company, No CLOUD act exposure. Your vendor and your data sit under the same jurisdiction.

02-compliance-and-security

Security and compliance documentation

Request the SOC 2 Type II report, ISO 27001 status, HIPAA BAA and GDPR DPA through our Trust Center.

03-connected-infrastructure

Deploy your way

Fully managed, in your own EU region, or air-gapped on your own servers with no egress and no telemetry.

04-usage-and-reporting

Evidence you can hand over

Every tool call is logged and exportable, so audit trails come out of the platform rather than out of a spreadsheet.

FAQs

Frequently Asked Questions

What is an MCP Gateway?

An MCP gateway sits between your AI agents and the tools they use, giving every team a scoped set of tools with shared authentication, guardrails, and an audit trail. This avoids each agent connecting directly to raw MCP servers.

How is this different from the AI Gateway?

The AI Gateway governs which models your agents can call. The MCP gateway governs which tools they can call. Both run on the same control plane, so policies and observability stay consistent.

Can I control what each team can access?

Yes. Use a virtual MCP server per team, with read and write permissions set per tool, not just per integration.

Does this work with coding agents?

Yes. Claude Code, Cursor, Warp, Codex, and other agent harnesses connect through the same gateway as any other agent.

What’s the difference between an MCP proxy, a gateway, and a registry?

A proxy forwards traffic. A registry lists available servers. A gateway does both and enforces policy on every call: who can reach which tool, what they can do with it, and what gets logged.

How is this different from the Orq.ai MCP server?

The MCP server points inward, letting tools like Claude Code and Cursor reach your Orq.ai workspace. The MCP Gateway points outward, at the tools your agents use.

Does it support multi-tenancy?

Yes. Configure separate permissions and audit trails by team, project, or environment.

Can I self-host it?

Yes. Fully managed, in your own EU region, or air-gapped on your own infrastructure.

What security and compliance documentation is available?

The Orq.ai Trust Center provides access to our SOC 2 Type II report, ISO 27001 status, HIPAA BAA and GDPR DPA. These documents are available through an access request.

Bring every MCP connection under one governance layer

Bring agent-tool access under the same governance layer as your AI models.

Bring every MCP connection under one governance layer

Bring agent-tool access under the same governance layer as your AI models.

Bring every MCP connection under one governance layer

Bring agent-tool access under the same governance layer as your AI models.