Concepts
This page explains the terms used throughout the Bloque documentation.
Hub
A Hub is your top-level project in Bloque. It has:
- A unique MCP endpoint URL
- One or more API keys
- A set of MCP server configurations
- Isolated, encrypted credential storage (AES-256-GCM)
Think of a Hub as a project or team boundary — you might have one Hub for personal use and another for a work project. Free accounts have 1 Hub; Starter has 3; Pro has 10.
MCP Server
An MCP Server is a configured entry for a server that implements the Model Context Protocol. Each entry records the transport type and connection details:
| Transport | Description |
|---|---|
stdio | Local process launched by a command and arguments |
HTTP | Remote server reachable via a Streamable HTTP URL |
SSE | Remote server reachable via a Server-Sent Events URL (deprecated — prefer HTTP) |
MCP servers are added to a Hub. The number of servers per Hub is limited by plan (10 / 20 / 30 for Free / Starter / Pro).
MCP Router
The MCP Router is Bloque's control-plane front door. When your AI client connects to the Bloque MCP endpoint, the Router:
- Validates your API key
- Applies sticky-session routing to keep a client session on the same runner
- Forwards the connection to the MCP Proxy
You never interact with the Router directly; it is transparent to your MCP client.
MCP Proxy / Runner
The MCP Proxy (also called the runner) executes the actual MCP server processes for your Hub. It handles:
- Launching stdio processes
- Connecting to remote SSE and HTTP servers
- Injecting credentials and environment variables (decrypted at runtime)
- Proxying OAuth token refreshes
Free and Starter plans use a shared runner pool. Pro plans will use a dedicated runner (coming soon).
API Key
An API key is a bearer token you generate in Bloque and pass to your MCP client. The key identifies which Hub the client should connect to. You can create multiple API keys per Hub and revoke them individually.
MCP Endpoint
The MCP endpoint is the URL your AI client connects to. The exact URL is shown in the Setup Guide page inside the Bloque app. Pair it with an API key as a Bearer token to authenticate.