MCP servers — managed, not scattered.

All Your MCPs,
Centrally Managed.

Bloque brings all your MCP servers into one centralized hub — one endpoint, one API key, accessible across your whole team.

Formerly known as MHaaS.

Apply for Early Access
Bloque mascot

How Bloque Works

Discover, configure, and operate all your MCP servers from a single platform

Add

Add MCP servers from a curated set of pre-configured options, or bring your own via GitHub URL, JSON config, or server URL.

Configure

Manage OAuth tokens, environment variables, and secrets centrally. Each Hub gets its own API key — no credentials exposed to clients.

Operate

Monitor usage per server and tool, rotate credentials, and maintain audit-ready logs. Built-in Playground to test MCP servers with any LLM.

Use Cases

Developer Experience

Stop configuring MCP servers on every developer's machine. Create a shared Hub, add servers once, and distribute a single API key. New team members are productive in minutes.

  • ✓ No local Node.js / runtime setup
  • ✓ Consistent environment across the team
  • ✓ Swap MCP servers without client changes

Security & Compliance

Prevent shadow-IT AI usage. Allowlist only approved MCP servers, centralize OAuth tokens, and know exactly who accessed which external service and when.

  • ✓ Single MCP access point for the org
  • ✓ Per-project scoped API keys
  • ✓ Audit-ready usage logging

Standardized Tool Sets

Build curated MCP Hubs for each team — "Dev Standard", "Customer Support", "HR". New members inherit the full setup instantly by using the shared Hub's API key.

  • ✓ Reusable Hub templates per use case
  • ✓ Faster onboarding across teams
  • ✓ Centralized updates, zero client changes

Watch Bloque in Action

These two short demos show both sides of Bloque: getting MCP servers running quickly, then using them to automate a real business workflow.

Note: these videos were recorded when Bloque was called MHaaS — the product is the same.

Demo Video

MHaaS Demo: Add & Test MCP Servers in Minutes (Part 1)

Walk through the full setup flow: add MCP servers to a Hub, enable them, browse tools, and validate everything in the built-in MCP Playground.

Watch on YouTube

Demo Video

MHaaS Demo Part 2: Automating welcome emails — no code required

See how the configured MCP tools can automate a real workflow in Claude Code: pull new registrants, compare CSVs, send personalized emails, and save the process as a reusable script.

Watch on YouTube

Architecture

Two components work together to deliver a seamless MCP experience

Web App

The management console where you register users, create Hubs, add MCP servers, and issue API keys.

  • →User registration & authentication (email, GitHub, Google)
  • →Hub (project) create / edit / delete
  • →MCP server search, install, and management
  • →API key issuance and rotation per Hub
  • →MCP Playground with ChatGPT / Claude integration
  • →Usage statistics per server and tool

MCP Proxy

The runtime layer that aggregates all Hub servers behind one endpoint. Your AI client only needs to know about the Proxy.

  • →Authenticates via API key issued by the Web App
  • →Exposes all Hub servers as a single MCP endpoint
  • →Runs stdio MCP servers locally in isolated sandboxes (Bubblewrap)
  • →Connects to remote servers via HTTP Streamable / SSE
  • →Deployed on AWS ECS on EC2

Ready to simplify your MCP infrastructure?

Bloque is currently in early access. Apply now to be among the first to experience centralized MCP management.

Apply for Early Access