MCP Server

The Business Dash MCP (Model Context Protocol) server lets AI coding assistants — Claude, Cursor, ChatGPT, Goose, VSCode, and others — interact with your organization's data directly. The assistant can read your business profile, browse your catalog, search services, check your booking link, and even submit quote requests, all through structured tool calls.

How It Works

Each organization's published site hosts its own MCP endpoint at /.well-known/mcp.json. AI clients that support MCP discovery find it automatically when pointed at your site URL.

The server implements the Streamable HTTP Transport specification (JSON-RPC 2.0 over HTTP POST).

Before the MCP endpoint responds, the organization must opt in by enabling the MCP App feature in the dashboard settings.

Enabling MCP

1. Go to Settings → AI & Integrations in the organization dashboard
2. Toggle MCP App to enabled
3. Optionally configure which write tools are allowed (see below)

Once enabled, the MCP endpoint is live at your published site's URL:

https://<your-site>.biab.app/.well-known/mcp.json

Or on your custom domain:

https://<your-domain>/.well-known/mcp.json

Connecting an AI Assistant

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "biab": {
      "type": "streamable-http",
      "url": "https://<your-site>.biab.app/api/mcp"
    }
  }
}

Claude Code / Cursor / VSCode

No dedicated config needed — these clients auto-discover MCP via the .well-known/mcp.json endpoint when pointed at your site URL. Just give your assistant the site URL and it will find the tools.

Goose

Use the Streamable HTTP transport type:

# In your Goose session config
mcp_servers:
  biab:
    type: streamable-http
    url: https://<your-site>.biab.app/api/mcp

Available Tools

Read Tools (always on)

Write Tools (disabled by default)

Write tools are gated per-tool. Enable them in Settings → AI & Integrations → MCP App Tools.

Write Tool Configuration

Write tools are individually gated through mcp_app_tools_config. To enable a write tool:

1. Navigate to Settings → AI & Integrations → MCP App
2. Toggle the specific write tool you want to allow
3. Changes take effect immediately — no restart needed

An AI assistant calling a disabled write tool receives:

{ "ok": false, "error": "tool_disabled" }

This gives you fine-grained control. For example, you might allow update_company_profile for onboarding assistance while keeping blog image generation off.

Tool Examples

Get business info

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_business_info"
  }
}

Search catalog

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "search_catalog",
    "arguments": {
      "q": "water heater"
    }
  }
}

Submit a quote request

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "request_quote",
    "arguments": {
      "name": "Jane Smith",
      "email": "jane@example.com",
      "phone": "555-0123",
      "message": "Looking to install a tankless water heater"
    }
  }
}

Protocol Details

• Transport: Streamable HTTP (JSON-RPC 2.0)
• Endpoint: https://<your-site>/api/mcp
• Discovery: https://<your-site>/.well-known/mcp.json
• Methods supported: initialize, tools/list, tools/call, resources/list, resources/read, ping
• Auth: Phase 2 (planned) — currently gated by organization opt-in + hostname resolution

Security

• The MCP endpoint only responds for organizations that have explicitly enabled the feature
• Requests are resolved per-hostname — only your published site's domain can reach your MCP endpoint
• Write tools are individually gated and disabled by default
• Every write action is logged with an audit trail (source, timestamp, changed fields)
• No authentication token is required in Phase 1 — security relies on hostname resolution and the opt-in gate