We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

Craft

MCP server by Craft Docs

Read and edit your Craft documents, notes and tasks from your AI assistant.

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Craft

Craft needs sign-in. Connect with its own URL:

https://mcp.craft.do/my/mcp

Your client opens Craft Docs’s sign-in the first time you use it. The token stays between your client and Craft Docs.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/craft

About

Connects your assistant to your Craft workspace, the notes, tasks and docs app from Craft Docs. The assistant can access your Craft documents and edit them on your behalf.

It runs as a hosted streamable HTTP endpoint at mcp.craft.do. Users sign in with their Craft account through OAuth, so no API key is needed. The tool list is not published ahead of sign-in.

What you can do

  • Access your Craft documents
  • Edit existing Craft documents
  • Use your Craft notes as context for the assistant

Tools

Craft lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • Summarize my latest meeting notes in Craft

  • Add a section on next steps to my project plan document in Craft

  • Find my Craft document about the podcast outline

Set up

Every client connects to mcp.craft.do, and Craft Docs asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http craft https://mcp.craft.do/my/mcp
  1. Start Claude Code, type /mcp, pick craft and choose Authenticate. A browser window opens for the Craft Docs sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it Craft and paste this URL:
https://mcp.craft.do/my/mcp
  1. Click Add, then Connect, and sign in when Craft Docs asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.craft.do/my/mcp and click Add.
  2. Click Connect and sign in when Craft Docs asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://mcp.craft.do/my/mcp as the server URL, then for authentication choose OAuth. ChatGPT sends you to Craft Docs to sign in.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "craft": {
      "url": "https://mcp.craft.do/my/mcp"
    }
  }
}

Cursor shows Needs authentication next to the server. Click the button beside it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"craft","type":"http","url":"https://mcp.craft.do/my/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "craft": {
      "type": "http",
      "url": "https://mcp.craft.do/my/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "craft": {
      "serverUrl": "https://mcp.craft.do/my/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add craft --url https://mcp.craft.do/my/mcp
codex mcp login craft

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.craft]
url = "https://mcp.craft.do/my/mcp"

Gemini CLI

gemini mcp add --transport http craft https://mcp.craft.do/my/mcp

Then, inside Gemini CLI, run /mcp auth craft to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "craft": {
      "type": "http",
      "url": "https://mcp.craft.do/my/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.craft.do/my/mcp.

Embed

Show Craft in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Craft on mcp.tc](https://mcp.tc/i/craft/badge.svg)](https://mcp.tc/i/craft)
HTML
<a href="https://mcp.tc/i/craft"><img src="https://mcp.tc/i/craft/badge.svg" alt="Craft on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/craft.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/craft" title="Craft on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/craft.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Craft card to your site.

Markdown
Add the mcp.tc card for Craft, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/craft.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="craft"><a href="https://mcp.tc/i/craft">Craft on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Craft on mcp.tc](https://mcp.tc/i/craft/badge.svg)](https://mcp.tc/i/craft)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.

Follow Craft and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/craft into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.craft.do/my/mcp, so your client talks to Craft directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Craft need an API key or a sign-in?

Yes, you need a Craft Docs account. The first time your client connects, it opens Craft Docs’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Craft a remote or a local server?

Remote. Craft Docs hosts it at https://mcp.craft.do/my/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Craft do?

You can access your Craft documents, edit existing Craft documents and use your Craft notes as context for the assistant.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Craft?

Partly. Craft’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Craft’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Craft Docs. This page was built from Craft’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.