Why Bloque

One control plane for every MCP server you run.

Protocol differences, scattered credentials, and zero visibility are the hidden tax of scaling with MCP. Bloque eliminates all three without touching your clients.

1

Fragmentation, solved

Every MCP server speaks a different protocol, auth scheme, and deployment model. Bloque normalises them behind one control plane so your clients never need to care.

2

Secrets, isolated

Each project has its own API keys — issue multiple, revoke any one independently. All keys are encrypted at rest.

3

Visibility, built in

See which tools were called, when, and by which AI agent — without adding instrumentation.

Demo

See Bloque in action.

Two short videos covering setup and a real automation use case end to end.

These demos were recorded before the rename to Bloque, so you may see or hear the former name, MHaaS, in the videos.

Part 1: Add & Test MCP Servers

Walk through the complete setup flow — adding MCP servers to your Hub, enabling them, and verifying tools live in the MCP Playground.

Part 2: Automate a Real Workflow

Use the four MCP servers configured in Part 1 to automate sending thank-you emails to new registrants — no programming required.

Get Started
How it works

Connect → Configure → Monitor

Wire up every MCP server once, expose a single endpoint everywhere, and keep security + observability tight without more bespoke scripts.

1

Add MCP servers

Install from the Bloque catalog or point to a GitHub repo. Authenticate via OAuth2 or PATs when needed.

2

Test in Playground

Validate how tools work together using the built-in MCP Playground before rolling to production.

3

Connect any AI client

Generate a Bloque API key, set the unified endpoint in tools like n8n or Activepieces, and run the workflow.

Dataflow
Bloque Dataflow Architecture

Start Free, Scale When Ready

Choose the plan that fits your needs. Upgrade or downgrade at any time.

Free

Get started with MCP server management at no cost.

$0forever
  • 1 Hub(s)
  • 10 MCP Servers per Hub
  • Shared Runner
Most Popular
Starter

For developers who need more power and playground access.

$5/month
  • 3 Hub(s)
  • 20 MCP Servers per Hub
  • MCP Playground
  • Shared Runner
Pro

For power users and teams needing maximum capacity.

$30/month
  • 10 Hub(s)
  • 30 MCP Servers per Hub
  • MCP Playground
  • Dedicated Runner (coming soon)

Enterprise

For organizations with advanced needs

Contact Sales
Security

Centralized control over MCP access and execution.

  • Admins choose which MCP servers are available — users get only what's permitted.
  • Local MCP servers run in an isolated runtime per project.
  • OAuth tokens and credentials managed inside Bloque — nothing stored on the client.