Developers

MCP server

Connect Claude — or any MCP client — to your account over Streamable HTTP with an ordinary API key, then just ask: “make a site for Maple Street Bakery from the bakery template”, “add an FAQ to Rosie’s catering page”, “what did people send through Hilltop’s quote form this week?”. Every tool is an API operation — same arguments, same checks — so an assistant can do exactly what its key can and nothing more.

Connect

claude mcp add --transport http website-buddy https://websites.workflowcorp.com/api/mcp \
  --header "Authorization: Bearer $WEBSITEBUDDY_API_KEY"

{
  "mcpServers": {
    "website-buddy": {
      "type": "http",
      "url": "https://websites.workflowcorp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_WEBSITEBUDDY_API_KEY"
      }
    }
  }
}

How it behaves

• tools/list shows only what the key may do: a key with just sites:read sees the read tools; a key with every scope sees all 167.
• Edits change the draft. Nothing is public until publish_site, which refuses (sample_content, with the list) while made-up sample content would go live unless publish_sample_anyway is true. create_siteadds the wholesale fee to your bill. Tools carry read-only and destructive hints so a client can ask before acting — the hints are advice, the key’s scopes are the rule.
• Stateless: POST one JSON-RPC message per request. No session id, no event stream.
• Every write tool takes idempotency_key (required where REST requires the Idempotency-Key header): a new UUID per operation, reused only to retry it. A retried call gets the first answer back, marked websitebuddy/idempotent_replayed in _meta, and nothing happens twice.
• Requests are capped at 256 KiB and results at 192 KiB — ask for fewer rows if a list is too big. Each MCP request counts toward the key’s 60 a minute.
• Two resources: the API reference (Markdown) and the OpenAPI document.