---
title: MCP connections
description: Choose the public documentation server or the authenticated transaction server for your task.
---

| Server                          | URL                           | Access        | Purpose                                                                                 |
| ------------------------------- | ----------------------------- | ------------- | --------------------------------------------------------------------------------------- |
| Blume documentation MCP         | https://agentsub.dev/docs-mcp | Public        | Search and read documentation                                                           |
| Human and agent transaction MCP | https://api.agentsub.dev/mcp  | Authenticated | Identity, balances, offers, voucher/payment requests and merchant account access checks |

The gateway uses the official MCP TypeScript SDK v2 and shares operations with the CLI. Tool results report HTTP-equivalent status, approval requirements and structured data. Protected operations require the configured identity, permissions and provider.

## Protocol revision

The public Blume documentation server currently supports **2025-11-25** and exposes four read-only tools: search_docs, get_page, list_pages and get_navigation. It uses that revision’s initialization and transport lifecycle. The transaction gateway uses its separately configured SDK protocol support.

The official latest specification resolves to **2026-07-28**. It defines a stateless request model, per-request version/capability metadata and HTTP method/name routing headers. A successful request carrying a newer version does not establish full compliance with that revision; use each server’s negotiated supported version. [Official release](https://blog.modelcontextprotocol.io/posts/2026-07-28/) and [specification](https://modelcontextprotocol.io/specification/2026-07-28).

## Authorization

Use [the OAuth guide](/fr/docs/oauth) for protected gateway connections. Human clients sign in through Clerk/Google and explicitly consent to owner scope; agents authorize through AgentID for agent scope. The requesting client must complete S256 code exchange for a resource-bound gateway access token. A discovery document or an available Bearer-token endpoint does not by itself prove an end-to-end MCP OAuth connection. Successful callback, token exchange and resource-audience validation must all be verified.

[Public documentation discovery](/fr/docs/discovery) · [stdio CLI adapter](/fr/docs/cli).