Servicialo MCP server
{
"mcpServers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server@latest"
]
}
}
}{
"mcpServers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server@latest"
]
}
}
}{
"mcpServers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server@latest"
]
}
}
}{
"servers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server@latest"
]
}
}
}{
"mcpServers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @servicialo/mcp-serverversion 0.9.0
What it does
Servicialo is an open protocol for coordinating booking, scheduling, identity verification, and payment settlement of professional services via AI agents. It is for developers building platforms that need to interact with service providers and clients across multiple service types using a common protocol specification.
- Build a platform that allows AI agents to discover, schedule, and verify delivery of professional services without custom integrations for each service type.
- Coordinate multi-party availability (provider, client, resource) with standardized handling of scheduling exceptions and state transitions.
- Handle financial settlement, invoicing, and revenue sharing between service providers and clients with explicit separation of payer from client.
Tools this server exposes
| Tool | Does |
|---|---|
| service_coordination | Handles multi-party availability scheduling and exception flows for professional services. |
| identity_verification | Manages provider credentials, trust scores, and explicit separation between client and payer. |
| financial_settlement | Manages invoicing, payment collection, and revenue sharing with dispute resolution. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.