Mcp

Servicialo MCP Server

Open protocol for booking and scheduling professional services via AI agents

Verified: 2026-05-13 (mcp-registry-ingest-2026-05-13+enrich-capability-skill)

When to use Servicialo MCP Server

Choose if

You're inside an agent session and need to actually book, reschedule, or record evidence for an in-person professional service — and the user is on (or willing to onboard to) a Servicialo-compatible platform like Coordinalo. The 34 tools across 6 phases (Resolver, Descubrir, Entender, Comprometer, Gestionar, Verificar, Cerrar) cover the full booking lifecycle with GPS / photo / signature evidence capture that generic calendar MCPs don't have.

Avoid if

The user isn't on a Servicialo-compatible platform — without an API key and org ID from a backing platform, only basic discovery works. Also avoid if you only need calendar slot management (Google Calendar / Calendly MCPs are simpler) or if your flow depends on the Finanzas / Disputas extensions, which are still in design and may break.

Risk Flags

  • MEDIUM scope Protocol v0.9 is marked stable only for the Core surface. The Finanzas and Disputas extensions are explicitly "en diseño" (in design) and the webhook spec is still "borrador" (draft). Agents that need payment or dispute flows may hit unimplemented behavior.
  • MEDIUM auth Full functionality requires `SERVICIALO_API_KEY` + `SERVICIALO_ORG_ID` provisioned by a Servicialo-compatible platform (Coordinalo by default). Discovery works unauthenticated, but booking, evidence capture, and payments need org-issued credentials.
  • LOW maturity Single-vendor backing today (Coordinalo). The "open protocol" framing assumes other compatible platforms emerge; until they do, this is a thin client to one HTTP API.

Cost

Type: Unknown

Distribution

MCP Registry
com.servicialo/mcp-server
Repository
https://github.com/servicialo/servicialo