Skip to main content
Bily MCP lets compatible AI clients discover and run supported Bily operations within your access boundaries. The public Streamable HTTP endpoint exposes two tools:
  • search finds the right operation in the current Bily catalog.
  • execute runs an async function with the selected bily.* helper.
The catalog currently contains 64 operations. They cover identity, stores, metrics, analytics, breakdowns, connected-platform reads, and supported writes. Use search as the source of truth. The catalog can grow without adding another top-level MCP tool.

Move from intent to a scoped result

  1. Your client connects to https://api-dispatcher.bily.ai/mcp.
  2. Bily authenticates the connection and applies organization and store access.
  3. The client calls search with the user’s intent.
  4. search returns matching helpers, inputs, risk guidance, and verification steps.
  5. The client calls execute with a focused async arrow function.
  6. Bily returns the JSON-serializable result and captured logs.
Start a new connection with bily.context(). One read returns the authenticated user, accessible organizations, and each organization’s nested stores.
Bily MCP exposes tools only. It does not publish MCP resources or prompts. Use the documentation resources below for agent-readable guidance.

Choose your next step

Quickstart

Connect a client through Bily Connect and verify both tools.

Client configuration

Configure the endpoint, transport, sign-in flow, or fallback key.

Tools and operations

Review the exact search and execute contracts.

Safety and permissions

Apply scope, approval, verification, and credential safeguards.

Give agents product context

These files help agents find public documentation. They are not authentication URLs or MCP endpoints.

Choose the API or MCP

Compare interactive AI-client work with deterministic server integrations.