Dovri customer support handoff

io.dovriPublished by dovri.ioOfficial publisherv1.0.0Updated Oct 24, 2026

Search published help and hand customer chat to a person. Requires your app's backend integration.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant search published help content and hand a customer chat over to a human agent.

What you can do
This remote MCP server connects an assistant to Dovri's customer support handoff service. It lets the assistant search published help articles and escalate or hand off a customer chat thread to a person. It is a backend integration rather than a standalone tool, so it works alongside your own app's support setup.
When to use it
Worth adding when an assistant already handles customer conversations and needs to look up published help content or pass a chat to a human agent. It suits teams using Dovri for support handoff who want that step available inside an assistant workflow.
Requirements
A remote streamable HTTP endpoint at the provider's API host, with bearer authentication required. The Authorization header must carry a thread-bound agent token obtained from the chat-session integration endpoint, and that token expires within about fifteen minutes. No packages or environment variables are declared.
Before you install
The Authorization header is backend-only: the token must not be exposed to a browser, and an app server key must not be used in its place. The token is short-lived, so it needs refreshing. Handing a chat to a person changes the state of a live customer conversation, so confirm when a handoff should occur.

Installation

In SourceWeft

  1. Open Dovri customer support handoff in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.dovri%2Fhandoff/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "dovri-customer-support-handoff": {
      "type": "http",
      "url": "https://api.dovri.io/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 23, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.