Booking is the easy half. What this adds is the rest of the chain — a contract agreed in advance, check-in and check-out to establish the session happened, evidence recorded against the contract's requirements, then documentation and settlement — so an agent can verify a service was delivered rather than merely scheduled.
The reference MCP server for Servicialo, an open protocol for professional services. It covers the whole chain: finding a compatible organisation, checking availability, booking and confirming, moving the session through its lifecycle, recording delivery evidence, then documenting and charging for it.
- Discovery — registry_search by vertical, location and country, registry_get_organization, registry_manifest, registry_list_verticals, registry_list_regions, registry_list_event_types
- Resolution and trust — resolve_lookup maps an organisation slug to its MCP and REST endpoints, resolve_search across the global resolver, trust_get_score, a2a_get_agent_card for agent-to-agent discovery
- Before booking — services_list returns the public catalogue with prices, durations and modalities; scheduling_check_availability needs no authentication; service_get returns a service's eight dimensions and contract_get the pre-agreed rules
- Booking — clients_get_or_create, scheduling_book, scheduling_confirm, scheduling_reschedule, scheduling_cancel
- Lifecycle and delivery — lifecycle_get_state, lifecycle_transition, delivery_checkin, delivery_checkout, delivery_record_evidence
- Closing — documentation_create writes the service record, then payments_create_sale, payments_record_payment and payments_get_status
- Physical resources — resource_list, resource_get, resource_create, resource_update, resource_delete, resource_get_availability for rooms, chairs and equipment
- Network operations — resolve_register and resolve_update_endpoint for portability, telemetry_heartbeat, and market_list_segments with market_get_benchmark for anonymised cross-network comparison
The npm package @servicialo/mcp-server. Discovery, the public service catalogue and availability checks need no authentication; booking, delivery and payment act against a specific organisation's node. Know what this repository is before you plan around it: the protocol and its reference implementation, not a booking platform — a service business needs a protocol-compatible platform, and Coordinalo is the reference one. Tool descriptions from the booking stage onward are written in Spanish.
One command plus a key — npx -y @servicialo/mcp-server, then supply credentials