On Page Navigation

One MCP Gateway For All Your Connectors Tools Users

MountDev AI MCP Router puts every connector your team uses behind a single endpoint, and lets you decide tool by tool what each person can reach. Nobody wires up a separate connection for every server, and nobody ends up holding a credential they could leak. Running it is our job rather than yours, and signing up is free.

Cascadia engineer writing WordPress code across dual monitors.

Built for teams running many tools

What changes when every connector shares one endpoint

A gateway moves one decision. Rather than each person assembling their own set of connections and holding the credentials that go with them, providers attach centrally and reach becomes something you grant. The six points below are where that shows up in ordinary work.

Gateway versus direct

An MCP gateway vs 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. These are the six places that difference bites.

One connection vs one per server

Your assistant holds a single entry pointing at the gateway. 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

Grant somebody three tools out of a connector and leave the rest closed. 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

The gateway stores provider credentials centrally. 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

Attach a new provider and grant it to whoever needs it. 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

Removing somebody is one action. 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

Everything you have been granted arrives together, tagged by the connector it came from. Managing a dozen separate entries per client is where setup drifts and people end up running different versions of it.

Who this is for

Who needs a router, and who does not

The gateway earns its place when more than one person needs more than one tool. A solo developer with a single connector does not need it. A team where different people should reach different systems does, and so does anybody who has tried to cleanly remove someone's access after they left.

Getting started

How setting it up actually goes

Three steps, none of which involve installing software. The longest part is deciding who should be able to reach what, and even that is a matter of ticking boxes once your providers are attached.

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. There is no infrastructure to provision first, so your first provider can go on straight away.

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. Attach as many providers as you like now, or come back and add more later.

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. Anything you change afterwards reaches them without a message asking anyone to reconnect.

What it costs

Pricing

Team Plan

Per User

Free
/user, per month
Starts free with one user included

DETAILS

Ten dollars per user, per month, with the rate coming down as your team grows. Connectors are not what you are billed for, so a tenth provider costs exactly what a second one does. The free tier is one user with no cap on what you attach, and seats only start counting when a second person needs their own access.

Testimonials

Here's what others had to say

Everything included

Sixteen things the router does

Cascadia Web Services logo

One Endpoint For Everything

Point your assistant at a single URL and reach every connector you have enabled. Adding a provider no longer means adding another connection to every client that needs it.
Cascadia Web Services logo

Attach Unlimited Connectors

There is no cap on how many providers you attach. Each one joins the same endpoint, and the tools it exposes appear alongside everything else already connected.
Cascadia Web Services logo

Local And Remote Providers

Attach connectors running inside your own instance and connectors reachable over HTTPS at the same time. The assistant sees one list of tools and does not care where each one lives.
Cascadia Web Services logo

Live Connection Reporting

Ask the router what it is connected to and it answers with the client identity, every active integration and its address, and the total number of tools currently exposed.
Cascadia Web Services logo

Tools Stay Namespaced

Every tool arrives tagged with the connector it came from, so two providers offering similarly named operations never collide or get confused for one another.
Cascadia Web Services logo

Per User, Per Tool Access

Enable and disable individual tools for each person. Two people can share the same router and see completely different tool lists, without either of them configuring anything themselves.
Cascadia Web Services logo

One Connection, Scoped Centrally

Each person connects once to the same endpoint. What they can actually reach is decided centrally, so an access change takes effect without anyone editing a configuration file.
Cascadia Web Services logo

Grant By Provider Or By Tool

Turn on an entire connector for someone, or pick out individual tools from it. Access is shaped to the person rather than handed over in one block.
Cascadia Web Services logo

Change Access Without Reconnecting

Adjust what somebody can reach and their existing connection picks it up. They do not need to reconnect, re-authenticate, or touch their assistant configuration for it to apply.
Cascadia Web Services logo

Revoke In One Place

Removing a person's access happens once, centrally. There is no hunt through separate client configurations to track down every connection they were given along the way.
Cascadia Web Services logo

Central Configuration

Provider addresses, credentials, and settings live in one place instead of being copied into every assistant that needs them and drifting out of sync over time.
Cascadia Web Services logo

Add A Provider Once

Attach a new connector and it becomes available to everyone you grant it to. There is no per-user setup step and no credential to reissue to each person.
Cascadia Web Services logo

Managed And Hosted

The router runs on our infrastructure. There is nothing for you to deploy, patch, monitor, or keep running, and no server of your own sitting in the path.
Cascadia Web Services logo

Named Client Identity

Every connection carries the identity of the person using it, so activity through the router is attributable to a named individual rather than to one shared anonymous key.
Cascadia Web Services logo

Token Authenticated Connectors

Downstream connectors accept traffic only when it carries the shared secret the router holds, so a publicly reachable connector rejects anything arriving without it.
Cascadia Web Services logo

Credentials Stay Server Side

Provider keys are held by the router rather than distributed into each person's assistant configuration, where they are easy to leak and painful to rotate afterwards.

Questions people ask before signing up

Frequently asked questions
What is the MountDev AI MCP Router?
It is a managed MCP gateway. Instead of wiring each MCP server into each AI assistant separately, you attach your connectors to the router 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 router 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, router, 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 router 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 router 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 router 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. If you would rather self-host the individual connectors, our Frappe and WordPress connectors are free and open source for exactly that.
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 router. There is no package to install, no container to run, and no certificate to manage. The connectors behind the router can be ones we host or ones you already run yourself.
What does it cost?
Pricing is per user, per month, starting at ten dollars for each person connected. The rate comes down as your team grows, so larger groups pay less per seat. You pay for the people using it rather than for the number of connectors you attach or the tools they reach, which means adding another provider never changes your bill.
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 router can reach. That includes connectors running locally inside an instance and connectors reachable over HTTPS, at the same time, in the same tool list. Our own Frappe and WordPress connectors are built to sit behind it, and any standards compliant MCP server works the same way.
How are provider credentials handled?
The router 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 router 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 router. 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.
​Contact

Ask Us Anything

We’d love to hear from you!