Coordinalo — Service Business Operations vs Xero MCP Server
A side-by-side look at the Coordinalo — Service Business Operations and Xero MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Coordinalo — Service Business Operations for finance & fintech work over a hosted endpoint; choose Xero MCP Server for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coordinalo — Service Business Operations when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
dunning_get_config, dunning_configure, admin_list_providers.
Choose Xero MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
XERO_CLIENT_ID, XERO_CLIENT_SECRET, XERO_SCOPES, XERO_CLIENT_BEARER_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | XERO_CLIENT_IDXERO_CLIENT_SECRETXERO_SCOPESXERO_CLIENT_BEARER_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 385 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 112 | Not listed |
| Full listing | View Coordinalo — Service Business Operations | View Xero MCP Server |
Tools & capabilities
Coordinalo — Service Business Operations tools 112
dunning_get_configGet the current dunning (payment recovery) configuration for an organization. Returns whether dunning is enabled, grace period, step timings, and blocking settings.dunning_configureUpdate dunning (payment recovery) configuration for an organization. All fields except organizationSlug are optional — only provided fields are updated, rest stays unchanged.admin_list_providersList 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_serviceAdd 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 services block admin_toggle_discoverable. Next step: admin_set_availability to configure the provider schedule. Requires X-Org-Api-Key header.admin_set_availabilityReplace 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_discoverableToggle 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/servicialo from the web panel (a deliberate, authenticated consent action). Without consent, the cron registry-sync and resolver-heartbeat skip the org, so calling this tool with discoverable=true on a non-consented org flips local flags but does not publish anywhere. Requires X-Org-Api-Key header.availability_get_slotsQuery 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) orgSlug only — slots from the public agenda grouped by service, provider auto-assigned at booking; (2) orgSlug + clientId — resolves titular provider if set, falls back to agenda; (3) orgSlug + agendaId — slots for a specific agenda; (4) serviceId — slots for all providers assigned to that service; (5) providerId — slots for a specific provider. Modes 1–3 hide provider details. Use before booking_create.availability_get_provider_scheduleGet the configured weekly availability schedule for a provider (not free slots, but the base configuration). Use admin_set_availability to modify.booking_createCreate 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 providerId and without publicAgendaId, the org default public agenda is used. Preconditions: (1) service must exist and be active, (2) client must exist (use client_create first). Use availability_get_slots to find valid time slots before calling this. Set retroactive: true to register past sessions (skips slot validation, sets status to completed by default). Use autoCharge: true with retroactive to auto-generate the charge. Retroactive sessions are tagged with self_declared provenance. Max 365 days in the past. Past dates are auto-detected as retroactive — the retroactive flag is optional (system infers it from scheduledAt).booking_getGet complete details of a session/appointment by its ID, including client, provider, service, financial, and delivery proof information.booking_listList sessions for an organization with filters by provider, client, service, status, and date range. Supports cursor-based pagination.booking_cancelCancel 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. Requires confirm: true.- +100 more on the listing page
Xero MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Coordinalo — Service Business Operations
{
"mcpServers": {
"coordinalo-service-business-operations-2": {
"url": "https://coordinalo.com/api/mcp"
}
}
}
Xero MCP Server
{
"mcpServers": {
"xeroapi-xero-mcp-server": {
"command": "npx",
"args": [
"-y",
"@xeroapi/xero-mcp-server@latest"
],
"env": {
"XERO_CLIENT_ID": "YOUR_XERO_CLIENT_ID_HERE",
"XERO_CLIENT_SECRET": "YOUR_XERO_CLIENT_SECRET_HERE",
"XERO_SCOPES": "YOUR_XERO_SCOPES_HERE",
"XERO_CLIENT_BEARER_TOKEN": "YOUR_XERO_CLIENT_BEARER_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Coordinalo — Service Business Operations is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Xero MCP Server belongs to Finance & Fintech and uses a local stdio subprocess. Pick Coordinalo — Service Business Operations for finance & fintech work and Xero MCP Server for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Coordinalo — Service Business Operations has no declared pricing — check the project's own site. Xero MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add coordinalo-service-business-operations-2 and xeroapi-xero-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coordinalo — Service Business Operations has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Xero MCP Server has 57/100 (Good) with 3 views, 0 installs and 385 GitHub stars.