DocSend

DocSend MCP Server

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.

GitHub

Documentation

📖
Authentication
https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/authentication/docsend-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/rate-limits/docsend-rate-limits.yml

Other Resources

🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/mcp/docsend-mcp.yml
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/scopes/docsend-scopes.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/docsend-mcp-server"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
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.