330 tools in. About 20 in the menu.
Every Parsons product and any MCP server you register, behind one address. Then profiles: a curated set of tools with its own private URL, for each assistant, each teammate, each public phone line — so the receptionist can book but can't read your books. Tool calls are never billed.
$15 a month, and it isn't just this app — every Parsons product is on the same subscription. Cancel any time. A tool that isn't on the profile isn't there — enforced at the hub, not in a prompt — and a member can be capped in cents per month, with 0 as a hard lock.
Register once. Grant per profile. Paste one address.
Everything's already on it.
Every Parsons product publishes its tools here. Register your own MCP servers — stdio, HTTP, OAuth — and they sit beside them.
Add the Linear MCP server with my token.Paste one link into your AI.
Your account comes with one private address. Paste it into Claude, ChatGPT or Cursor once, and MCP Hub's tools are there. No AI of your own? The console has chat built in.
https://mcp-hub.parsons.ai/p/prof_••••••••/mcpMake a profile for the job.
Admin gets everything. The receptionist gets book, find_free and send_sms. A contractor gets the tracker and nothing else. Each profile is its own private address.
Make a front-desk profile: booking, texting, new contacts. Nothing else.Watch it get used.
Every call, by whom, on which profile. Cap a member in cents a month. Revoke a tool and it's gone from the next call.
What did the front desk profile call today?A hub, not a list of 330 tools.
One gateway per server, unlimited grants
Instead of publishing 330 tool definitions and hoping your client keeps them, the hub publishes one gateway per server. Grants live behind it.
Profiles as boundaries
A profile is a curated tool set with its own address. The public phone line gets the small one. Structurally, not by prompt.
hub__grant_toolfront-desk · calendar_bookgrantedhub__revoke_toolfront-desk · send_emailrevokedGrant and revoke by name
From the console or from chat. The next call sees the change. There is no cache to wait out.
Members, capped in cents
Add a teammate to a profile and cap their spend — AI, metered usage, purchases — in cents per month.
Any client
Claude, ChatGPT, Cursor, VS Code, Claude Code — anything that speaks MCP takes the address.
Tool calls never billed
Recorded, never charged, no monthly allowance — on every account. The hub is the door; we don't charge for opening it.
It hands out tools. It cannot hand out one you didn't grant.
- ×Serve a tool that isn't on the profileThe grants table has no row for it, so the tool isn't in the index the client sees.
- ×Let a member change their own permissionsManagement tools live on a separate admin mount. A managed profile can't be given "change permissions" even by mistake.
- ×Bill a tool callRecorded for visibility. Never metered, never capped.
- ✓Register servers — first-party, external, OAuth
- ✓Create profiles, grant and revoke tools, add members with caps
- ✓Read every call, on every profile
There is no security slogan on this page and no badge we haven't earned. Everything in that list is a thing you can check; the full mechanism and every tool are on the details page.
Fifteen dollars a month — and it isn't just this app.
Is it worth it? Start where we look worst.
If you have one MCP server and one client, you don't need a hub — paste the server in and go. Here's what the hosted MCP gateways publish.
Ours is $15 — and the hub comes with the 21 products it fronts, which is the part the others don't have. And there is no free tier because a hub that meters your tool calls is a hub with a reason to slow you down.