# Coordinalo Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Coordinalo

Scheduling, clients, billing and CRM for appointment-based service businesses

- Record: https://musedirectory.ai/connector/coordinalo
- Category: Productivity
- Developer: Coordinalo (https://coordinalo.com/developers)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 2015ms, checked 2026-09-28T08:16:05Z
- Endpoint: https://coordinalo.com/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T01:06:04Z)
- Source: Found in the official MCP Registry (com.coordinalo/mcp-server) https://registry.modelcontextprotocol.io/v0/servers?search=com.coordinalo%2Fmcp-server

Manages bookings, provider availability, client records, and billing for service businesses. Handles recurring appointments, payment tracking, cancellation policies, and financial reporting. Requires API key and organization setup.

Example request: "Show me my pending payments and reschedule requests from clients this week"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Coordinalo to help me. It is a free service with an MCP server at https://coordinalo.com/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- dunning_get_config: Get the current dunning (payment recovery) configuration for an organization. Returns whether dunning is enabled, grace period, step timings, and blocking settings.
- dunning_configure: Update dunning (payment recovery) configuration for an organization. All fields except organizationSlug are optional — only provided fields are updated, rest stays unchanged.
- admin_list_providers: List active providers (professionals) for an organization. Use this to get providerId before calling admin_set_availability. The org owner is auto-provisioned as a provider. Requires X-Org-Api-Key header.
- admin_create_service: Add a bookable service to an organization. Use after admin_create_organization. Auto-discoverable by default. If the org has exactly one active provider, the service is auto-assigned to them. With multiple providers, use service_assign_provider to assign manually — unassigned ser
- admin_set_availability: Replace the weekly availability schedule for a provider (not additive — overwrites all existing blocks). Get providerId from admin_list_providers first. Schedule uses day names and HH:MM times. Requires X-Org-Api-Key header.
- admin_toggle_discoverable: Toggle the LIFECYCLE flags isPublic and servicialoPublished. ⚠️ This tool does NOT grant public discovery consent — discovery in the Servicialo registry requires Organization.discoveryConsent=true, which can ONLY be set by the human owner via PATCH /api/organizations/:slug/servic
- availability_get_slots: Query available time slots within a date range. Agenda-aware: without clientId, filters by the org default public agenda — each org decides which services to expose. With clientId, resolves the client titular provider and returns their full service catalog. Five modes: (1) orgSlu
- availability_get_provider_schedule: Get the configured weekly availability schedule for a provider (not free slots, but the base configuration). Use admin_set_availability to modify.
- booking_create: Create a new session/appointment for a client. providerId is optional — if omitted, the system auto-assigns a provider using the agenda assignment strategy (round_robin, least_booked, etc.). When a client has a titular provider, that provider is preferred automatically. Without p
- booking_get: Get complete details of a session/appointment by its ID, including client, provider, service, financial, and delivery proof information.
- booking_list: List sessions for an organization with filters by provider, client, service, status, and date range. Supports cursor-based pagination.
- booking_cancel: Cancel an existing session. By default applies the org cancellation policy: the charge is computed from the no-charge/partial/full windows and, if the policy has autoApply, registered as a penalty transaction (money-write). Set applyCancellationPolicy: false to waive the charge. 
- booking_reschedule: Reschedule a session to a new time. Cancels the original and creates a new one. Requires confirm: true.
- booking_update_status: Advance a session through the Servicialo lifecycle: confirm, start, complete, or mark as no-show. NOTE: the "deliver" action is NOT available via MCP (ref PDC-SEC-001) — MCP authentication cannot validate actor-as-Proveedor. Delivery must be performed via the REST endpoint PATCH 
- booking_create_recurring: Create recurring sessions (e.g. weekly therapy). Generates multiple individual sessions linked by a recurrence series ID. Max 52 occurrences.
- booking_list_requests: List the reschedule requests (SessionRequest) of an organization — the org side of the bilateral coordination loop a client opens from the portal. Filter by status (pending|all|resolved, default pending), sessionId or clientId. Returns the proposed slot, current session state, an
- booking_resolve_request: Approve or reject a pending reschedule request (SessionRequest) that a client proposed from the portal — closes the bilateral coordination loop. outcome: "approved" applies the reschedule atomically (moves the session to the proposed slot in the same transaction); "rejected" requ
- client_list: List clients of an organization with search and pagination. Can filter by provider or outstanding debt.
- client_get: Get complete details of a client including financial summary and recent sessions.
- client_create: Create a new client in the organization. If a Person with the same email exists, it will be linked (not duplicated).
- client_update: Update an existing client's personal data. Email cannot be changed via MCP.
- service_create: Create a new bookable service in an existing organization. Use this for day-to-day service management (requires X-Org-Api-Key). For initial org setup, prefer admin_create_service instead. After creating, use service_assign_provider to link providers. A service without providers c
- service_list: List services of an organization. Can filter by active status, discoverability, or category.
- service_update: Update an existing service (price, duration, status, etc.). Creates a price history entry if price changes. Delivery-verification overrides can be changed too: verificationLevel (none / default_confirm / dual_confirm / documented — see service_create for semantics) and qualityCap
- service_assign_provider: Assign or unassign a provider to/from a service. Controls which providers can deliver which services.
- provider_get: Get complete details of a provider including services, schedule, and session stats.
- provider_create: Create a new provider in the organization. Links or creates a Person record by email.
- provider_update: Update provider data: status, commission, coverage areas, permissions.
- provider_get_stats: Get detailed performance metrics for a provider over a date range: sessions, occupancy, no-show rate, revenue.
- finance_list_cobros: List charges (cobros) for an organization. Filter by client, status, or date range. Includes summary totals.
- finance_get_cobro: Get details of a specific charge (cobro) including all associated payments.
- finance_register_payment: Register a manual payment against an existing charge (cobro). Updates cobro status automatically. Requires confirm: true.
- finance_client_balance: Get the complete financial balance for a client: total sales, charges, payments, pending debt, and credits.
- finance_list_payments: List payments received with filters. Includes summary by payment type.
- finance_list_ventas: List sales (ventas) for an organization. Filter by client, service, provider, or status.
- finance_create_venta: Create a service sale (venta) for a client. Optionally auto-creates a charge (cobro) depending on org configuration. Requires confirm: true.
- finance_create_cobro: Create a manual charge (cobro) for a client. Not linked to a sale/venta. Requires confirm: true.
- finance_aging: Get accounts receivable aging report: pending charges grouped by age buckets (0-7, 7-30, 30-90, 90+ days). Use to answer "who owes money" or "old debts" questions.
- finance_list_confirmations: List pending charge confirmations and their status. Shows cobros in pending_confirmation state that await client verification. Filter by client or confirmation status (pending, confirmed, disputed, auto_confirmed).
- finance_send_confirmations: Send pending confirmation digest to clients. Groups all pending_confirmation charges by client and sends a single message per client via WhatsApp or email. Creates confirmation tokens and sets a grace period for auto-confirmation. Requires confirm: true.

Screening checks:
- MCP handshake: pass (Answered in 1793ms)
- Domain against threat feeds (Cloudflare security DNS): pass (coordinalo.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (112 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 1313 days ago)
- AI review of purpose and tool behavior: pass (No concerns)