What is Bloque?
Hosted MCP gateway with team Hubs, shared servers, per-member keys and paid Playground Bloque review: one MCP gateway, with beta limits worth reading By Ashley Richmond.
Why we recommend it
Bloque is a focused hosted MCP gateway for technically led small teams tired of maintaining connector configs on every laptop. Hub keys, central server setup and paid Playground deserve a low-risk pilot. Current beta shares upstream identity, and uploaded workspace files are not encrypted at rest; it is not personal-account isolation or audited enterprise security. Desk research only, no live connection test.
Best for
- Technically led small teams with shared MCP business resources and a low-risk pilot; developers who can vet packages and OAuth scopes.
Key features
Documented tenant-aware Streamable HTTP endpoint and Hub keys route clients to centrally configured servers. SSE deprecated; no connectivity…
npx/pipx stdio runners and remote HTTP supported. Shared or paid dedicated runner; Docker-in-Docker and arbitrary local installs unsupported.
Add repository/package URL, MCP JSON or manual server; discover tools. Registry quantity vendor claim, not certification of community…
DCR where supported; Slack/GitHub require own OAuth apps. Recoverable secrets AES256GCM/KMS, platform keys one-way HMACSHA256 vendor policy.
Team central billing/admin and per-member keys/logs. Beta shared upstream identity; per-user OAuth roadmap, not delivered guarantee.
Pros
- Focused hosted gateway with clear transport/setup documentation
- Published credential handling and explicit plaintext-file limitation
- Low public entry pricing with free Hub and annual totals
- Official demo shows genuine server setup and Playground UI
Cons
- Paid beta shares upstream identity; per-user OAuth remains roadmap
- Uploaded workspace raw files are not encrypted at rest
- Client plan/Playground/dedicated-runner wording has source conflicts
- No operational deployment security audit uptime or offboarding test