Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Full read-write Claude connector for DocSend

Have Claude pull viewer analytics and react to view events in DocSend

Stop clicking through DocSend to chase view data. Claude pulls page-by-page engagement, summarizes who viewed a shared link, and reacts to new-view events through DocSend's documented Zapier triggers and webhooks, all where your documents already live.

Build my connectorTalk to us

DocSend is a document-sharing and tracking tool teams use to send decks, proposals, and data rooms as trackable links and see how viewers engage. People want Claude to surface that activity: to read visit analytics, summarize who engaged, and route new-view events into their workflow.

What is a DocSend MCP server?

A DocSend MCP server is a small hosted service that exposes DocSend's data and actions to Claude over the Model Context Protocol, so Claude can agreements and signatures inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can DocSend's current connector do today?

Today, DocSend has no widely available first-party Claude or MCP connector, so out-of-the-box Claude cannot read your tracking analytics or react to view events in your account. DocSend exposes no confirmed public write API for creating links or changing access, so a custom connector focuses on the read and event surface DocSend documents, such as Zapier triggers and webhooks, with approvals on anything outbound.

What does full read-write DocSend access unlock?

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

Can Claude create a DocSend share link with access controls?

Not through any confirmed public API. DocSend documents no public link-creation endpoint, and its Zapier and webhook surface is read-only, so it cannot create links or set access settings such as email verification, a passcode, an NDA gate, expiry, or downloads. A create-link tool would need a private API you confirm DocSend grants.

Can Claude pull viewer analytics for a DocSend link?

Pulling viewer analytics is a read action Claude handles: it fetches visit and page-by-page engagement for a shared link so you can see who looked at what. These read tools stay separate from the write tools, and Claude never sees more analytics than your own DocSend account exposes.

Can Claude tell me when someone new views a document?

Yes. DocSend can deliver new-view events through its documented Zapier triggers and webhooks, and Claude reacts to those: it can summarize the visit, flag a key viewer, or draft a follow-up. This stays read and event-only, and Claude never sees more activity than your own DocSend account exposes.

How a DocSend connector works

We build a small MCP server that connects to DocSend through the read and event surface your account exposes, such as Zapier triggers, webhooks, or a scoped credential. DocSend documents no confirmed public write API, so the connector centers on read tools (fetch analytics, list documents) and event handling (new-view notifications). Any outbound action Claude takes in another tool, like sending a follow-up, requires your confirmation. Claude never has more access than your own account.

Frequently asked questions

Can Claude create a DocSend share link, not just read analytics?
Not through any confirmed public API. DocSend documents no public link-creation endpoint, and its Zapier and webhook surface is read-only and cannot create links. A create-link tool would depend on a private or enterprise API you confirm DocSend grants your account. Otherwise the connector focuses on reading analytics and events.
What can the connector actually do with my DocSend data?
It reads what your account already exposes: visit and page-by-page engagement, document and link lists, and new-view events delivered through Zapier triggers or webhooks. Claude can summarize that activity and react to it, but DocSend documents no public write API, so it does not change access controls or revoke links.
Can the connector get more access to my DocSend than I have?
No. The connector authenticates as your account through OAuth or a scoped credential and inherits the permissions you already hold. It never grants Claude more access to documents, spaces, or analytics than you have yourself, and we scope the tools to only the actions the work actually needs.

Related connectors

SignNow connectorSignRequest connectorProposify connector

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