Skip to main content

​
Quick Start

​
Prerequisites

  • Node.js 18+ installed
  • A TagadaPay API key with read scope (Settings → API Keys in the dashboard)
The API key never leaves your machine — the MCP server sends it directly to api.tagada.io over HTTPS. We recommend a key scoped to read only.

​
Setup for Cursor

Add this to .cursor/mcp.json in your project (or in your global Cursor settings): 
{
  "mcpServers": {
    "tagada-crm": {
      "command": "npx",
      "args": ["-y", "@tagadapay/crm-mcp"],
      "env": {
        "TAGADAPAY_API_KEY": "sk_live_..."
      }
    }
  }
}
Cursor will start the MCP server automatically and inject the API key via env.

​
Setup for Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows): 
{
  "mcpServers": {
    "tagada-crm": {
      "command": "npx",
      "args": ["-y", "@tagadapay/crm-mcp"],
      "env": {
        "TAGADAPAY_API_KEY": "sk_live_..."
      }
    }
  }
}
Restart Claude Desktop after saving.

​
Setup for Windsurf

Add to ~/.codeium/windsurf/mcp_config.json: 
{
  "mcpServers": {
    "tagada-crm": {
      "command": "npx",
      "args": ["-y", "@tagadapay/crm-mcp"],
      "env": {
        "TAGADAPAY_API_KEY": "sk_live_..."
      }
    }
  }
}

​
Manual start (any MCP client)

If your tool doesn’t auto-start MCP servers, run it manually: 
TAGADAPAY_API_KEY=sk_live_... npx -y @tagadapay/crm-mcp
The server speaks the standard stdio MCP transport. Configure your MCP client to connect to it via stdio.

​
Verify the connection

Once connected, ask your agent:
“What payment processors do I have configured?”
The agent should call processors.list and return your processors with their active flag, currencies, and countries. If you get an error like unauthorized or invalid_api_key, double-check that the key is set and has read scope.

​
Configuration

Env varRequiredDefaultDescription
TAGADAPAY_API_KEYYes—Your API key with read scope
TAGADAPAY_BASE_URLNohttps://api.tagada.ioOverride for staging / self-hosted

​
Multiple accounts

If you manage several TagadaPay accounts, register one MCP server per account with distinct names: 
{
  "mcpServers": {
    "tagada-crm-acme": {
      "command": "npx",
      "args": ["-y", "@tagadapay/crm-mcp"],
      "env": { "TAGADAPAY_API_KEY": "sk_live_acme_..." }
    },
    "tagada-crm-globex": {
      "command": "npx",
      "args": ["-y", "@tagadapay/crm-mcp"],
      "env": { "TAGADAPAY_API_KEY": "sk_live_globex_..." }
    }
  }
}
The agent will see both surfaces and can be told which to use (“check Acme’s processors”).

​
Next steps