List your agent

Duvo MCP

MCP server● Hosted · onlinev2026-05-24

Governed retail, FMCG, and CPG operational tools: runs, cases, approvals, audit-ready execution

Reviews

No review yet. Used Duvo MCP? Be the first to help others choose.

What it does

Duvo MCP is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version2026-05-24
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 7h ago (live check)

Hosted endpoint

  • https://api.duvo.ai/v1/mcp streamable-http

Required: Authorization (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "duvo-mcp": {
      "url": "https://api.duvo.ai/v1/mcp",
      "headers": {
        "Authorization": "<your Authorization>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 7h ago

ONLINE Duvo MCP answered an MCP connection on 17 Nov 2026 and introduced itself as duvo-public-api 1.0.0 (MCP protocol 2025-06-18).

394 tools offered to AI assistants

  • listAgentMemoryFiles · List the memory files stored for an agent.
  • getAgentMemoryFile · Get the contents of a single memory file for an agent.
  • listPluginCatalog · List plugins that can be referenced by name in a build's plugins array. Builds may also reference any public GitHub repository URL (https://github.com/owner/repo) as a plugin; those are not enumerated here.
  • createSchedule · Create a schedule for an agent. The schedule fires against the agent's live build. The authenticated user owns the schedule. On a team with revisions, a repeating schedule for an Agent in an automation joins that automation's revisions: one
  • updateSchedule · Update fields on an existing schedule. Only supplied fields are changed; omitted fields retain their current values. Owners may update their own schedules; team superadmins may update any schedule on agents in the current team. A schedule t
  • deleteSchedule · Delete a schedule. Owners may delete their own schedules; team superadmins may delete any schedule on agents in the current team. Deleting a schedule that belongs to an automation with revisions stops it for its owner at once; the automatio
  • getTeam · Get a team by ID. The caller must be scoped to the requested team.
  • startNativeOAuth · Start an OAuth-based connection with a native provider (Gmail, Google Sheets, Outlook, etc.). The provider path parameter is the native OAuth provider key from listIntegrations, not the integration type. Returns an authorization URL that mu
  • authorizeMcpOAuth · Start an OAuth-based connection with a remote MCP server using Dynamic Client Registration. Returns an authorization URL the user must open in a browser; once they grant consent, Duvo creates the matching connection and redirects the browse
  • checkMcpOAuth · Probe an MCP server URL to discover whether it supports OAuth Dynamic Client Registration. Returns the authorization endpoint and required scopes when supported. Useful as a precursor to `/v2/teams/:team_id/connections/oauth/mcp/start` or `
  • listPulseDashboards · List your Duvo Pulse dashboards (live, agent-generated visualizations of your Duvo data). Ordered most recently updated first, except scope=automation, which is ordered by creation time (then id) so the whole scope can be read with the afte
  • createPulseDashboard · Create a new Duvo Pulse dashboard from a natural-language prompt (e.g. 'open cases by queue this week') and dispatch the first generation turn. Generation is asynchronous — poll GET /artifacts/{artifactId} until status is completed. The das
Show 88 more
  • getPulseDashboard · Get a Duvo Pulse dashboard's metadata and generation status. When status is completed and html_code_present is true, fetch the rendered HTML from GET /artifacts/{artifactId}/render; the conversation is served by GET /artifacts/{artifactId}/
  • getPulseDashboardHtml · Serve a Duvo Pulse dashboard's rendered HTML document (text/html, not JSON). 404 until the first generation turn has produced HTML.
  • getPulseDashboardPdf · Render a Duvo Pulse dashboard to a PDF document (application/pdf, not JSON). 404 until the first generation turn has produced HTML; 409 for an openui dashboard, whose substrate this exporter cannot render.
  • exportPulseDashboardHtml · Render a Duvo Pulse dashboard to a self-contained static HTML snapshot (text/html, data baked in). 404 until the first generation turn has produced HTML; 409 for an openui dashboard, whose substrate this exporter cannot render.
  • updatePulseDashboard · Update a Duvo Pulse dashboard's settings — rename it. Only the creator can update it.
  • publishPulseDashboard · Publish (share) a Duvo Pulse dashboard to your whole team or your whole organization, or revert it to private (creator only). When publishing, set permission to 'view' (teammates see the dashboard) or 'edit' (teammates can also iterate on i
  • deletePulseDashboard · Delete a Duvo Pulse dashboard. Only the creator can delete it.
  • duplicatePulseDashboard · Duplicate a Duvo Pulse dashboard, producing an idle clone of the current rendered dashboard. The conversation history, shares, and connections are not copied.
  • sendPulseDashboardMessage · Send an instruction to iterate on a Duvo Pulse dashboard (e.g. 'make it a bar chart', 'filter to last 14 days'). The creator can always iterate; teammates can too when the Pulse is published to the team with edit access. The agent regenerat
  • createPulseDashboardAttachmentUploadUrl · Issue a presigned upload URL for a file to attach to a Duvo Pulse dashboard message (e.g. an HTML dashboard to copy, or a screenshot to match). POST the file bytes to the returned upload_url as multipart form data under the field name 'file
  • getPulseDashboardAttachmentDownloadUrl · Mint a short-lived presigned URL to download or preview a file attached to a Duvo Pulse dashboard message. Returns 410 with code `sandbox_expired` once data retention deleted the dashboard's sandbox, and 404 when the file is otherwise gone.
  • refreshPulseDashboard · Trigger an on-demand data refresh of a Duvo Pulse dashboard. The dashboard regenerates its connection-sourced values in the background — poll GET /artifacts/{artifactId} for status.
  • stopPulseDashboardMessage · Stop an in-flight Duvo Pulse generation turn. Requires edit access to the dashboard. Flips the dashboard to 'interrupted' and keeps any streamed-so-far reply; stopping when nothing is generating is a successful no-op.
  • listPulseDashboardConnections · List the connections (data sources) attached to a Duvo Pulse dashboard (requires edit access).
  • attachPulseDashboardConnection · Attach one of your connections (data sources) to a Duvo Pulse dashboard so the agent can use its tools (requires edit access).
  • detachPulseDashboardConnection · Detach a connection (data source) from a Duvo Pulse dashboard (requires edit access).
  • answerPulseDashboardQuestion · Answer a pending question the Duvo Pulse agent asked and resume the paused run (creator or team editors). Use the toolCallId from the dashboard's message transcript.
  • listPulseDashboardMessages · List the chat transcript of a Duvo Pulse dashboard's live version (requires edit access). Returns the most recent page by default, oldest first within the page; pass `before` (a message id from a previous page) to walk back through older me
  • listPulseDashboardComments · List the comment threads on a Duvo Pulse dashboard (requires view access). Each thread carries its author, the dashboard element it is pinned to, its replies oldest-first, and whether it has been marked complete.
  • createPulseDashboardComment · Start a comment thread on a Duvo Pulse dashboard (requires view access). Pass `element` — captured from the dashboard canvas — to pin the thread to one element; omit it for a comment on the dashboard as a whole.
  • createPulseDashboardCommentReply · Reply to a comment thread on a Duvo Pulse dashboard (requires view access). `commentId` must be a thread root; threads are one level deep. A thread already marked complete still accepts replies and stays complete.
  • setPulseDashboardCommentResolution · Mark a Duvo Pulse dashboard comment thread complete, or reopen it (requires view access). Pass the target state in `resolved`; the call is idempotent, and the response carries the thread with `resolved_at` and `resolved_by` set or cleared.
  • deletePulseDashboardComment · Delete a comment or reply on a Duvo Pulse dashboard. Allowed for the comment's author and for the dashboard's creator. Deleting a thread root keeps its replies, rendered under a deleted opening comment.
  • listPulseDashboardVersions · List the version history of a Duvo Pulse dashboard, newest first (requires edit access). Use the version id with the restore and version-render endpoints.
  • getPulseDashboardVersionHtml · Serve a specific version's rendered HTML document for a Duvo Pulse dashboard (text/html, requires edit access).
  • restorePulseDashboardVersion · Restore a previous version of a Duvo Pulse dashboard, making it live again (requires edit access). Non-destructive — it moves the head pointer to the chosen version.
  • createSandbox · Create a new sandbox for file uploads. The returned sandbox_id can be passed to POST /v2/teams/:team_id/runs to stage data for a run.
  • createSandboxUploadUrl · Get a presigned URL for uploading a file into a sandbox. Use for files larger than 10MB; smaller files can be uploaded directly via POST /v2/sandboxes/:sandbox_id/files.
  • listSandboxFiles · List files in a sandbox directory.
  • uploadSandboxFile · Upload a file directly to the sandbox. Maximum file size is 10MB. For larger files, use POST /v2/sandboxes/:sandbox_id/upload-urls.
  • getRunEvaluation · Get the latest evaluation analysis for a specific agent run (Run).
  • getEvalScores · Aggregate evaluation counts and flag distribution for an Assignment's Jobs since the given timestamp.
  • getEvalRubrics · List the evaluation rubrics a Run is scored against: the platform default rubrics plus the Agent-specific rubrics for a build. Defaults to the Agent's live build; pass build_id to target the revision a specific Run ran against.
  • createEvalRubric · Add one Agent-specific evaluation rubric to a build. A build may hold at most 5 custom rubrics by default (25 on teams with the newer rubric generator enabled); this fails with 409 once the build's ceiling is reached, and the error message
  • replaceEvalRubrics · Replace a build's entire Agent-specific evaluation rubric set in one call (at most 5 rubrics by default, 25 on teams with the newer rubric generator enabled). Existing custom rubrics are removed and the supplied list becomes the new set; pa
  • updateEvalRubric · Edit a single Agent-specific evaluation rubric's title and/or description. The edit produces a NEW rubric (with a new id and slug) so previously scored Runs stay attributed to the original criterion; the response contains the new rubric.
  • deleteEvalRubric · Remove a single Agent-specific evaluation rubric. Future Runs on the build are no longer scored against it.
  • listAgentSchedules · List the schedules you own on an agent. Returns only your own schedules, whoever you are. Callers with an elevated team role can read every member's schedules on the agent, including who created each one, via `GET /agents/{agent_id}/schedul
  • listAllAgentSchedules · List every team member's schedules on an agent, including who created each one. Requires an elevated team role; callers without one receive 403 and should use `GET /agents/{agent_id}/schedules`, which returns only the schedules they own.
  • listAgentCaseTriggers · List the case triggers configured for an agent. Each trigger automatically dispatches the agent to run cases added to a queue.
  • previewAgentCaseTriggerConflicts · Preview which other agents would conflict with this agent's case trigger if it pointed at the given queue. Does not modify the trigger.
  • getAgentCaseTrigger · Retrieve a single case trigger by id.
  • createAgentCaseTrigger · Create a case trigger for an agent. An agent may have at most one case trigger; this returns 409 if one already exists.
  • updateAgentCaseTrigger · Update fields on a case trigger. Only the trigger creator or a builder/admin can disable an enabled trigger or change its queue, and only a builder/admin can change queue concurrency.
  • deleteAgentCaseTrigger · Delete a case trigger. Only the trigger creator or a builder/admin can delete it.
  • listAgentTriggers · List the trigger definitions the authenticated user owns on an agent (Agent in the Duvo UI). Triggers start a Run automatically when an external event fires (e.g. an email arrives or a Linear issue is created).
  • upsertAgentTrigger · Create or update the authenticated user's trigger for an integration on an agent. The integration must already be connected to the agent (its OAuth connection set up in the Duvo dashboard). Set `enabled: false` to pause a trigger without de
  • deleteAgentTrigger · Permanently delete one of your own event triggers on an agent. The agent stops starting Runs for that event and the trigger's filter config is lost. To keep the trigger but stop it firing, upsert it with `enabled: false` instead.
  • listAgentTriggerTypes · List the trigger types available for an agent, grouped by integration. Use the returned `integration_slug` and `trigger_type` values when creating a trigger.
  • createAgentSlackTrigger · Create a Slack channel trigger on an agent (Agent in the Duvo UI): the agent starts a Run whenever a matching message is posted in the channel. An agent can carry one trigger per channel, so call this once per channel. The Slack workspace m
  • listAgentSlackTriggers · List the Slack channel triggers you own on an agent (Agent in the Duvo UI), oldest first. Each trigger's `filter_config` carries the watched `channelId`, `channelName`, Slack `workspaceId`, and `matchRule`. Capped at 100 triggers per agent.
  • updateSlackTrigger · Update a Slack channel trigger you own — repoint it at another channel, change which messages match, or pause and resume it with `enabled`. Only the supplied fields change. Resuming a paused trigger requires the Slack connection it runs off
  • listAgentSlackBoundWorkspaces · List the Slack workspaces bound to an agent build that you can create channel triggers for. Creating a Slack channel trigger for any other workspace is rejected, so start here to pick a valid `slack_team_id` and `integration_instance_id`.
  • deleteSlackTrigger · Permanently delete a Slack channel trigger you own. The agent stops starting Runs for that channel. To keep the trigger but stop it firing, update it with `enabled: false` instead.
  • acceptRevisionGeneration · Accept the reviewed generated configuration and complete the builder run. The saved draft is not activated.
  • generateRevision · Generate agent instructions or code into a saved draft. Poll the returned builder run, answer questions if requested, then accept or decline the reviewed checkpoint. This never activates the revision.
  • promoteRevision · Promote a draft or historic revision to the live version. The live revision is the one used by triggers and new runs. Fails if the revision is already live, if a draft revision still has an active builder run, or with 409 if the agent's aut
  • resumeBuilderRun · Resume a builder run that is waiting for user input
  • cancelBuilderRun · Cancel a running builder run and pause its sandbox
  • createRevision · Create a new revision for an existing agent.
  • declineRevisionGeneration · Discard generated changes by restoring checkpoint_config and completing the builder run. The saved draft is not activated.
  • getRevision · Get a revision by ID.
  • getBuilderRun · Get the status of a builder run
  • getRevisionBody · Read one section of a revision's config as plain text, in character ranges: the AOP (`input`) or the code-step program (`source`). Use it instead of getRevision when the text is large; listAgents with `config=light` reports each agent's `in
  • listAgentRevisions · List revisions for an agent. Pass `config=light` to leave each revision's config out of the page and get its sizes instead; read the AOP with getRevisionBody.
  • updateRevision · Update a revision's configuration, name, description, or handover targets. Returns the updated revision.
  • duplicateAgent · Duplicate an existing agent into a new agent named "Copy of <name>", carrying over its configuration. Use the include_* flags in the (optional) body to control what is copied; all default on except memory. Requires the Lead Builder team rol
  • getAgent · Get an agent by ID. The response carries no revision config: use listAgentRevisions and getRevision for a revision, and getRevisionBody to read a large AOP in character ranges.
  • updateAgent · Update an agent's display name or delivery settings.
  • deleteAgent · Delete an agent and cascade-clean its schedules, case triggers, builder runs, and handover targets. Any active jobs are interrupted and their sandboxes paused.
  • moveAgent · Move an agent (and its connected workspace) to a different team. Pass dry_run=true to preview the closure without applying changes.
  • getAutomation · Get a single automation with its agent and queue counts, the tab arrangement its detail view navigates by, and `links` to each tab it has right now.
  • updateAutomation · Update an automation, e.g. rename it. Only the fields present in the body are changed.
  • generateAutomationProcessMap · Start the setup step Generate current process map for a Module automation being set up, the same as pressing it in the web app: Duvo writes the map of how the work runs today from the uploaded files, the interviews and the Policy. Returns 2
  • generateAutomationProposal · Approve the current process map of a Module automation being set up and start writing the automation proposal from it, the same as the setup's Approve and continue in the web app. The proposal says what Duvo automates, what stays with the t
  • approveAutomationProposal · Approve the automation proposal of a Module automation being set up, the same as the setup's Approve and build in the web app: it opens an Ask Duvo conversation that reads the proposal and the Policy, proposes which Agents, Queues and dashb
  • getAutomationTabs · Get the automation detail view's tab arrangement, plus metadata for the Pulse dashboards pinned into it. Pinned dashboards are filtered to the ones the calling identity may see.
  • updateAutomationTabs · Replace the automation detail view's tab arrangement. Pinning, unpinning, reordering and hiding a tab are all expressed as a different arrangement.
  • deleteAutomation · Soft-delete an automation. Its member agents and queues stop dispatching and disappear from listings, but their underlying rows and run history are preserved (not erased). Runs still in progress on its agents are interrupted.
  • duplicateAutomation · Duplicate an automation into a new one named "Copy of <name>", copying what it runs today: its live agents and builds, its queues (empty), the routing and handovers between them, and each agent's Memory when the team holds Memory and the ag
  • getAutomationCurrent · Get what the automation is set up to do right now: its member agents with the builds that are live, its queues' routing, and the triggers and schedules firing for it. The revision-less counterpart of the revision detail — an automation with
  • getAutomationCurrentFlow · Get the automation's flow graph as it stands right now: the agents and queues it currently wires together, plus the producer, consumer, and handover edges between them. The revision-less counterpart of the revision flow.
  • getAutomationReadiness · What still has to be set up before an automation can run on real work. Call this first for a readiness question ("what do I still need to set up", "is it ready to run", "why isn't it running") and before checking an automation's Connections
  • readAutomationDashboardData · The figures a Module automation's Pulse dashboards show, computed server-side the same way the dashboard computes them: each tile's `label`, `value`, `unit` and `display` (the value as the dashboard prints it), with a `description` where th
  • listProcessRoles · List the process roles of an automation (Operator, Executive, Approver and the like, defined on that one automation, not the team's Admin/Member/Builder roles) with what each can do and who holds it. Answer "who can see X", "who has which r
  • assignProcessMember · Put one person on an automation in one of its process roles. Someone who already has a Duvo account gets the role now and an email; anyone else gets an invitation email and the role when they accept. In an organization that requires single
  • addAutomationAgent · Add an agent to an automation on a team that is on the Automations workspace, with or without revisions — membership is not versioned. The agent must not already belong to another automation; on a team that changes its automations by revisi
  • removeAutomationAgent · Remove an agent from an automation on a team that is on the Automations workspace, with or without revisions — membership is not versioned. Deleting the agent interrupts its active runs and pauses their sandboxes, exactly as a standalone ag

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://api.duvo.ai/v1/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Websitehttps://www.duvo.aiDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/duvoai/duvo-website-2026DECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version2026-05-24DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Duvo MCP? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Duvo MCPLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Duvo MCP?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/duvo-mcp?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/duvo-mcp/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Duvo MCP

How do I connect Duvo MCP?

Use the hosted endpoint https://api.duvo.ai/v1/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Duvo MCP need an API key or token?

Yes. The registry entry lists a required value: Authorization. Get it from the publisher.

What tools does Duvo MCP offer?

When Electra Index connected on 17 Nov 2026, it listed 394 tools: listAgentMemoryFiles, getAgentMemoryFile, listPluginCatalog, createSchedule, updateSchedule, deleteSchedule, getTeam, startNativeOAuth and more. The full list is in "Live check" above.

Is Duvo MCP online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 7h ago.