Superhuman Docs
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/mcpWorks 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_decodeandReadPage, 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
- Live auth posture check against
https://docs.superhuman.com/apis/mcp— an anonymousinitializereturns HTTP 401, and the server's RFC 9728.well-known/oauth-protected-resource/apis/mcpdescriptor returns HTTP 200 withresource_name: "Superhuman Docs MCP Server",authorization_servers: ["https://id.superhuman.com"]andscopes_supported: ["mcp:all"]. Our own observation, 2026-08-18. Sibling-path probes the same day:POST /apis/returns HTTP 401;/,/mcp,/apisand/api/mcpreturn HTTP 400InvalidCsrfTokenfrom the Coda web app.GETon the MCP path returns HTTP 401 as well, so the server publishes no public tool catalogue over GET./llms.txtand/skill.mdreturn HTTP 404. · retrieved 2026-08-18 - Authorization server metadata —
https://id.superhuman.com/.well-known/oauth-authorization-serverreturns HTTP 200 withissuer: "https://id.superhuman.com", PKCES256, andscopes_supported: ["mcp:all"]. The same path ondocs.superhuman.comreturns HTTP 200 withissuer: "https://tokens.grammarly.com"and identical scope and PKCE values — the resource host serves the un-rebranded Grammarly token service metadata. Our own observation, 2026-08-18. · retrieved 2026-08-18 - Legacy endpoint check —
https://coda.io/apis/mcpreturns HTTP 401; its descriptor returns HTTP 200 withresource_name: "Superhuman Docs MCP Server",scopes_supported: ["mcp:all"]andauthorization_servers: ["https://coda.io"]. Our own observation, 2026-08-18. · retrieved 2026-08-18 - Connect to the Superhuman Docs MCP (retrieved 2026-08-18 via the help centre API; vendor-updated 2026-08-17). Source for supported clients, per-client setup, the plan and role gate, the 30/60 request caps, the OAuth-versus-token scope answer and the 401 troubleshooting entry. · retrieved 2026-08-18
- Using the Superhuman Docs MCP (retrieved 2026-08-18 via the help centre API; vendor-updated 2026-08-17). Source for example use cases, best practices, the URL-pasting efficiency tip, the pricing answer and the warning that tool names may change. · retrieved 2026-08-18
- Security recommendations for the Docs MCP (retrieved 2026-08-18 via the help centre API; vendor-updated 2026-08-17). Source for the
mcp:allscope statement and the "coming soon" granular scopes, the read/write/read-and-write token table, the official endpoint, audit trails and the prompt injection guidance. · retrieved 2026-08-18 - Manage AI and MCP controls for your Docs org (retrieved 2026-08-18 via the help centre API; vendor-updated 2026-08-12). Source for the Enterprise admin controls over PAT and OAuth access, and the block-versus-revoke distinction. · retrieved 2026-08-18
- Superhuman Docs MCP tools and endpoints — , which returns HTTP 301 to
docs.superhuman.com/@bharat-batra/tools-and-endpoints(HTTP 200 after the redirect, retrieved 2026-08-18). The vendor's own tool reference, linked from the help centre. Source for the 33-tool vendor list used in the subset check, and for every tool description on this page includingdocument_delete("cannot be undone"),document_manage,tool_guide,name_matchandurl_convert. · retrieved 2026-08-18 - Delete and recover docs (retrieved 2026-08-18 via the help centre API; vendor-updated 2026-08-17). Source for the 7-day trash window, the Deleted tab restore path, and that deletion and restoration both require Doc Maker ownership. · retrieved 2026-08-18
- View and copy doc history (retrieved 2026-08-18 via the help centre API). Source for per-plan history retention and that an in-place restore requires contacting Support. · retrieved 2026-08-18
- What's changing: Coda becomes Superhuman Docs (retrieved 2026-08-18 via the help centre API). Source for the October 2025 Grammarly-to-Superhuman rename, the 8 July 2026 Coda-to-Superhuman-Docs launch and the coda.io URL redirects. · retrieved 2026-08-18
- Roles in Superhuman Docs (retrieved 2026-08-18 via the help centre API). Source for the Doc Maker, workspace admin and Editor roles and that Doc Maker seats are the paid licences. · retrieved 2026-08-18
- Privacy policy — Anthropic's directory publishes
https://www.grammarly.com/privacy-policy, which returns HTTP 301 to (HTTP 200, retrieved 2026-08-18; effective 2026-07-06). Names Superhuman Platform Inc. (formerly Grammarly) as issuer and as the data controller for the EU, EEA, UK and Switzerland, and lists Grammarly Inc. and Coda Project LLC as subsidiaries. · retrieved 2026-08-18 - Anthropic connectors directory snapshot, 2026-08-16 — source for the 32 tool names, the partner tier, the endpoint, the streamable-HTTP transport and the productivity category. A separate listing, Superhuman Mail, covers a different endpoint and different tools; the two are distinct connectors for distinct products. · retrieved 2026-08-16
robots.txtpolicy check, 2026-08-18:docs.superhuman.com/robots.txtis a blanketDisallow: /, so we read only the vendor's own tool reference, which Superhuman's help centre nominates by link, and did not crawl that host.help.superhuman.com/robots.txtpermits/hc/*/articles/, andcoda.io/robots.txtdisallows/apis/,/docsand/d/while permitting/resources/. NoContent-Signaldirective is present on any of the three hosts. The help centre article URLs above return HTTP 403 to a plain command-line client while its public help-centre API serves the same articles at HTTP 200, which is how they were read. That is a bot-filtering behaviour, not a policy signal —robots.txton that host permits the path. · retrieved 2026-08-18
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 StudioServer 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.