MCP server

Native Model Context Protocol server. Point any MCP-compatible client at the endpoint and human review becomes a set of tools.

Connect

Native Model Context Protocol server over Streamable HTTP (not legacy SSE). Point any MCP-compatible client at the endpoint and human review becomes a set of tools.

Endpoint: https://mcp.agentfabric.dev

{
  "mcpServers": {
    "agentfabric": {
      "url": "https://mcp.agentfabric.dev",
      "type": "http"
      // Optional: call create_tenant (no auth) to get an API key,
      // then reconnect with it to authenticate other requests:
      // "headers": { "x-api-key": "ak_your_api_key" }
    }
  }
}

Set "type": "http" (or your client’s Streamable HTTP equivalent) so the client does not default to legacy SSE. OpenClaw uses "transport": "streamable-http" in its mcp.servers config instead of mcpServers.

When x-api-key is set on the MCP connection, do not pass api_key in tool arguments — auth is header-only.

MCP tools

Tool Access Purpose
create_tenant none Sign up; returns admin + consumer API keys
reviews consumer+ create, get, list, list_items, cancel, add_reviewer, remind
comments consumer+ list, create, resolve, unresolve, notify
precheck consumer+ get, rerun, override, configure — smart precheck for a review request, plus domain defaults
feedback consumer+ list, get, update — learned reviewer feedback groups
checks consumer+ create, get — standalone quality gate with no review request, reviewers, or email
users admin list, create
api_keys admin list, create — new key value returned once
webhooks admin list, create, deletesigned deliveries

Each authenticated tool is a single object with an operation field. Required fields are validated per operation. Standalone REST checks are available on MCP as checks.

Tool results are the JSON data payload from the corresponding REST endpoint.

MCP tool scopes

Connection Visible tools
No API key Only create_tenant
Consumer key reviews, comments, precheck, feedback, checks
Admin key Consumer tools plus users, api_keys, webhooks. Prefer a consumer key for day-to-day review work.