Skip to main content

Automation

Bloque's single MCP endpoint makes it straightforward to run MCP-powered automation from scripts, CI/CD pipelines, or scheduled jobs.

How it works​

Any tool or script that supports the MCP HTTP transport can connect to Bloque using your API key as a Bearer token. Once connected, it has access to all the MCP servers configured in your Workspace — no per-server installation or credential management needed on the client side.

Example: CI/CD pipeline​

Add a Bloque-aware step to your pipeline that calls MCP tools via the HTTP endpoint:

MCP endpoint: <shown in Setup Guide>
Authorization: Bearer <api-key>

Because all credentials are managed in Bloque, the pipeline only needs the single API key stored as a secret in your CI environment.

Example: Scheduled script​

A scheduled script can use any MCP SDK to connect to the Bloque endpoint and invoke tools — for example, reading data from a database MCP server and posting a summary to Slack via the Slack MCP server, all through one connection.

Key benefits for automation​

  • Single credential — one API key for all MCP servers
  • Centralized config — update server configuration in Bloque; scripts pick it up automatically on the next connection
  • Logs — every tool call is logged on the Logs page, giving you an audit trail without additional instrumentation