Craft is a document and note-taking app for writing structured documents, managing tasks, and organizing a personal or team knowledge base.
Agen.co connects to Craft through Craft's own hosted MCP server as an Official connector. Each user authorizes one Craft space, and agents work with the documents in that space.
Prerequisites
Prerequisites
- A Craft account with access to the space you want to connect. No app needs to be registered with Craft — the MCP server registers Agen.co as a client automatically, so there is no Client ID or Client Secret to copy.
- If a workspace administrator has disabled MCP access in Craft, ask them to enable it before connecting.
In the Agen.co portal, go to Connectors → My connectors and click Add connector.
In the Select connector drawer, search for
Craftand select it. The Add Craft panel opens.Fill in the field:
Field Required Description Instance Slug Yes Prefixes each imported tool as slug__tool, so several instances of the connector can coexist. Prefilled withcraft. Use lowercase kebab-case. You can change it later from the connector's settings.Click Connect. Craft opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
On the Authorize MCP client screen, which reads MCP OAuth Client wants to access your Craft space, choose the space in the dropdown and click Approve. Sign in to Craft first if prompted. The requesting client is named MCP OAuth Client rather than Agen.co.
Back in Agen.co, the panel switches to Select the tools to import from Craft. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even though the Craft tab reported success.
Adding the connector doesn't authorize anyone's tool calls yet. The first time each user's agent calls a Craft tool, the call returns an authorization link instead of a result. The user opens the link, chooses a space, and clicks Approve. On this screen the requesting client is named mcp-gateway:source:<uuid> wants to access your Craft space, not MCP OAuth Client as when adding the connector — this is expected, so tell users to approve it. After that, the user's tool calls run against the space they chose, with their own Craft access.
Each authorization covers a single Craft space. A user who needs agents to reach a second space has to authorize it separately.
Once connected, Craft appears under My connectors with three tools:
| Tool | What it does |
|---|---|
craft_read | Runs read commands against the connected space |
craft_write | Runs commands that create or change content |
blocks_revert | Reverts changes made to blocks |
craft_read and craft_write don't take separate fields per operation. Each accepts a single string of CLI-style commands, for example folders list; documents list. The commands cover:
| Area | What it covers |
|---|---|
| Documents and folders | Documents, their blocks, and the folders that organize them |
| Collections | Collection tables, their schemas, and items |
| Daily notes | Daily notes in the space |
| Tasks and reminders | To-dos and reminders |
| Whiteboards | Whiteboards in the space |
| Images and files | Images and files attached to documents |
| Search | Searching content across the space |
Because policies grant access per tool, allowing craft_write allows every write command it accepts. To keep agents read-only, allow only craft_read.
Enabling the Craft connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.