ReferenceView as Markdown ↗

Connecting Biloh over MCP

In plain terms

This page is for whoever connects your AI assistant to Biloh. Once connected, your assistant can run your business's work for you, and each connection acts on your business only. You approve each assistant app once and can revoke it in Settings. Each business has a daily allowance of calls, which the owner can raise.

Biloh exposes a Model Context Protocol server at /api/mcp/mcp on biloh.com.au, and your tenant's own address serves the same server at the same path. Authenticate with a tenant-scoped Personal Access Token, and any MCP-compatible assistant can drive the tenant's operations end-to-end. MCP is part of the platform, not a paid add-on.

At a glance

Who it's for:
Engineers building on Biloh
What a person approves:
Each connection works on one business only, and cannot reach another.
Checked against the code:
2026-10-30

Biloh exposes a Model Context Protocol (MCP) server so an MCP-compatible AI assistant can run a tenant's operations end-to-end: Claude and Grok; ChatGPT with the core tool list. This page is the reference for connecting.

Where is the endpoint?

The MCP server lives at:

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

Your tenant's own address serves the same server at /api/mcp/mcp. It is a streamable HTTP MCP server implementing the Model Context Protocol. MCP integration is part of the platform, not a paid add-on.

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, independent of the agent: the server fixes the tenant from the token before any tool runs, every query and write gateway is scoped to it, and row-level security in the database is a second wall.

Assistants that sign in for you instead of using a pasted token (Claude's connector library, for example) use OAuth. The first time an app connects to a business, you are shown an Allow screen before any key is issued.

What the Allow screen shows

When an AI app connects to your business over OAuth for the first time, Biloh shows you one screen and waits for your answer:

  • The app's name — the name the app registered with ("Allow Claude to connect?").
  • Where it sends you back to — the web address your answer is returned to. If you do not recognise it, press Deny.
  • Which business — the business the connection will act on, and the account you are signed in as.
  • What it can do, and for how long — everything your account can do in that business, at your role, for 7 days.

Allow connects the app and remembers your approval for that app, so the next sign-in from the same app does not ask again. Deny sends the app an access_denied answer and nothing is saved.

To see or remove approved apps, open Settings → Agent access → Approved AI apps and press Revoke — or ask your assistant to call list_agent_connections and revoke_agent_connection. After a revoke, the next sign-in from that app asks again.

A connection stops working within a minute if the person who approved it is removed from the business, or the business is archived; the assistant is told why (membership_revoked or tenant_archived).

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 an assistant starts are always two-step (propose_send_* then approve_send_*), so nothing it writes leaves the system without an explicit approval.

Are there limits?

Limits: 240 calls a minute per connection; a daily allowance per business, shown by get_my_entitlements.

  • Only tool calls count. Connecting (initialize), listing tools and ping are free.
  • Reads and writes count alike against the daily allowance, which resets at midnight in the business's timezone.
  • A refused call answers HTTP 429 with { "error": "rate_limited", "reason": "token_rate" | "tenant_quota" } and a Retry-After header saying how many seconds to wait.
  • The business owner can raise the daily allowance, or set it to 0 for unlimited, with the setting mcp.quota.calls_per_day — in Settings or through update_setting.

Next steps

Under the hood

Source files this page is checked against:

  • app/api/mcp/[transport]/route.ts
  • lib/mcp/registry.ts
  • lib/mcp/call-quota.ts

Raw markdown: /docs-md/reference/mcp-overview

Last updated 2026-11-11