Skip to content

Duvo MCP.

Duvo MCP (Model Context Protocol) guide: hosted Duvo MCP endpoint, custom MCP server patterns, discovery cards, and the Duvo MCP Registry listing.

Duvo MCP

Duvo supports MCP as an agent integration surface for approved workspaces. Teams can use hosted Duvo MCP tools or connect custom MCP servers that expose proprietary systems, data sources, and workflows to agents.

Browser WebMCP

On duvo.ai pages, browsers with WebMCP enabled can call read_duvo_information with a topic: overview, pricing, developers, getting_started, authentication, mcp, or cli. The read-only tool returns the published Markdown document. It does not access workspace data or submit requests. Example input: {"topic":"pricing"}. The result contains the document in content[0].text. Invalid topics and failed document requests reject the call; they are not successful reads. Registration uses document.modelContext, with navigator.modelContext as a fallback for older previews. Availability depends on browser support. Public Markdown links remain available in every browser.

Hosted MCP

  • Endpoint: https://api.duvo.ai/v2/mcp
  • Access: workspace-issued credentials and scopes.
  • Use cases: start runs, create cases, inspect approvals, retrieve run messages, and expose Duvo tools to compatible agents.

Custom MCP Servers

  • Use custom MCP servers to expose internal systems, domain-specific tools, and proprietary workflows.
  • Keep tool descriptions specific, scoped, and auditable.
  • Route sensitive actions through human approvals or policy gates when needed.
  • Treat MCP tools as governed production capabilities, not arbitrary shell access.

Discovery

Machine-readable source:

https://www.duvo.ai/mcp.md