MCP Gateway
The MCP Gateway for enterprise AI
Connect AI agents to tools without giving up control. Govern every Model Context Protocol (MCP) connection with access controls, policies and a complete audit trail.
Secure by design
European sovereign
One decision point for models and tools
Tool sprawl
Every new tool is a door into your systems
Connect a tool once, and every agent that can reach it gets full read and write access.
All-or-nothing access
One connection means every agent gets read, write, and delete on that tool - not only the parts a team actually needs.
how we solve the problem
Every team gets the access it needs. Nothing more.
An MCP Gateway sits between your agents and your tools, deciding which ones each team can reach and what they can do there. Orq.ai scopes that per tool and per action.
Marketing can publish
Engineering can deploy
Finance can read
You decide
FEATURES
One governance layer for every tool your agents can reach
Set who can access what, enforce policies on every call and keep a complete record of what happened across teams, agents and MCP servers.
Compliance and deployment
Built for regulated industries
European jurisdiction, certified infrastructure, and deployment that matches your data posture. Designed for regulated organizations preparing for the operational requirements of the EU AI Act.
Skills
Skills, governed the same way
Push approved skills, including your brand voice and workflows, to the teams that need them, and update everyone at once. Distributed through the same gateway that governs your tools.
Why Orq.ai
Nothing new to run
Most MCP gateways are point solutions bolted onto your AI infrastructure. Orq.ai's MCP gateway shares policies, guardrails, and observability with our AI Gateway.
Trusted by teams shipping AI at scale
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 compliance certifications do you hold?
SOC 2 Type II, ISO 27001, GDPR, and HIPAA, with EU AI Act support built in. Orq.ai is an EU entity with an EU cap-table.
Bring your tools under the same control you already have over your models
MCP Gateway is in final testing. Get early access.