Book any ManyMore business from your agent

Endpoint

POST https://manymore.ca/slotsmith/api/mcp

• Protocol: Model Context Protocol over streamable HTTP, protocol version 2025-06-18, plain JSON-RPC 2.0 bodies. Responses are always JSON (no server-sent events), whatever the Accept header says. Methods: initialize (answers with an Mcp-Session-Id; the server is stateless and accepts any session id back), notifications/initialized, ping, tools/list, tools/call. Every tool carries annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) and an outputSchema; every result comes back as both text and structuredContent, with ok: false + error + message on failure.
• Authentication:none required. Reads are public business information; writes carry the customer's own details and are gated by them (a booking is only ever shown to a caller holding its confirmation code and the phone number it was made with). Partners can send Authorization: Bearer <partner key> for higher limits; an unknown key is a 401. Keys: hello@manymore.ca.
• Attribution: send X-ManyMore-Agent: muse (or dots, or your product's name). It is recorded on every booking and message, so businesses see which assistant sent the job. With a partner key the partner name is the default.
• Limits and region: 60 requests a minute per IP (burst 30) without a key; 600 a minute with one. Businesses in Canada and the US.

Tools

Example

curl -X POST https://manymore.ca/slotsmith/api/mcp \
  -H "content-type: application/json" -H "X-ManyMore-Agent: my-agent" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"find_pros","arguments":{"trade":"appliance repair","near":"Kingston, Ontario"}}}'

# then, with a slug and serviceId from the result:
curl -X POST https://manymore.ca/slotsmith/api/mcp \
  -H "content-type: application/json" -H "X-ManyMore-Agent: my-agent" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"get_availability","arguments":{"slug":"northside-demo","serviceId":"<id>"}}}'

# book a slot (the demo business confirms on the spot):
curl -X POST https://manymore.ca/slotsmith/api/mcp \
  -H "content-type: application/json" -H "X-ManyMore-Agent: my-agent" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call",
       "params":{"name":"request_booking","arguments":{"slug":"northside-demo","serviceId":"<id>",
         "startISO":"<a slot>","customerName":"Pat Test","customerPhone":"+16135550199",
         "customerEmail":"pat@example.com","address":"12 King St, Kingston","problem":"Washer won't drain"}}}'

# later: {"name":"get_booking_status","arguments":{"confirmationCode":"<code>","customerPhone":"+16135550199"}}

For testing, use the demo business northside-demo (Northside Appliance Repair, a fictional business in Kingston). Its requests are confirmed automatically and cleared nightly, so nobody is dispatched. Requests to real businesses reach a real owner.

Guarantees

• Availability comes from the business's own calendar, the same source its booking page uses. An agent is never offered a slot a person couldn't book.
• Every write goes through the same engine as every other channel: idempotent, no double-booking, notice and buffer rules enforced, the same reschedule and cancel paths the customer's own link uses.
• On businesses that screen requests, the owner accepts or declines. An agent cannot force a confirmed job onto anyone's calendar.
• No tool returns another customer's information. A booking is shown only to a caller holding both its confirmation code and the phone number it was made with — the same trust as the customer's texted link.
• Every agent booking and message is recorded with its source and the agent's name, so businesses can see which assistant sent what.
• A business that has paused new requests answers with a clear message instead of taking the booking.