@anyslate/mcp

Connect AI agents to your AnySlate workspace via the Model Context Protocol.

Setup

Add to your MCP client configuration:

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "anyslate": {
      "command": "npx",
      "args": ["-y", "@anyslate/mcp@latest"],
      "env": {
        "ANYSLATE_TOKEN": "as_mcp_your_token_here"
      }
    }
  }
}

Claude Code

claude mcp add anyslate -- npx -y @anyslate/mcp@latest

Then set the ANYSLATE_TOKEN environment variable before running Claude Code.

Cursor

Go to Settings > MCP Servers > Add Server:

{
  "anyslate": {
    "command": "npx",
    "args": ["-y", "@anyslate/mcp@latest"],
    "env": {
      "ANYSLATE_TOKEN": "as_mcp_your_token_here"
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "anyslate": {
      "command": "npx",
      "args": ["-y", "@anyslate/mcp@latest"],
      "env": {
        "ANYSLATE_TOKEN": "as_mcp_your_token_here"
      }
    }
  }
}

Getting a Token

1. Go to app.anyslate.io
2. Navigate to Settings > MCP Tokens
3. Click Create Token
4. Choose one access profile:
   • AI Memory automation for Claude, Cursor, Windsurf, and other agents
   • Markdown files only for normal .md workspace file management
   • Full access only when the same integration must do both
5. Copy the token (starts with as_mcp_)

MCP access requires an AnySlate Professional subscription.

The remote MCP server filters tools/list by token scope. A Memory token does not advertise Markdown resource CRUD tools, which keeps agents from using create_resource or update_resource when they should be calling import_chat, checkpoint_session, and upload_artifact.

Available Tools

The visible tool list depends on the token profile.

Resource tools (markdown files)

| Tool | Description | |------|-------------| | list_resources | List markdown files with pagination and folder filtering | | search_resources | Search files by name | | read_resource | Read file content and section structure | | get_resource_versions | View version history | | create_resource | Create new markdown files | | update_resource | Replace entire file content | | update_resource_section | Update a specific section by ID | | delete_resource | Delete a file |

Memory tools (AI Work Memory Layer)

| Tool | Description | |------|-------------| | list_memories / read_memory / search_memory | Browse and search captured chats | | import_chat | Spawn a new memory page from a fresh chat | | checkpoint_session | Append a turn / decision / task / artifact to a memory | | recall / find_matching_memory | Semantic search across all memories | | upload_artifact / get_artifact | Persist files, code, configs, images | | append_decision / append_task | Promote a single decision or task | | generate_continuation_prompt | Render a continuation seed for an existing memory | | get_checkpoint_status / get_context_subgraph / expand_decision / get_related / list_handles | Inspect graph and pending state |

Slash prompts (MCP prompts/list)

When your host surfaces MCP prompts as slash commands (Cursor, Claude Desktop, Claude Code, Windsurf), AnySlate exposes:

• /anyslate-new - paste-as-first-message capture seed for a fresh chat. The agent will spawn an AnySlate memory page and checkpoint every reply automatically.
• /anyslate-continue <memory_id> - continuation seed for an existing memory. Renders the canonical mcp_lite header + glossary + decisions + open tasks.

Optional arguments: topic (anyslate-new) and theme (both): general | coding | debugging | prd | strategy | marketing | research.

Repo scaffolding

npx @anyslate/mcp@latest setup-repo [path] [--force]

Drops AnySlate instruction files into the target directory:

| File | Picked up by | |------|--------------| | CLAUDE.md | Claude Code, Aider, generic CLAUDE.md-aware tools | | .cursor/rules/anyslate.md | Cursor (Project Rules) | | AGENTS.md | OpenAI Codex and other AGENTS.md-aware tools | | .windsurfrules | Windsurf workspace rules |

Each file contains the AnySlate standing rules: recall-before-answering, checkpoint-after-every-reply, upload-artifacts-first, optional handle. Existing files are skipped unless --force is passed; safe to re-run.

Important: MCP exposes the tools, but the repo rules tell the agent when to use them. Cursor and Windsurf need these rules for automatic memory behavior. Claude Code can also use lifecycle hooks from @anyslate/cli for background activity capture.

Requirements

• Node.js 18 or later
• AnySlate Professional subscription

Troubleshooting

"Node.js 18 or later is required" - The MCP SDK needs Node 18+. If you use nvm, set your default: nvm alias default 22. Or specify the full path in your config:

{
  "command": "/Users/you/.nvm/versions/node/v22.22.0/bin/npx",
  "args": ["-y", "@anyslate/mcp@latest"]
}

"TransformStream is not defined" - Same cause as above: you're running on Node <18. Update Node or use a full path.

"Missing ANYSLATE_TOKEN" - Set the ANYSLATE_TOKEN environment variable in your MCP client config.

"Invalid token format" - Tokens must start with as_mcp_. Generate one at app.anyslate.io.

"Invalid or expired token" - Your token may have been revoked or expired. Generate a new one.

"MCP access requires Professional subscription" - Upgrade at anyslate.io/pricing.

Documentation

Full documentation: anyslate.io/docs/mcp