MCP server

Connect an AI client (e.g. Claude) straight to your vendor account through the Model Context Protocol server. It uses the same OAuth tokens and scopes as the REST API.

Endpoint

The MCP server speaks Streamable-HTTP at /api/mcp. Authenticate every request with your OAuth access token as a Bearer token.

http

POST /api/mcp HTTP/1.1
Host: brutlers.com
Authorization: Bearer brut_at_...
Content-Type: application/json

Register a client

An MCP client is a regular OAuth app. Register it under Integrations and select the scopes your client needs (e.g. inbox:read for inbox triage).

Client configuration

Add the endpoint and your access token to your AI client's MCP configuration.

json

{
  "mcpServers": {
    "brutlers": {
      "url": "https://brutlers.com/api/mcp",
      "headers": { "Authorization": "Bearer brut_at_..." }
    }
  }
}

Available tools

Each tool enforces its scope. Full descriptions are returned by the server's tools/list call.

Tool	Scope
vendor_orders_list	orders:read
vendor_customers_query	customers:read
vendor_appointments_list	appointments:read
vendor_profile_get	profile:read
vendor_inbox_triage	inbox:read
vendor_stats_ask	orders:read
vendor_orders_create	orders:write
vendor_customers_create	customers:write
vendor_appointments_schedule	appointments:write

Prompt: inbox triage

The vendor_inbox_triage_workflow prompt walks the AI client through reviewing unread conversations and open inquiries and drafting replies.

Notes

Access tokens expire after 1 hour — use the refresh token exactly as with the REST API.
A per-token rate limit applies; too many calls return 429.
A client can only use tools whose scope the token was granted — missing scopes return a scope error.