Superhuman Docs MCP server icon

Superhuman Docs

by Superhuman Docs

Productivity32 tools

Create docs, build tables, run formulas and search your workspace from your AI assistant. 32 tools, OAuth sign-in with a single scope named mcp:all, and a personal-access-token path that is the only way to get read-only.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Superhuman Docs via MCP

https://docs.superhuman.com/apis/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Superhuman Docs Tools & Capabilities (32)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • OAuth cannot be narrowed. The descriptor advertises one scope, mcp:all, and the vendor confirms OAuth connections are set to read and write automatically. Granular scopes are documented as coming soon. A read-only OAuth connection is not something you can approve today.
  • The free tier is a taste, not a plan. 30 requests per week with a 60-per-month ceiling, after which access stops until you upgrade to a paid Doc Maker role. Editors on any plan get read-type tools only.
  • Deleted documents survive 7 days, and nothing else gets a trash. Tables, rows, columns, views, controls and comments have no documented restore path, and the connector ships no undelete tool for any object type.
  • Restoring a document to a previous version requires Support. Version history lets you view changes and copy an old version into a *new* doc, but restoring the original in place is a support request, not a self-serve action.
  • The vendor's prose lags its own tool reference. The usage guide names url_decode and ReadPage, neither of which appears in the published tool list. Superhuman Docs itself warns that tool names and parameters are not fixed and may change, and tells developers not to hardcode them.
  • HIPAA organizations lose Docs AI entirely. Superhuman Docs states that where an organization requires HIPAA compliance, AI is automatically turned off for all workspaces and the AI controls do not appear in admin settings.
  • Prompt injection is the vendor's own stated risk. Its security guidance warns that content inside your docs could carry malicious instructions aimed at the assistant, and recommends requiring human confirmation before deletions and bulk table edits.
  • No tool descriptions came from the server. The endpoint requires OAuth, so we read 32 names from Anthropic's directory and every behavioural detail from Superhuman Docs' published reference. We read no parameter schemas and no safety annotations, because the handshake never reached tools/list.
  • We did not exercise any tool. Our check was an anonymous protocol request that returned an authentication challenge, plus reads of the server's own metadata documents.

Frequently asked questions

Which Superhuman Docs plan do you need for the MCP server?

A paid plan for full use. Superhuman Docs documents that Doc Makers on paid plans get the complete MCP experience with all tools and endpoints. Free plans and Editors get a limited free taste capped at 30 requests per week and 60 per month, and Editors are restricted to read-type tools only. Exceeding the cap requires upgrading to a paid Doc Maker role.

Can you connect the Superhuman Docs MCP server as read-only?

Only with a personal access token, not with OAuth. Superhuman Docs states that OAuth 2 connections automatically get read and write, and that more granular scopes are coming soon. Personal access tokens let you choose read only, write only, or read and write, so the vendor explicitly recommends tokens if you want to limit scope.

Can the Superhuman Docs MCP server permanently delete a document?

Yes, but a deleted doc sits in the trash for 7 days first. Superhuman Docs documents that deleted docs are recoverable from the Deleted tab for 7 days, after which they are permanently removed and cannot be restored. The vendor tool reference describes document_delete itself as an action that cannot be undone, so the two sources disagree and the trash window is the reconciling detail.

Do I need to switch if I already connected the Coda MCP?

No. Superhuman Docs states that existing Coda MCP connections keep working exactly as before, even when you use docs.superhuman.com URLs, and that the older coda.io/apis/mcp server is still officially supported. The vendor says it will notify users if and when moving over makes sense.

Why am I getting a 401 error when using an auth token to connect?

The token most likely has the wrong restriction type. Superhuman Docs advises generating a new token from your account settings and selecting MCP as the restriction type, then retrying the connection. Personal access tokens created for other purposes will not authenticate against the MCP endpoint.

Can an admin block the Superhuman Docs MCP server for an organization?

Yes, on Enterprise plans. Superhuman Docs gives Enterprise org admins separate controls for personal access tokens and OAuth, each set to all members, selected members, or no members. Changes take effect immediately and block existing connections rather than revoking them, so restoring access automatically unblocks the earlier tokens.

Sources

Use in Agentman

Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio

Server Info

Category
Productivity
Developer
Superhuman Docs
Tools
32
Domain
docs.superhuman.com

Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.