Client Setup

Configure AnySlate MCP with your favorite AI tool. Select a client below for setup instructions.

The @anyslate/mcp npm package provides universal compatibility with any MCP client. You need an API token from the API Tokens page and the config format for your client.

npm package

npx -y @anyslate/mcp

Select client

Claude Desktop

macOS / Windows / Linux

Setup Steps

1Open Claude Desktop → Settings → Developer → Edit Config
2Add the configuration below to the JSON file
3Replace the token placeholder with your actual token
4Restart Claude Desktop - AnySlate tools will appear automatically

Configuration File

~/Library/Application Support/Claude/claude_desktop_config.json

Configuration

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

Windows path: %APPDATA%\Claude\claude_desktop_config.json

Troubleshooting

"Server disconnected" or "TransformStream is not defined"

This is the most common setup issue. It means npx is running on Node.js 16 or older, which lacks APIs the MCP SDK requires (like TransformStream and native fetch). The package requires Node.js 18 or later.

Why does this happen?

If you use nvm (Node Version Manager), it only sets the Node version inside interactive shell sessions (terminals). GUI apps like Claude Desktop, Cursor, and VS Code are launched by macOS directly and do not load your shell profile (.zshrc / .bashrc), so they may resolve npx to an older Node version that was installed system-wide or is first in the default macOS PATH.

How to check

# Check your terminal's Node version
node --version

# Check what the system sees (what GUI apps use)
/usr/local/bin/node --version 2>/dev/null || echo "No system node"

# Check nvm default
nvm alias default

Fix options (pick one)

Option 1: Use the full path in your config (recommended)

Point directly to the Node 22+ or 24+ npx binary. This bypasses PATH resolution entirely and always works.

{
  "mcpServers": {
    "anyslate": {
      "command": "/Users/you/.nvm/versions/node/v24.x.x/bin/npx",
      "args": ["-y", "@anyslate/mcp"],
      "env": { "ANYSLATE_TOKEN": "as_mcp_your_token_here" }
    }
  }
}

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

Option 2: Symlink Node to /usr/local/bin

This makes your preferred Node version visible to all GUI apps system-wide, so "command": "npx" works everywhere without full paths.

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

Verify with: /usr/local/bin/node --version

Option 3: Install Node via Homebrew

Homebrew installs Node to /opt/homebrew/bin (Apple Silicon) or /usr/local/bin (Intel), both of which GUI apps can see automatically.

brew install node

This gives you a system-wide Node that works alongside nvm. Your nvm-managed versions still take priority in terminal sessions.

Clear the npx cache

After fixing your Node version, clear the npx cache to ensure the latest package version is downloaded:

rm -rf ~/.npm/_npx

Then restart your MCP client. The package will be re-downloaded with the correct Node runtime.

Server not appearing

Fully restart your client after adding the config - a window reload is often not enough.

Authentication errors

Verify your token is correct and hasn't expired. Confirm your account has a Professional subscription.

Connection timeout

If behind a corporate firewall, configure a proxy or use a VPN to reach mcp.anyslate.io.

Invalid JSON config

Validate your JSON with a linter. Missing commas and trailing commas are the most common mistakes.