Coordinalo — Service Business Operations

What Coordinalo — Service Business Operations does

Coordinalo — Service Business Operations exposes Coordinalo’s scheduling platform through the Model Context Protocol. It gives an agent access to operational records and actions for appointment-based services, including available time slots, bookings, clients, providers, services, and organization-level dashboard metrics.

The interface covers the main scheduling lifecycle. An agent can find openings for a provider or service, create an appointment, inspect or filter existing bookings, move an appointment, and cancel it. It can also search or create client records, retrieve active providers, list bookable services, and request summary metrics for an organization.

This is a fit for assistants that need to answer scheduling questions or perform booking operations using Coordinalo data. It is less suited to workflows that require capabilities not represented by the documented tools, such as a dedicated payment or invoice operation.

How it works

The hosted MCP endpoint is https://coordinalo.com/api/mcp. MCP clients send requests to that endpoint, and the server maps the requests to Coordinalo operations. Each tool accepts an orgSlug parameter in the documented interface, while the request also requires the organization identifier in the X-Org-Slug header.

Authentication uses an API key in the Authorization header with the Bearer scheme. The API key is obtained from Coordinalo’s API settings. Rescheduling and cancellation require a confirm value, providing an explicit confirmation step for those changes.

Coordinalo implements the Servicialo open protocol. As a result, clients compatible with that protocol can use the same tool names and parameter conventions, which can help keep agent integrations portable across compatible scheduling platforms.

Setup and configuration

Add a remote MCP server entry for Coordinalo in the client’s MCP configuration. The required connection details are:

• URL: https://coordinalo.com/api/mcp
• Header: Authorization: Bearer <YOUR_API_KEY>
• Header: X-Org-Slug: <your-org-slug>

The README provides configuration examples for Claude Desktop and Cursor, and states that any MCP client can point to the same endpoint. Replace the placeholder API key with a key from Coordinalo and use the slug for the target organization. The supplied material does not document local installation, a command-line launcher, or environment-variable configuration.

Tools and capabilities

The Coordinalo — Service Business Operations MCP server provides these tool groups:

• Availability: availability_get_slots searches free times using date ranges and optional provider or service filters.
• Bookings: booking_create, booking_list, booking_get, booking_reschedule, and booking_cancel create, inspect, filter, move, or cancel sessions.
• Clients: client_list, client_get, and client_create search, retrieve, and add organization clients.
• Catalog and staff: admin_list_providers returns active providers, while service_list returns bookable services.
• Reporting: report_dashboard returns organization summary metrics for a specified date.

Booking creation uses provider, service, client, and scheduled-time information. Listing supports filters such as status, provider, and date range. Client creation accepts a name and last name, with optional email and phone fields.

Limitations and notes

The documented interface is organization-scoped and requires both authentication and an organization slug. The source material lists no tool for modifying provider records, changing services, or performing billing transactions. It also does not specify response schemas beyond directing readers to the full tool documentation.

The repository identifies the implementation as Apache 2.0 licensed and describes the hosted instance as production status. The endpoint is remote, so access depends on a valid Coordinalo account, API key, organization slug, and network connectivity to Coordinalo’s service.