General Tools
datailo.com
Provides general-purpose tools through the Model Context Protocol.
ENDPOINT 1
https://mcp.datailo.com/mcp
MCP server metadata
- Name
- datailo
- Version
- 0.1.0
Datailo is one MCP connection to every Kiznis Studio data and workflow service. Call datailo_start_here first: it orients you on what is enabled, what is available, and the next step. The tool surface is fixed and flat — datailo_* tools only, never a child's own tool names. Speak to the user in THEIR language at every step; tools return machine states (state, next) for you to explain. Browsing needs no sign-in; enabling services and calling their tools does, and it happens inside the chat: datailo_connect(email, language) sends one email with a confirm link and a six-digit code; the user clicks Confirm or tells you the code; then call datailo_connect_verify(request_id, code?) — with the code, or with no code right away: it waits for the click, so the user never has to come back and say they confirmed. The result contains `session`: pass session=<that value> on EVERY later Datailo call in the conversation, or a client that opens a fresh connection per call is anonymous again. For a sign-in that lasts across chats, the user reconnects Datailo with 'Sign in' (OAuth) in the connector.
Known tools 15
datailo_start_hereOrientation for a new connection: the cross-service jobs you can hand over (listed first), which services are enabled, which are available, and what to do next.
Inferred read-onlydatailo_connectSign in, inside the chat (needed to enable services and call their tools).
Inferred read-onlydatailo_catalogCompact rows for every federated service: name, job, datasets, tool and workflow counts, tiers, whether it is enabled on this account.
Inferred read-onlydatailo_describeThe full product card for one service: tagline, datasets, workflows, tiers, docs.
Inferred read-onlydatailo_planSee a service's plans or record that you want to enroll, change or discontinue one (action: status | enroll | change | discontinue).
Inferred read-onlydatailo_toolsSearch the tools of your enabled services (read live from each service).
Inferred read-onlydatailo_tool_schemaThe full input schema for one tool of an enabled service, and how to call it.
Inferred read-onlydatailo_invokeCall one tool of an enabled service through the hub: service, tool name and its arguments (see datailo_tool_schema).
Inferred read-onlydatailo_workflowsReady-made playbooks across the services (from each service's live card), marked enabled or not.
Inferred read-onlydatailo_workflowOne playbook's steps from the service itself, each annotated with the exact datailo_invoke call to run it through this connection.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.datailo]
url = "https://mcp.datailo.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"datailo": {
"type": "http",
"url": "https://mcp.datailo.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: datailo
Remote MCP URL: https://mcp.datailo.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"datailo": {
"url": "https://mcp.datailo.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"datailo": {
"type": "http",
"url": "https://mcp.datailo.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "datailo",
"transport": "streamable-http",
"url": "https://mcp.datailo.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.