Connecting Biloh over MCP

Biloh exposes a Model Context Protocol server at app.biloh.com.au/api/mcp. Authenticate with a tenant-scoped Personal Access Token, and any MCP-compatible assistant can drive the tenant's operations end-to-end. MCP is included at every tier.

Biloh exposes a Model Context Protocol (MCP) server so any MCP-compatible AI assistant — Claude, ChatGPT, Grok, Perplexity — can run a tenant's operations end-to-end. This page is the reference for connecting.

Where is the endpoint?

The MCP server lives at:

https://app.biloh.com.au/api/mcp

It is a streamable HTTP MCP server implementing the Model Context Protocol. MCP integration is included at every Biloh tier.

How does authentication work?

Requests authenticate with a tenant-scoped Personal Access Token (PAT). The token binds every call to a single tenant, so a connection always acts on exactly one business's data — isolation is enforced server-side by row-level security and write gateways, independent of the agent.

What can an agent do once connected?

Orient first, then act:

  • get_session_context — the read-me-first call: returns the active tenant, your persona, conventions, and live state.
  • search_tools(query) — find the right tool by intent instead of scanning the full catalogue.
  • Composite tools like onboard_client_for_service set up a client, site, and pricing in one call.

Sends are always two-step (propose_send_* then approve_send_*) so nothing leaves the system without an explicit approval.

Next steps

Last updated 2026-06-25