MCP

Clauhub has an MCP (Model Context Protocol) server so an AI assistant can work with your account: what the API offers people, the server offers as tools.

The address

https://clauhub.ai/api/mcp

It is an MCP server over HTTP (streamable HTTP). Add it to your client with the address and nothing else.

How you connect

With OAuth (the usual way). The client tries to connect, gets a 401 and finds where to sign in on its own:

1. It reads /.well-known/oauth-protected-resource/api/mcp, which names Clauhub’s authorization server.
2. It identifies itself, either registering on its own (dynamic client registration) or with a client metadata document (its client_id is that document’s https URL).
3. It sends you to sign in to Clauhub and to a consent page that names the app. If you accept, the app gets a token; if you don’t, it stays unconnected.

The flow is OAuth 2.1 with PKCE (S256). The token acts as you, with your permissions.

With an API key. If your client lets you set headers, send your API key as authorization: Bearer ch_...; it works like x-api-key.

The tools

Every procedure a person can call in the API is a tool, named <domain>_<group>_<procedure>; for example, identity_organizations_list answers your organizations. Each tool has a description and its input’s JSON Schema.

Calling a tool is the same API call, made as you: each service decides as it always does. If you lack a permission or the input is invalid, the tool answers an error (isError) with the API’s error, such as PERMISSION_DENIED or BAD_REQUEST.

Client guides

How to add it to each AI assistant, step by step: Coming soon.