---
name: Anchorify + MCP
description: Run Anchorify as a stdio MCP server so any MCP client (Claude Desktop/Code, Cursor, Zed) can publish and manage shares as tools.
---

# Anchorify + MCP

Anchorify ships a built-in [Model Context
Protocol](https://modelcontextprotocol.io) server. Point any MCP client
at it and the agent gets first-class tools to publish a document to a
stable URL, list and update shares, manage access, and read comments,
versions, and suggestions — no shelling out to the CLI.

It's the same `anchorify` npm package: the server is the `anchorify mcp`
subcommand, not a separate install.

## Install

```bash
npm i -g anchorify
```

Get a per-user token at <https://anchorify.io/dashboard/settings> (it's
the same token `anchorify login` uses).

## Configure your MCP client

Add one stanza. The server authenticates with `ANCHORIFY_TOKEN` from its
environment — put your token there.

**Claude Desktop** (`claude_desktop_config.json`), **Cursor**
(`.cursor/mcp.json`), or any client that speaks stdio MCP:

```json
{
  "mcpServers": {
    "anchorify": {
      "command": "anchorify",
      "args": ["mcp"],
      "env": {
        "ANCHORIFY_TOKEN": "your-token"
      }
    }
  }
}
```

To target a self-hosted or dev instance, add `"ANCHORIFY_HOST":
"http://localhost:3737"` to `env` (defaults to `https://anchorify.io`).

Restart the client; "anchorify" appears in its tool list.

## Tools

Flat tools mirroring the CLI verbs. All take a `share` argument (a slug,
id, or full URL) where they act on an existing share.

| Tool | What it does |
| --- | --- |
| `anchorify_publish` | Publish new content → returns the share URL |
| `anchorify_update` | Replace an existing share's content (snapshots a version) |
| `anchorify_list` | List your shares |
| `anchorify_view` | Fetch a share's raw source |
| `anchorify_delete` | Delete a share |
| `anchorify_set_access` | Set link access (restricted/view/comment/suggest) + indexing |
| `anchorify_set_password` | Set or clear a view password |
| `anchorify_rename` | Rename a share's slug (old URL 301s) |
| `anchorify_move` | Move a share into another project |
| `anchorify_comments_list` | List comments (with anchors + reactions) |
| `anchorify_comment_add` | Add a comment (document-level or anchored) |
| `anchorify_versions_list` | List version history |
| `anchorify_version_restore` | Restore a share to an older version |
| `anchorify_suggestions_list` | List a share's pending suggestions, or your own |

## Example prompts

- "Publish this proposal to Anchorify and give me the link."
- "List my Anchorify shares and update `q3-report` with this new draft."
- "Make `client-onboarding` view-only and not indexed."
- "Show me the comments on the `pricing-memo` share."

## Notes

- **Auth:** the server only does what your token can do — your own org's
  shares. Public reads (`anchorify_view` on a public share) work without
  a token; everything else needs `ANCHORIFY_TOKEN`.
- **Transport:** stdio only today. A hosted/remote (SSE + OAuth) server
  is a future addition.
- **No extra endpoints:** the MCP server is a pure client of the same
  HTTP API the CLI uses, so behavior matches `anchorify <verb>` exactly.