Dora

work.doraPublished by dora.workOfficial publisherv1.0.1Updated Oct 30, 2026

AI account manager and client portal: requests, approvals, clients, files, and handing work over.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Dora is a remote MCP server for an AI account manager and client portal covering requests, approvals, clients, files and work handover.

What you can do
  • Work with client requests and approvals
  • Manage client records in the portal
  • Handle files attached to client work
  • Hand work over between people or stages
  • No individual tools are listed, so the exact actions depend on what the server exposes after connecting.
When to use it
Consider it if your team runs client-facing work through Dora and wants an assistant to help track requests, approvals, client records and handovers inside that portal.
Requirements
A remote endpoint at dora.work reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your Dora account, which holds client records, files and approval decisions; actions may create, change or hand over work data. Review the scopes requested at sign-in and confirm what the assistant is allowed to modify.

Installation

In SourceWeft

  1. Open Dora in the dashboard and add it to a workspace.
  2. Connect the required 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/work.dora%2Fdora/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dora": {
      "type": "http",
      "url": "https://dora.work/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Oct 30, 2026

Score

67% 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
  • 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.

Other Dora integrations