Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect DocSend to Claude Code

Have Claude pull viewer analytics and react to view events in DocSend. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect DocSend to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect DocSend, you add a DocSend MCP server: a small hosted service that exposes DocSend's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own DocSend account. No API keys pasted into config files.

claude mcp add --transport http docsend https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in DocSend once connected?

A read-and-events DocSend connector lets Claude pull visit and page-by-page engagement, summarize who looked at a shared link, and react to new-view and new-space events through DocSend's documented Zapier triggers and webhooks, all once you approve. The viewer triage that meant manual checking happens where your documents already live.

  • Pull visit and page-by-page engagement analytics for a shared link
  • Summarize who viewed a document and how far they read
  • Receive a new-view event through a webhook and route it onward
  • List documents and shared links your account can already see
  • Flag when a space or data room records a new viewer event
  • Draft a follow-up email when a key viewer opens a link

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same DocSend access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the DocSend API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when DocSend changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build DocSend connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same DocSend connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own DocSend account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on DocSend's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to DocSend?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the DocSend account it signs in with. Revoking access is one click in DocSend.

More on the DocSend connector

DocSend connector for claude.aiSignNow + Claude CodeSignRequest + Claude CodeProposify + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us