Skip to content
Kuro Agentby Kurogrid

Websites assistants can safely use

The clinic website your agent can act on, with a human in charge.

Kuro Agent turns Mimo Veterinary Care, a fictional vet clinic, into a WebMCP capability surface. Customers approve every booking before it is sent, and the Owner reviews and applies one exact availability plan at a time. Live at webmcp.kurogrid.com.

Run the full demoTalk to Mimo, live customer demo
  • Live availability
  • Customer approval first
  • One exact plan
  • Full audit trail
Mimo Veterinary CareCustomer agent
Customer requestClinic response
Appointment / LunaLive times available

Find Luna's next dermatology visit.

Mimo publishes its current dermatology availability. The agent prepares the exact request, but only the customer can send it. The same slots work in the traditional booking form.

Prepared for customer reviewDermatology · Selected openingNothing sent yet
Agent capabilities on this page
find_appointment_slotsprepare_appointment_requestconfirm_appointment_request

One complete appointment

From a question to a confirmed visit.

WebMCP lets an assistant discover and use the actions published by the website, without bypassing the customer or the clinic. Three parties stay in control: the customer, the Owner, and the published page they both see.

  1. 01

    Customer books

    Talk to Mimo on /sites/mimo-01

    The assistant reads live services and slots, prepares the exact request, and stops. The customer reviews service, time, pet, and email before anything reaches the clinic. No agent on hand? The TraditionalBooking form books the same slots without WebMCP.

    • find_appointment_slots
    • prepare_appointment_request
    • confirm_appointment_request

  2. 02

    Owner reconciles

    Availability control room at /app/[slug]

    The Owner describes schedule intent once. The agent combines it with normalized busy intervals — never credentials, titles, attendees, or notes — and Mimo derives slots, conflicts, and held alternatives. Luna gets a proposed alternative while Max stays preserved. One exact plan applies under a one-shot approval; stale or conflicting plans fail closed with an audit record.

    • prepare_availability_plan
    • apply_availability_plan

  3. 03

    Parity holds

    One published truth

    The public page and its WebMCP tools resolve the same immutable publication version: same services, slots, holds, and appointment state. Tools register through document.modelContext and refresh when auth, role, organization, or resource state changes; stale registrations abort.

    • get_site_content
    • get_appointment_status

Built into the page

The website becomes a working interface.

Luna books dermatology on Saturday morning while Max's booking stays untouched. The Owner applies the reconciled plan from the control room, the customer accepts the held alternative, and the confirmation lands by email with a Calendar handoff.

Clinic responseConfirmed
Luna · DermatologyConfirmed time
  • Email update sent
  • Ready for Calendar

Capability surface · 21 tools

Every tool the site publishes. Nothing else.

Tools register through document.modelContext and execute server-side against the current session, tenant, role, and resource state. Registration is not authorization: every call is re-resolved, and consequential actions consume one-shot approvals with audit records.

Availability · Owner control room

Manual review, external-agent prompt, and WebMCP inspector over one exact plan.

  • get_availability_configuration
  • prepare_availability_plan
  • apply_availability_plan
  • apply_approved_availability_plan

Appointments · Customer

Prepare first, send only on customer approval; the clinic accepts or proposes another time.

  • get_clinic_services
  • get_opening_hours
  • find_appointment_slots
  • prepare_appointment_request
  • confirm_appointment_request
  • get_appointment_status
  • respond_to_appointment_proposal
  • get_appointment_calendar_event

Attention and content operations

Secondary demonstration: signals, drafts, publication versions, and rollback.

  • get_attention
  • create_action_plan
  • acknowledge_lead_attention
  • get_site_content
  • create_or_patch_site_draft
  • preview_publish_consequences
  • publish_site_draft
  • list_site_versions
  • rollback_site_version

Tool names match src/features/webmcp/contracts.ts exactly. Inspect them live in the Owner control room's WebMCP inspector or the parity simulator at /demo/simulator.

Try it live

Three doors into the same clinic.

Customer · /sites/mimo-01

Talk to Mimo

Ask for Luna's dermatology visit on Saturday morning. The assistant finds live slots and prepares the request for your review.

Open the customer demo

Owner · /demo → /app/[slug]

Availability control room

Claim a resettable sandbox, prepare September availability with your agent, and apply one exact plan under Owner approval.

Claim a demo workspace

Both · /demo/simulator

Parity simulator

Customer booking on the left, Owner copilot on the right, one shared truth in the middle — with a live WebMCP inspector.

Open the simulator

One fictional clinic. One real agent interaction.

Ask Mimo for Luna's next visit.

Try it on MimoRun the full demo