Craft
by Craft
Read, write, reorganize and delete documents in a Craft space from an AI agent. 32 tools including five deletes, OAuth 2.0 with PKCE, and no OAuth scope that separates reading from deleting.
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 Craft via MCP
https://mcp.craft.do/my/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Craft 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
- The OAuth grant has no scopes. Neither Craft OAuth document declares
scopes_supported, so consent is all-or-nothing across 32 tools including five deletes. The only real boundary is the read-only / write-only / document-scope setting inside Craft's Connections tab. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or server-declared destructive hint is published here. The read/write/delete split is our classification.
- One tool name disagrees between the two enumerations. Anthropic lists
collectionSchema_create; Craft's table listscollections_create. We could not determine which the live server exposes. - Craft's own tool count is wrong on its own page. The document states 28 while tabulating 32.
blocks_revertis not generally available. Craft states it is only available from the edit-review widget, so an ordinary MCP client should not count on an undo call.- Collections cap at 20 properties, per Craft's documentation, and its guidance is to fetch the schema with
collectionSchema_getinjson-schema-itemsformat before modifying any item. - Pagination is enforced, not optional. Craft states large responses require cursor paging on
documents_list,documents_search,blocks_get,collectionItems_getandtasks_get, and that aCURSOR_INVALIDerror means the underlying data changed and the walk must restart. - One space per connection. Multi-space workspaces need one MCP server entry per space.
- ChatGPT cannot read media in a Craft document, per Craft's own limitations page, and connectors there are confined to developer mode and cannot be combined with most built-in tools.
- Craft's "official MCP documentation" link is a marketing page. Both the MCP and API help articles point readers at
www.craft.do/imagine/for "complete details"; that page is a gallery of example projects with no endpoint or tool reference.developer.craft.doredirects to the Craft homepage. The real reference is the shared document linked below. - The vendor documentation is a Craft-hosted document, and it is marked
noindex. Its HTML is an empty client-rendered shell; the text lives in a JSON payload the page fetches. Expect it to be invisible to search engines and to some automated readers. - Craft's help centre pages carry text addressed to AI readers. Every article opens with an instruction block telling automated readers to fetch a documentation index before exploring further. We report it rather than following it; a connector that pipes web content into an agent should treat all such text as data.
- Whether deleting a folder deletes its documents is unresolved. Craft documents a 30-day Recently Deleted window for documents, and we found no statement covering
folders_deletespecifically. Treat folder deletion as the least reversible call in the set.
Frequently asked questions
No. None of the 32 tools creates a share link, publishes a page or invites a collaborator by email. Craft publishing runs through the Share button in the app, which generates a craft.me web link, and Craft documents that flow separately from the connector. Nothing in the tool surface reaches an audience outside your own space.
Yes, and folders too. Five tools carry a delete verb: documents_delete, folders_delete, blocks_delete, tasks_delete and collectionItems_delete. Craft's help centre states deleted documents move to a Recently Deleted folder and can be restored for 30 days, so a document deletion is recoverable within that window.
None are advertised. Craft's RFC 9728 resource descriptor and its authorization server metadata were both read on 2026-08-22 and neither declares scopes_supported. There is therefore no consent-screen boundary between reading a note and deleting a folder. Craft's help centre describes read-only and write-only restrictions set inside Craft instead.
Thirty-two. Craft's own MCP document says the server provides 28 tools, but the table immediately below that sentence lists 32 names, and Anthropic's directory also lists 32. The prose count is stale relative to the table on the same page, so treat 32 as the figure and 28 as a leftover.
It exposes one space. Craft's documentation states the server is space-scoped with no cross-space access, and that connecting a second space requires a separate MCP connection. Craft's help centre also describes narrowing a connection to specific documents, daily notes and tasks, or search-matched documents.
It documents the self-created connection, not the directory listing. That page describes secret links with optional password protection over OAuth 2.0 dynamic client registration. The endpoint Anthropic lists, mcp.craft.do/my/mcp, returned a standard Bearer authentication challenge on 2026-08-22 pointing at Craft's own authorization server.
One tool can undo it, but not from a normal chat. Craft's documentation states blocks_revert can undo a previous mutation and that the tool is only available from the edit-review widget. From an ordinary client the practical undo is Craft's own version history in the app, not a connector call.
Yes, applied per authenticated user. Craft's MCP documentation states rate limits are per authenticated user and asks clients to retry after a short delay. It also states cursor-based pagination is enforced for requests with large responses, across documents_list, documents_search, blocks_get, collectionItems_get and tasks_get.
Sources
- Craft MCP Server documentation (retrieved 2026-08-22). This is the
documentationURL Anthropic's directory publishes for the connector. The page is client-rendered and markednoindex; its text was read from the JSON payload the page itself fetches. · retrieved 2026-08-22 - Craft Help Center, MCP overview (retrieved 2026-08-22) · retrieved 2026-08-22
- Craft Help Center, MCP Security (retrieved 2026-08-22) · retrieved 2026-08-22
- Craft Help Center, MCP Limitations with ChatGPT (retrieved 2026-08-22) · retrieved 2026-08-22
- Craft Help Center, Managing Documents (retrieved 2026-08-22) · retrieved 2026-08-22
- Craft Help Center, Publishing Documents and Sharing Documents — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Craft Help Center machine index,
llms.txt(retrieved 2026-08-22).support.craft.do/robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes, an express permission to synthesise.documents.craft.me/robots.txtcarries the content-signal preamble with no signal line and no disallow. · retrieved 2026-08-22 - Craft site index,
llms.txt(retrieved 2026-08-22) · retrieved 2026-08-22 - Live OAuth posture check: anonymous initialize to
https://mcp.craft.do/my/mcpreturned HTTP 401 withWWW-Authenticate: Bearer; RFC 9728 metadata athttps://mcp.craft.do/.well-known/oauth-protected-resource/my; authorization server metadata athttps://mcp.craft.do/my/auth/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Craft support — <mailto:feedback@craft.do> · Privacy
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
- Craft
- Tools
- 32
- Domain
- mcp.craft.do
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.