Cloudflare brings Access-style identity and edge hosting for remote HTTP MCP. Toolport is local-first: one governed server set for the team, secrets on each machine, policy enforced in the gateway your agents already talk to. This page only claims what ships. Roadmap and non-goals are labeled.
This is cooperative enforcement, not a cloud proxy sitting on every call. A member who is not running Toolport is outside org policy. That is the trade for local-first, secretless control, and full support for stdio MCP servers.
Cloudflare column is public portal positioning (Access, edge, remote HTTP). Toolport column is what is live on main as of the P1 gap close (policy, caps, webhooks, audit export, TOTP).
| Topic | Cloudflare MCP portals | Toolport |
|---|---|---|
| Where it runs | Remote HTTP MCP at the Cloudflare edge | Local gateway on each machine (stdio + HTTP bridge), plus hosted or self-host Teams control plane |
| Secrets | Platform / org patterns | No org secret vault. Keys stay in each member's OS keychain |
| Shared server catalog | Portal config | Teams config sync with version history (Team+) |
| Who can use which server | Portal access controls | Per-server member and group grants (Team+ to edit) |
| Per-tool allow / deny | Portal tool policy | Org allow-lists and deny-lists enforced in the local gateway (Team+) |
| Safety policy | Platform controls | Destructive block, human approval, quarantine, content defense; org can only tighten |
| Proof policy applied | Inline path = enforced at edge | Apply receipts + coverage for instructions and screening policy (cooperative, with timestamps) |
| Runaway tool-call protection | Spend / identity budgets (model and platform) | Hard tool-call rate limits (day/month, member/tool axes) in the gateway (Team+); 80% webhook warn |
| Spend budgets | Dollar limits with block at model layer | Monthly estimated-cost budget with admin email alert (Team+). Not a model-meter hard block |
| Audit trail | Analytics + Logpush-style export | Usage and events CSV; Free 14-day floor; opt-in per-call export (tool, time, duration, ok, args hash; never args or results) |
| Webhooks / alerts | Platform notifications | HMAC-signed webhooks, retries, all or security filter; Free includes one security channel |
| Dashboard sign-in | Cloudflare Access (any IdP, MFA, device posture) | GitHub / Google OAuth, magic link, and TOTP 2FA |
| SSO (SAML / OIDC) + SCIM | Yes via Access / IdP | Roadmap (Enterprise). Contact for scoping Roadmap |
| Device posture | Yes (Cloudflare One) | Not a product lane (local-first) N/A by design |
| Self-host control plane | Different product shape | Yes: Docker image on your network |
No. Org policy is authored in Teams and enforced by each member's local Toolport gateway. A machine that is offline or not running Toolport is outside that policy. Apply receipts show what each client reported as enforced, with timestamps.
On each member's machine, in the OS keychain. The Teams server stores the shared server set and non-secret policy, not secrets.
Yes for tool-call rate limits on Team: day and month caps by team, member, group, or tool, enforced in the gateway. Monthly spend budgets alert admins on estimated MCP tool spend; they do not block cloud model billing.
Dashboard sign-in today is OAuth, magic link, and TOTP 2FA. SAML/OIDC and SCIM are Enterprise roadmap, scoped with you before you commit, not self-serve checkboxes today.
On Team, you can mint an API token that pulls the full shared server config for deploy or CI. It is a full-config credential today, not a per-server or read-only token. Use it like a deploy key, and rotate it if it leaks.
Free for up to 5 people. Team adds access control, per-tool policy, rate limits, signed webhooks, full audit history, and more.
Related: Security model · Pricing · Source