DocSend MCP Server

name: DocSend MCP Server
description: 'DocSend''s hosted Model Context Protocol server — the only programmatic surface DocSend
  publishes. An MCP client POSTs Streamable-HTTP JSON-RPC to https://docsend.com/mcp (also reachable at
  https://mcp.docsend.com/mcp) with an OAuth 2.0 bearer token. The authorization surface is fully machine-discoverable:
  RFC 8414 authorization-server metadata, RFC 9728 protected-resource metadata, RFC 7591 dynamic client
  registration and mandatory PKCE (S256). Five resource scopes are advertised — documents:read, spaces:read,
  spaces:write, analytics:read, contacts:read — so the surface spans documents, Spaces (virtual data rooms),
  viewer analytics and contacts, with Spaces the only writable domain. The tool list is behind the bearer
  requirement and DocSend publishes no MCP documentation, so tools must be discovered after authorizing.'
humanURL: https://www.docsend.com/
baseURL: https://docsend.com/mcp
tags:
- MCP
- Agents
- Document Sharing
- Data Room
- Analytics
properties:
- type: MCPServer
  url: mcp/docsend-mcp.yml
- type: Authentication
  url: authentication/docsend-authentication.yml
- type: OAuthScopes
  url: scopes/docsend-scopes.yml
- type: RateLimits
  url: rate-limits/docsend-rate-limits.yml
x-humanurl-note: DocSend publishes no documentation page for this API — no developer portal, no API reference,
  no MCP setup guide on any readable host. humanURL points at the product the API serves, which is the
  closest human-readable page that genuinely exists. No Documentation / DeveloperPortal / APIReference
  pointer is emitted for this repo, because none of those pages exist.