Skip to main content
Version: 1.0

MCP server

The Hub Chatt2.me documentation is available through a public MCP (Model Context Protocol) server:

https://docs.chatt2.me/mcp

It requires no API key and exposes only the documentation published at docs.chatt2.me.

Available tools​

Search the documentation before fetching a page.

{"query":"webhook signature","limit":10}

query is required. limit is optional and accepts values from 1 to 20.

docs_fetch​

Fetch the complete Markdown content of a page returned by docs_search.

{"url":"https://docs.chatt2.me/docs/latest/authentication"}

Connect an MCP client​

Claude Code​

claude mcp add --transport http hub-chatt2me-docs https://docs.chatt2.me/mcp

Cursor and VS Code​

Add the server to your MCP configuration:

{
"mcpServers": {
"hub-chatt2me-docs": {
"url": "https://docs.chatt2.me/mcp"
}
}
}

Test the endpoint​

List the tools with JSON-RPC:

curl -X POST https://docs.chatt2.me/mcp \
-H 'Accept: application/json, text/event-stream' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Search for a topic:

curl -X POST https://docs.chatt2.me/mcp \
-H 'Accept: application/json, text/event-stream' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"docs_search","arguments":{"query":"authentication"}}}'

Operational Hub MCP​

For browser OAuth, team contexts, application/key preparation and human approval, see Hub MCP actions. This public documentation server remains account-free and cannot approve business operations.

WhatsApp insights and purchases​

The operational tools hub_get_whatsapp_template_analytics, hub_compare_whatsapp_templates and hub_push_whatsapp_purchase_conversion use authorized organization/application/channel contexts. The first two read shared cached metrics; Purchase requires browser confirmation and a stable business idempotency key. The documentation MCP can search and fetch the insights guide and purchase guide; it cannot submit events.

hub_get_whatsapp_templates returns lastUsedDate for each template: an ISO 8601 UTC timestamp of the latest locally recorded provider acceptance of a send through Hub, or null when no usage is recorded. Acceptance does not guarantee delivery. Existing history is not backfilled; Sandbox returns null. This date is independent of template edits.

Example of item metadata: {"elementName":"welcome","lastUsedDate":"2026-11-13T12:30:00.000Z"} or {"elementName":"reminder","lastUsedDate":null}.