MCP servercom.datailo/datailo

The connected account's email, service links, and plan states. action='keys' lists your dat_ keys (prefix, origin, created, last used — never the key); action='revoke_key' with key

Compact rows for every federated service: name, job, datasets, tool and workflow counts, tiers, whether it is enabled on this account. Rendered from each service's live product car

Sign in, inside the chat (needed to enable services and call their tools). Send the user's email and the language you are speaking with them (e.g. 'lt', 'en', 'de'). Datailo sends

Finish signing in. Call it RIGHT AFTER datailo_connect with the request_id and no code: it waits up to 45 s for the user to click Confirm in the email and returns as soon as they d

The full product card for one service: tagline, datasets, workflows, tiers, docs.

Disable a service: revokes the hub's key for it. Your account and data there remain yours.

Enable a federated service on your Datailo account. For services with an account model the hub links (or creates) your account there by your email and keeps an encrypted key; keyle

Call one tool of an enabled service through the hub: service, tool name and its arguments (see datailo_tool_schema). Returns the service's own result.

See a service's plan (action: status | enroll | change | discontinue). Everything is free during the beta: there is no paid plan to choose, nothing is charged and no checkout link

Orientation 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. Call this first.

The full input schema for one tool of an enabled service, and how to call it.

Search the tools of your enabled services (read live from each service). q takes words or a whole sentence: tools are ranked by the words they match, name and title first. service

One playbook's steps from the service itself, each annotated with the exact datailo_invoke call to run it through this connection. service='datailo' with a job name returns the who

Cross-service jobs first (service 'datailo', kind 'job': whole work products that chain several services), then each service's ready-made playbooks, marked enabled or not. Open one

Messages from the Datailo team to this person: replies to their feedback, questions about it, service notices and news about the tools they use. action='list' shows the inbox; 'rea

Send feedback about Datailo to the team that builds it: a bug, a wrong answer, missing data, a missing feature, a workflow idea, or praise. Every item is read by a person. When to