MCP Gateway

Connect Claude to all MSP tools through a single hosted gateway at mcp.wyretechnology.com. No Docker, no config files — just add one URL and authenticate.

How It Works

1. Add the unified gateway URL as an MCP server in Claude Code or Claude Desktop (see below)
2. Claude initiates a single OAuth 2.1 + PKCE flow — a browser window opens
3. Log in or sign up, then connect your vendor API credentials via the web UI
4. The gateway validates your credentials, then encrypts and stores them (AES-256-GCM)
5. All vendors are available through the single connection — tool names are prefixed with the vendor (e.g., autotask__list_tickets)

Supported Vendors

All vendors below are available through the unified endpoint at https://mcp.wyretechnology.com/v1/mcp. You only need to connect the vendors you use — the gateway automatically discovers which vendors you have credentials for.

Claude Code (CLI)

Claude Code supports remote MCP servers natively. Add a .mcp.json to your project root:

// .mcp.json (in your project root)
{
  "mcpServers": {
    "mcp-gateway": { "url": "https://mcp.wyretechnology.com/v1/mcp" }
  }
}

On first use, Claude Code will open a browser for OAuth authentication. After that, all connected vendors are available automatically.

Claude Desktop

Claude Desktop setup has two parts: installing the plugin (skills, commands, and domain knowledge) and adding the MCP server (the API connection to the gateway).

Step 1: Install the Plugin via Cowork

Install the MSP Claude Plugins through the Cowork plugin marketplace:

1. Click the Cowork icon in the bottom-left of Claude Desktop
2. Click the + button
3. Click Plugins
4. Click Add Plugin
5. Click Personal
6. Click the + button
7. Click Add marketplace from Github
8. Enter the repo owner/URL:

9. Click Sync

This installs all plugin skills, commands, and MSP domain knowledge into Claude Desktop.

Step 2: Add the MCP Gateway Server

Quick Install (Recommended)

Run one command to automatically configure Claude Desktop. The installer preserves your existing config, creates a backup, and only appends the gateway entry.

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/wyre-technology/msp-claude-plugins/main/msp-claude-plugins/wyre-gateway/install.sh | bash

Windows (PowerShell):

irm https://raw.githubusercontent.com/wyre-technology/msp-claude-plugins/main/msp-claude-plugins/wyre-gateway/install.ps1 | iex

The installer also detects Claude Code CLI and configures it automatically. A backup of your existing claude_desktop_config.json is saved to .bak before any changes.

Manual Configuration

Alternatively, add a single entry to your claude_desktop_config.json that connects to all vendors at once. Claude Desktop uses stdio-based transports, so the remote gateway requires the mcp-remote bridge:

// claude_desktop_config.json
{
  "mcpServers": {
    "mcp-gateway": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wyretechnology.com/v1/mcp"]
    }
  }
}

That's it — one entry for all vendors. On first use, a browser will open for OAuth authentication. After that, add your vendor credentials via the gateway web UI at mcp.wyretechnology.com.

Config File Location

Requires Node.js 18+. The npx -y mcp-remote command downloads the bridge automatically on first run. If the file doesn't exist yet, create it with the JSON content above. Restart Claude Desktop after editing.

Claude.ai (Web) — Connectors UI

Claude Pro, Team, and Enterprise users can connect the gateway directly from claude.ai — no config files or CLI needed:

1. Click Customize in the left sidebar
2. Click Connectors
3. Click the + button, then Add custom connector
4. Enter a name (e.g. MCP Gateway)
5. Enter the Remote MCP server URL: https://mcp.wyretechnology.com/v1/mcp
6. Click Add
7. Complete the OAuth login flow when prompted

After setup, all your connected vendors are available immediately in any conversation. The same flow also works in Claude Desktop via Settings → Connectors → Add Connector.

Per-Vendor Endpoints (Legacy)

The per-vendor endpoints (/v1/{vendor}/mcp) are still available but deprecated. They require a separate OAuth flow and config entry for each vendor, which can cause connection timeouts when multiple flows run simultaneously. We recommend migrating to the unified endpoint above.

// .mcp.json — per-vendor (legacy)
{
  "mcpServers": {
    "autotask": { "url": "https://mcp.wyretechnology.com/v1/autotask/mcp" },
    "datto-rmm": { "url": "https://mcp.wyretechnology.com/v1/datto-rmm/mcp" }
  }
}

// claude_desktop_config.json — per-vendor (legacy)
{
  "mcpServers": {
    "autotask": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wyretechnology.com/v1/autotask/mcp"]
    },
    "datto-rmm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.wyretechnology.com/v1/datto-rmm/mcp"]
    }
  }
}

Security

• OAuth 2.1 + PKCE — industry-standard authentication with mandatory code challenge
• AES-256-GCM encryption — credentials encrypted at rest with per-user key derivation (PBKDF2, 100k iterations, SHA-512)
• Refresh token rotation — old tokens revoked on every use
• No credential exposure — vendor API keys never leave the gateway; injected as HTTP headers on the internal network

Local Alternative

If you prefer to keep credentials on your own machine, you can run individual MCP servers locally instead of using the hosted gateway. See the deployment guide for Docker, npx, and MCPB bundle options.