6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Create docs, build tables, run formulas and search your workspace from an AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Superhuman Docs MCP server connects a Superhuman Docs workspace — the product that was Coda until July 2026 — to Claude, ChatGPT, Cursor and any MCP agent. It exposes 32 tools for creating documents and pages, building tables, running formulas, managing comments and searching your workspace. Sign-in is OAuth, and the connection grants read and write together.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
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.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.tools/list.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.
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.
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.
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.
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.
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.
https://docs.superhuman.com/apis/mcp — an anonymous initialize returns HTTP 401, and the server's RFC 9728 .well-known/oauth-protected-resource/apis/mcp descriptor returns HTTP 200 with resource_name: "Superhuman Docs MCP Server", authorization_servers: ["https://id.superhuman.com"] and scopes_supported: ["mcp:all"]. Our own observation, 2026-08-18. Sibling-path probes the same day: POST /apis/ returns HTTP 401; /, /mcp, /apis and /api/mcp return HTTP 400 InvalidCsrfToken from the Coda web app. GET on the MCP path returns HTTP 401 as well, so the server publishes no public tool catalogue over GET. /llms.txt and /skill.md return HTTP 404. · retrieved 2026-08-18https://id.superhuman.com/.well-known/oauth-authorization-server returns HTTP 200 with issuer: "https://id.superhuman.com", PKCE S256, and scopes_supported: ["mcp:all"]. The same path on docs.superhuman.com returns HTTP 200 with issuer: "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-18https://coda.io/apis/mcp returns HTTP 401; its descriptor returns HTTP 200 with resource_name: "Superhuman Docs MCP Server", scopes_supported: ["mcp:all"] and authorization_servers: ["https://coda.io"]. Our own observation, 2026-08-18. · retrieved 2026-08-18mcp:all scope 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-18docs.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 including document_delete ("cannot be undone"), document_manage, tool_guide, name_match and url_convert. · retrieved 2026-08-18https://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-18robots.txt policy check, 2026-08-18: docs.superhuman.com/robots.txt is a blanket Disallow: /, 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.txt permits /hc/*/articles/, and coda.io/robots.txt disallows /apis/, /docs and /d/ while permitting /resources/. No Content-Signal directive 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.txt on that host permits the path. · retrieved 2026-08-18Connect Superhuman Docs once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.