dpaperwork

MCP

Run your workspace from the tools you already use

Connect Claude to dpaperwork and ask about any client, deal, or document from where you already work. It reads and acts on the same records as the app, with the permissions you already have.

The same tools

The MCP tool list is the in-app assistant’s, so the two never drift apart.

Your own token

Mint a per-user token in Settings, scoped to one workspace. Revoke it any time.

Your permissions

Every call is checked against your role, exactly like the web app.

How it works

Step 1

Mint a token in Settings

A per-user token, scoped to one workspace. Revoke it any time.

Step 2

Add it to your MCP client

One command for Claude Code, or a config entry for Claude Desktop.

Step 3

Ask from where you work

Your role permissions apply to every call, just like the web app.

  • Every tool the in-app assistant has: query records, create and update them, run playbooks, read company knowledge
  • A single chat tool that runs a full dpaperwork agent turn from a plain-English prompt
  • Runs with your role permissions, so an MCP client can’t do more than you can
  • Read-only and unpaid workspaces block writes; queries keep working
  • Works with Claude Code, Claude Desktop, and any client that speaks Streamable HTTP

Part of one workspace

Every part reads and writes the same records, so nothing has to be kept in sync.

ChatAsk anything about a client, deal, or document.InboxA Morning Brief and alerts for what needs you.PlaybooksRoutine work, run on schedule within your limits.KnowledgeContext, activity, and decisions, recalled.PipelineOne board for every deal, across every client.DeliveryEvery project and cycle in one urgent-first list.DocsProposals and reports drafted from real history.

Less paperwork. More business.

Seats open in small batches — join the waitlist and you’ll be first in line when yours is ready.

orBook a demo