Getting Started with MCP

Set up MCP integration in under 5 minutes. This guide walks you through creating an API token and connecting to your favorite AI assistant.

Create an API Token

Open the AnySlate desktop app and navigate to your account settings to create an MCP API token:

Click on your profile icon in the top-right corner
Select Account Settings from the menu
Click on API Tokens in the sidebar
Click the + New Token button
Give your token a descriptive name (e.g., "Claude Desktop")
Select the scopes you need: read, write, and/or search
Set an expiration date (optional)
Click Create Token

Important: Copy your token immediately. It will only be shown once! The token starts with as_mcp_.

Install the Package

The @anyslate/mcp npm package works with any MCP client. No manual setup needed — just add it to your client config:

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

See detailed setup for your specific client:

View all 10+ supported clients

Test the Connection

After configuring your client, restart it and try asking about your files:

"List all my AnySlate files"

You should see a response listing your workspace files. If you get an error, check that:

You have Node.js 18+ installed (run node --version to check)
The token is correct and not expired
Your account has a Professional subscription
Your client has been restarted after configuration
If using nvm, GUI apps may not see your shell's Node version — use the full path to npx or install Node via Homebrew

npm Package

npx -y @anyslate/mcp

Requires Node.js 18+. View on npm

Troubleshooting

"Server disconnected" or "TransformStream is not defined"

This means npx is running on Node.js 16 or older. The @anyslate/mcp package requires Node.js 18+.

Common cause: If you use nvm, GUI apps like Claude Desktop and Cursor don't load your shell profile, so they may use an older system Node instead of your nvm-managed version.

Quick fixes

Use the full path to npx in your config

"command": "/Users/you/.nvm/versions/node/v24.x.x/bin/npx"

Find your path: ls ~/.nvm/versions/node/

Or symlink to /usr/local/bin for system-wide access

sudo ln -sf ~/.nvm/versions/node/v24.x.x/bin/node /usr/local/bin/node
sudo ln -sf ~/.nvm/versions/node/v24.x.x/bin/npx /usr/local/bin/npx
sudo ln -sf ~/.nvm/versions/node/v24.x.x/bin/npm /usr/local/bin/npm

Or install Node via Homebrew

brew install node

Homebrew places Node in a GUI-visible path automatically.

After fixing, clear the npx cache (rm -rf ~/.npm/_npx) and restart your client. See the full troubleshooting guide for details.

Missing ANYSLATE_TOKEN

Set the ANYSLATE_TOKEN environment variable in your MCP client config's env block.

Invalid token format

Tokens must start with as_mcp_. Generate one from the API Tokens page.

Invalid or expired token

Your token may have been revoked or expired. Generate a new one from the desktop app.

Professional subscription required

MCP access is a Professional tier feature. Upgrade here.

Ready for More?

Learn about token scopes, audit logging, and security best practices.

Token Management Security

Back to MCP Overview API Tokens