Setup Guide

The Zwitch MCP Server is a hosted Streamable HTTP service. Point your AI assistant at the endpoint and you're done — no Docker, no local binary, no API keys.

Prerequisites

  • An MCP-compatible AI assistant (Claude Desktop, Claude Code, Cursor, VS Code, Gemini CLI, Windsurf, or any other client that speaks Streamable HTTP MCP).
  • For clients that only speak stdio (Claude Desktop, Cursor today), mcp-remote bridges stdio → HTTP. It runs via npx and needs Node.js LTS installed.

Endpoint

https://mcp.zwitch.io/mcp

Streamable HTTP transport. Use this URL in your client's MCP config. The 11 shipping tools require no authentication — send the request as-is.

Step 1 — Configure Your AI Assistant

Pick the section that matches your client.

Claude Code CLI

Terminal → Paste, then run:

claude mcp add --transport http zwitch --scope user https://mcp.zwitch.io/mcp

Claude Desktop

Settings → Developer → Edit Config, then add:

{
  "mcpServers": {
    "zwitch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zwitch.io/mcp"
      ]
    }
  }
}

Cursor

Settings → MCP tools → Add Custom MCP, then add:

{
  "mcpServers": {
    "zwitch": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zwitch.io/mcp"
      ]
    }
  }
}

Or use a project-scoped .cursor/mcp.json with the same content.

VS Code

Create .vscode/mcp.json at the project root (or add the entry to user settings):

{
  "servers": {
    "zwitch": {
      "type": "http",
      "url": "https://mcp.zwitch.io/mcp"
    }
  }
}

Requires GitHub Copilot Chat with MCP support enabled.

Gemini CLI

Add to ~/.gemini/settings.json (user) or .gemini/settings.json (project):

{
  "mcpServers": {
    "zwitch": {
      "httpUrl": "https://mcp.zwitch.io/mcp"
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "zwitch": {
      "serverUrl": "https://mcp.zwitch.io/mcp"
    }
  }
}

Step 2 — Restart Your Assistant

Most clients only pick up MCP config changes on restart. After restarting, your assistant should list 11 Zwitch tools.

The fastest way to verify:

"Run zwitch_setup and tell me which tools are available."

You should see 11 tools listed — 4 documentation tools and 7 integration-guide generators.

Step 3 — Try It

Some prompts to confirm everything works:

  • "Search the Zwitch docs for bulk transfer error codes."
  • "Generate the Node.js webhook handler for Zwitch."
  • "Read the doc on virtual account funding sources."

Team Sharing

To share configuration with a team, drop a .mcp.json at the project root and check it in:

{
  "mcpServers": {
    "zwitch": {
      "type": "http",
      "url": "https://mcp.zwitch.io/mcp"
    }
  }
}

Troubleshooting

SymptomLikely causeFix
Assistant doesn't list any Zwitch toolsConfig not reloadedFully quit and reopen the client
connection refused / timeoutEndpoint URL wrong, or behind a corporate proxyVerify the URL; configure proxy for npx mcp-remote if needed
Tools listed but zwitch_setup errorsServer-side issueRetry; if persistent, contact Zwitch

For anything else, contact [email protected].

Related