WYRE MCP Gateway

Connect Claude to all MSP tools through a single hosted gateway at conduit.wyre.ai. 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 Connections

Every connection is available through the unified endpoint at https://conduit.wyre.ai/v1/mcp. You only need to connect the vendors you use — the gateway automatically discovers which ones you have credentials for.

Each vendor's tools are namespaced with a <vendor>__ prefix — for example autotask__list_tickets, datto-rmm__list_devices, or m365__list_users.

See the full connections catalog → for the complete, always-current list of supported vendors and the tools each one provides.

Claude Code (CLI)

One command adds the gateway to Claude Code. Run this in your terminal — no config files to edit:

Add for all projects (recommended)

Use --scope user to make the gateway available in every Claude Code session on this machine:

claude mcp add --scope user --transport http msp-mcp-gateway https://conduit.wyre.ai/v1/mcp

Add for the current project only

Omit --scope to scope the gateway to the current project (writes to .mcp.json in the project root):

claude mcp add --transport http msp-mcp-gateway https://conduit.wyre.ai/v1/mcp

On first use, Claude Code will open a browser for OAuth authentication. After signing in, connect your vendor credentials at conduit.wyre.ai — all connected vendors are then available automatically.

Verify the install

claude mcp list

You should see msp-mcp-gateway in the list. To remove it later, run claude mcp remove msp-mcp-gateway.

// .mcp.json (in your project root) — manual alternative
{
  "mcpServers": {
    "msp-mcp-gateway": {
      "type": "http",
      "url": "https://conduit.wyre.ai/v1/mcp"
    }
  }
}

Claude Desktop

Part 1: Install the Plugin via the Cowork Marketplace

The plugin gives Claude Desktop the MSP skills and slash commands (e.g. /search-tickets, /create-ticket). Add it from the Cowork marketplace UI:

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:
   wyre-technology/msp-claude-plugins
9. Click Sync — all plugin skills and commands are now installed

Part 2: Add the WYRE MCP Gateway Server

Pick one of the two options below — you only need to do this once.

Option A: Connectors UI (easiest — no CLI, no config files)

If you're on Claude Pro, Team, or Enterprise, add the gateway directly from Claude Desktop's built-in Connectors UI:

1. Open Claude Desktop → Settings → Connectors
2. Click Add Connector (or Add custom connector)
3. Name it MSP Gateway (or anything you like)
4. Remote MCP server URL: https://conduit.wyre.ai/v1/mcp
5. Click Add, then complete the OAuth login in the browser that opens

After OAuth completes, connect your vendor credentials at conduit.wyre.ai. All connected vendors become available immediately.

Option B: Manual Configuration

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

// claude_desktop_config.json
{
  "mcpServers": {
    "msp-mcp-gateway": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://conduit.wyre.ai/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 conduit.wyre.ai.

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)

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. MSP Gateway)
5. Enter the Remote MCP server URL: https://conduit.wyre.ai/v1/mcp
6. Click Add, then complete the OAuth login flow when prompted

After setup, all your connected vendors are available immediately in any conversation.

Claude Team & Enterprise — Organization-Wide Setup

On Claude Team and Enterprise plans, an organization owner adds the gateway once and every member can use it:

1. Admin: go to Organization settings → Connectors
2. Click Add, then Custom → Web
3. Enter a name (e.g. MCP Gateway) and the Remote MCP server URL: https://mcp.wyretechnology.com/v1/mcp
4. Leave the Advanced settings (OAuth Client ID / Client Secret) empty — see the warning below
5. Click Add
6. Each member: go to Customize → Connectors, find the connector, click Connect, and complete the browser sign-in to the gateway

Every member authenticates to the gateway individually with their own account. The gateway resolves that member's personal vendor credentials first, then falls back to the team's shared credentials. The typical Team rollout is: the gateway team owner adds shared vendor credentials once, the Claude org admin adds the connector once, and every member just clicks Connect — no credentials are ever typed into Claude itself.

Service Clients — API & Automation Access

Service client credentials (a svc_… client ID plus secret) are for machine-to-machine access where no browser sign-in is possible: the Claude API's MCP connector, CI pipelines, scheduled agents, and scripts. They are not usable in Claude Desktop or claude.ai connectors. Mint a short-lived access token (1 hour) with the OAuth client_credentials grant:

curl -X POST https://mcp.wyretechnology.com/oauth/token \
  --data-urlencode 'grant_type=client_credentials' \
  --data-urlencode 'client_id=svc_YOUR_CLIENT_ID' \
  --data-urlencode 'client_secret=YOUR_CLIENT_SECRET'

Then pass the returned access_token as a Bearer token. For example, with the Claude API's MCP connector:

{
  "mcp_servers": [{
    "type": "url",
    "url": "https://mcp.wyretechnology.com/v1/mcp",
    "name": "mcp-gateway",
    "authorization_token": "<access_token from /oauth/token>"
  }]
}

Tokens expire after one hour — automation should mint a fresh token per run rather than storing one. Service clients act with your team's shared credentials.

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://conduit.wyre.ai/v1/autotask/mcp" },
    "datto-rmm": { "url": "https://conduit.wyre.ai/v1/datto-rmm/mcp" }
  }
}

// claude_desktop_config.json — per-vendor (legacy)
{
  "mcpServers": {
    "autotask": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://conduit.wyre.ai/v1/autotask/mcp"]
    },
    "datto-rmm": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://conduit.wyre.ai/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
• Per-team tool scoping — narrow which vendor tools a team can call beneath the org-level allowlist; see Per-Team Tool Access

If something goes wrong

Common issues — missing tools after adding a vendor, "Failed to update tool access" when saving allowlists, OAuth failures — are documented in the Troubleshooting guide. If you'd rather have Claude diagnose the issue, install the wyre-gateway-troubleshooting skill from the shared-skills plugin.

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.