Skip to content
backlex Cloud backlex Cloud backlex Cloud
API & automation

MCP server

A Model Context Protocol server lets AI agents operate your organization — list/create projects, read usage, manage keys — over JSON-RPC, authenticated by an API key.

The control plane exposes a Model Context Protocol server so AI agents (Claude, IDEs, custom tooling) can operate your org with the same guardrails as a human.

Endpoint

Section titled “Endpoint”
POST https://cloud.backlex.com/api/mcp

JSON-RPC 2.0 over Streamable HTTP (stateless). Authenticate with a Bearer API key; the key’s organization scopes every call.

Terminal window
curl https://cloud.backlex.com/api/mcp \
  -H "Authorization: Bearer pak_..." \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

Section titled “Tools”

Tools cover the operational surface: projects (list/get/create/provision_retry/pause/resume), deploys, usage, members, API keys, audit, domains, alarms, branches, backups, billing.checkout, integrations, webhooks, and sso.

  • resources/list exposes org and project context as MCP resources.
  • prompts/list ships starter prompts: diagnose_project, usage_report, provision_project.

Scopes & read-only safety

Section titled “Scopes & read-only safety”

The key’s scope is enforced on every tool call:

  • A read-only key can call read tools only — every write tool (anything that mutates) is blocked.
  • An mcpTools allowlist on the key further restricts which tools it may call.