Skip to main content
This is the catalog of tools the Duvo MCP server makes available once your host is connected. It exposes every Public API endpoint as a tool. Tool names are the OpenAPI operationId values — camelCase, stable identifiers. Renaming a value is a breaking change, so names only change in major releases. New Public API endpoints automatically become MCP tools on the next deploy. There is no separate registration step.
A Setup is a versioned configuration of an Agent — its AOP, Connections, and other settings.
Cases are individual work items routed through an Agent. Queues group related cases.
Files attached to a case. Uploading is a three-step flow: mint an upload URL, PUT the bytes to it, then finalize so the file becomes visible on the case.
Case triggers automatically route new cases to a queue based on matching rules.
Event triggers start a Run automatically when an external event fires (for example, an email arrives, a Linear issue is created, or a file changes in Google Drive).Slack channel triggers have their own tools: an Agent can watch many channels at once, so each channel is a separate trigger rather than one trigger per Connection.
Duvo proposes improvements to an Agent based on its past Runs — for example, adding, removing, or replacing a Connection. These tools manage the suggestions inbox.
Skills keep a version history. Instead of editing the live version in place with updateSkillFile, open a draft, edit the draft’s files, then activate it — the previous version stays intact and can be re-activated later.
These tools attach Connections, Logins, and Secrets to a specific Setup.
Inviting requires the Manager role or above on the team; revoking a team invitation requires Superadmin or above. Creating an invitation does not email anyone — call sendTeamInviteEmail with the returned id, or use bulkCreateTeamInvites, which creates and emails in one step.Accepting or declining an invitation is not exposed as a tool: both are matched against the signed-in person’s verified email address, so they only work from the Duvo web app.
Notification tools require the Notification Center feature and return a not-found error when it is not enabled for the team.
deleteReadNotifications and deleteAllNotifications permanently delete notifications and cannot be undone. Both are flagged as needing your approval, so a host that supports permission prompts asks you to confirm every call before the tool runs.
Clarity v2 snapshot tools keep their existing names and endpoints. On backends supporting plural exceptions, save tools accept either exceptions arrays or the older exception/handling pair on each step and return V2 arrays. Mixing both shapes on one step is invalid. Arrays preserve exception IDs, handling, and frequency. Refresh your client’s tool schemas and support both response versions before using the upgraded backend; tool results contain the endpoint response as JSON text.Ask Duvo applies the same team, process, and organization permissions as the web app. Organization tools therefore work only when the represented user has the required organization role. Live browser recording, audio/media transport, upload ingestion callbacks, and other session-bound internals are not tools. For free-form artifact edits, Ask Duvo uses its reviewed patch-draft workflow; the lower-level Artifact Chat send-message and patch-decision routes remain CLI and web-app surfaces instead of raw MCP tools.
Pulse dashboards are live, agent-generated visualizations of your Duvo data.
Generation runs in the background — after creating or iterating on a dashboard, poll getPulseDashboard until its status is completed, then read its rendered HTML.

Connect to the Duvo MCP server

Set up a host before calling these tools.

Public API Reference

Exact request and response shapes for each tool.