Managed MCP
Managed MCP Access For Your AI Agents, Powered By Cloudflare
We run MCP access for your team on Cloudflare, so your AI agents reach the tools they are supposed to reach and nothing else. Access is set person by person and tool by tool, the connection runs on our Cloudflare account rather than yours, and there is no gateway for you to host, patch or renew.
Why teams use Managed MCP
One endpoint, every connector
Every provider you attach arrives through the same connection, so your assistant is looking at one tool list rather than a dozen. Whether a given connector runs inside your own instance or somewhere across the internet makes no difference to what that list looks like.
Access decided per person
Access is set person by person and tool by tool, and none of it lives on their machine. Somebody in support and somebody in finance can point at the same gateway and be looking at two different tool lists, without either of them knowing the other list exists.
Nothing for you to run
This is a hosted service, so the operational side of it belongs to us. No container of yours sits in the path and no certificate of yours expires at an inconvenient moment.
What you get
Sixteen things the service does
All 16 of these come with Managed MCP, set up and looked after by our team.
Setup
- Attach unlimited connectors
- Live connection reporting
- One connection, scoped centrally
- Change access without reconnecting
- Central configuration
- Token authenticated connectors
- Per user, per tool access
Messaging
- One endpoint for everything
- Local and remote providers
- Tools stay namespaced
- Grant by provider or by tool
- Revoke in one place
- Add a provider once
- Managed and hosted
- Named client identity
- Credentials stay server side
Ready to hand over MCP access?
Tell us which tools your team uses and we will map out the access, per person and per tool.
An MCP gateway compared with wiring each server by hand
At one person and two tools, direct connections are the right call and a gateway would be overhead. The cost arrives with the third person or the fourth server, when every pairing turns into an entry somebody creates now and forgets to remove later.
| What to compare | How it works here |
|---|---|
| One connection vs one per server | Connecting directly means a separate entry for every server, recreated by hand on every machine and in every client that needs to reach it. |
| Access per tool vs all or nothing | A direct connection hands over whatever that server exposes, because there is no layer in between with the authority to narrow it down. |
| Keys held once vs pasted everywhere | Direct connections put a copy of every key into every person’s configuration file, which is where credentials go to leak and where rotation quietly fails to reach. |
| Add once vs set up for everyone | Without a gateway, each person repeats that setup themselves, and you find out who missed a step when something quietly does not work for them. |
| Revoke once vs chase every config | With direct connections you have to know every server they held and reach every machine storing those credentials, which in practice means some access quietly survives. |
| One tool list vs a pile of entries | Who this is for |
What clients say about working with Cascadia
Questions about Managed MCP?
Talk to us
Who needs a gateway, and who does not
Teams sharing one set of tools
Everyone connects to the same address and sees only what you granted them. A new starter is working on their first morning without anybody walking them through a config file, and somebody leaving loses access in one action, not several.
Agencies working across client systems
Keep every client’s connectors attached in one place and hand each person only the ones they actually work on. Nobody carries credentials for accounts they have no business reaching, and moving somebody onto a new client means changing permissions, not redoing setup.
Anyone running several MCP servers
Past three or four servers, keeping separate entries current in every client stops being trivial. One address covering all of them removes that bookkeeping without removing any of the tools, and adding a fifth costs you nothing on the client side.
How setting it up actually goes
1. Sign up and create your gateway
Signing up is free. You get your own gateway endpoint, and that address is what every assistant and every person on your team points at from here on.
2. Attach the providers you want
Add each MCP server you want to reach, whether it is one of ours, one you already run yourself, or a third party service. Credentials go in here, once.
3. Grant people the tools they need
Add your team and choose, tool by tool, what each person can reach. They add one entry pointing at the same address you use, and see exactly what you granted and nothing else.
Pricing
What Managed MCP costs
Charged per person rather than per connector, with the apps and agents each person uses set up as part of the service. Tell us how many people need access and which tools they work in, and we will put a number to it.
Ask for a quoteNo obligation, and no call required.Ask us
Questions people ask before signing up
Weighing us against another option? Our comparisons take the main ones in turn.
What is the Managed MCP?
It is a managed MCP gateway. Instead of wiring each MCP server into each AI assistant separately, you attach your connectors to the service once and point your assistant at a single endpoint. Everything you have been granted shows up in one tool list. We host and run it, so there is no server for you to deploy or maintain.
How is this different from connecting each MCP server directly?
Connecting directly means one configuration entry per server, per client, per person. Ten tools across five people is fifty pieces of setup to create and later maintain. The service collapses that to one connection each. You attach a provider once centrally, and everyone you grant it to picks it up without touching their own configuration.
Is this an MCP gateway?
Yes. Gateway, gateway, proxy, and aggregator all describe the same pattern: a single service sitting between your AI assistants and the MCP servers behind them. We call ours a gateway because it also decides which person reaches which tool, rather than only forwarding traffic to whatever sits downstream.
How many connectors can I attach?
There is no limit. Each connector you attach joins the same endpoint, and its tools appear alongside everything else already connected. Tools stay tagged with the connector they came from, so two providers offering similarly named operations do not collide or get mistaken for one another.
How do per-user permissions work?
Access is set per person and per tool. You can enable a whole connector for somebody, or pick out individual tools from it. Changes apply to their existing connection, so nobody has to reconnect, re-authenticate, or edit a config file when you adjust what they can reach.
Can two people share one gateway and see different tools?
Yes, and this is the main reason to run one. Both people connect to the same endpoint with the same setup steps, but each sees only the tools you have granted them. Their assistants show different tool lists without either person configuring anything differently.
Where does the service run?
On our infrastructure. It is a managed service, so you connect to an endpoint we operate rather than standing anything up yourself. That means no deployment, no patching, and no uptime to watch.
Do I need to install or host anything?
No. You sign up, attach the providers you want, and add one entry to your assistant’s configuration pointing at the service. There is no package to install, no container to run, and no certificate to manage. The connectors behind the service can be ones we host or ones you already run yourself.
Is there a free option?
Yes. A free account gives you one user with no limit on how many connectors you attach, so you can wire up your real providers and use it properly rather than poking at a demo. Adding a second person is what moves you onto paid seats, at which point the per user rate applies across the account.
What can I connect to it?
Any MCP server the service can reach. That includes connectors running locally inside an instance and connectors reachable over HTTPS, at the same time, in the same tool list.
How are provider credentials handled?
The service holds them. Keys stay server side rather than being copied into each person’s assistant configuration, where they are easy to leak and painful to rotate. When a credential changes you update it once centrally, and every connected user keeps working because none of them were holding it.
How do I remove someone’s access?
In one place. Because everybody connects through the same endpoint rather than holding their own direct connections, revoking a person is a single action rather than a hunt through separate client configurations to find every connector they were ever given.
Can I use it with Claude Desktop?
Yes. Add the service as a connector in your client and it appears as one entry exposing every tool you have been granted. This works the same way in any MCP compatible client, and it replaces the separate entry you would otherwise need for each individual server.
How do I see what is currently connected?
Ask the service. It reports back the client identity it sees, every active integration with its address, and the total number of tools currently exposed to you. That gives you a quick way to confirm a new provider attached correctly and that a person is seeing what you expect them to see.
Ask Us Anything
We’d love to hear from you!