Back to Browse

Slide MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP server for Slide's backup/BDR (business continuity/disaster recovery) API.

About

MCP server for Slide's backup/BDR (business continuity/disaster recovery) API.

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-designed read-only MCP server for Slide's backup/DR API with strong security practices. The server implements deliberate secret-stripping sanitizers to prevent credential exposure (passphrases, IPsec PSKs, WireGuard keys, VNC/Samba passwords), uses proper authentication via bearer tokens with support for both environment variables and request-scoped gateway credentials, and strictly limits scope to non-mutating GET endpoints. Minor code quality issues around error handling and input validation do not materially impact security. Supply chain analysis found 4 known vulnerabilities in dependencies (2 critical, 0 high severity).

7 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Static bearer API token issued per-account in the Slide Console (Settings > API Keys). Sent as Authorization: Bearer <token> to api.slide.tech.Required

Environment variable: SLIDE_API_TOKEN

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-ai-slide-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "SLIDE_API_TOKEN": "your-slide-api-token-here"
      },
      "args": [
        "-y",
        "@wyre-ai/slide-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Slide MCP Server

MCP server for Slide's backup/BDR (business continuity/disaster recovery) API - account, agent, device, network, backup, snapshot, and restore visibility, for AI assistants and the WYRE Conduit gateway.

Authentication

Slide authenticates with a static bearer API token, issued per-account in the Slide Console (Settings > API Keys) - not OAuth. This connector never mints or refreshes anything: it only ever holds a live token, sent as Authorization: Bearer <token> to api.slide.tech. In gateway mode the token arrives per-request via the X-Slide-Api-Token header; in local/stdio mode it's read once from SLIDE_API_TOKEN.

Configuration

Env varDescription
SLIDE_API_TOKENStatic bearer API token, issued in the Slide Console.
MCP_TRANSPORTstdio (default) or http.
AUTH_MODEenv (default, reads the var above) or gateway (credential arrives per-request via the X-Slide-Api-Token header, injected by the Conduit gateway).
CONDUIT_S2S_SECRETWhen set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request.
LOG_LEVELdebug | info (default) | warn | error.

Tools

Accounts

  • slide_list_accounts - list accounts, filterable by creation date.
  • slide_get_account - get a single account by ID.

Agents

  • slide_list_agents - list agents (protected systems), filterable by device, client, type, and pairing date.
  • slide_get_agent - get a single agent by ID (backup schedule, retention, volumes, alert configs).
  • slide_search_agent_files - search the indexed file paths on an agent's protected system.
  • slide_get_agent_file_versions - get the snapshot versions available for a file path on an agent.
  • slide_get_agent_services - get the backed-up services detected on an agent.

Alerts

  • slide_list_alerts - list alerts, filterable by device, agent, resolved status, and creation date.
  • slide_get_alert - get a single alert by ID.

Audits

  • slide_list_audit_logs - list audit log entries, filterable by action, resource type, client, and time range.
  • slide_list_audit_actions - list the full set of audit action names.
  • slide_list_audit_resource_types - list the full set of audit resource type names.
  • slide_get_audit_log - get a single audit log entry by ID.

Backups

  • slide_list_backups - list backup attempts, filterable by agent, snapshot, device, and time range.
  • slide_get_backup - get a single backup attempt by ID.

Billing

  • slide_list_billing_credit_memos - list billing credit memos.
  • slide_list_billing_invoices - list billing invoices.
  • slide_list_billing_subscriptions - list subscriptions and device licenses.

Clients

  • slide_list_clients - list clients (the MSP's end customers), filterable by creation date.
  • slide_get_client - get a single client by ID.

Devices

  • slide_list_devices - list devices (physical/virtual Slide Boxes), filterable by client and creation date.
  • slide_get_device - get a single device by ID.
  • slide_get_device_network - get a device's network configuration.
  • slide_list_device_vlans - list a device's configured VLANs.
  • slide_get_device_vlan - get a single VLAN on a device by ID.

Networks

  • slide_list_networks - list disaster-recovery networks, filterable by client and creation date.
  • slide_get_network - get a single network by ID (port forwards, IPsec connections, WireGuard peers).

Restores (File)

  • slide_list_file_restores - list file restores, filterable by creation date.
  • slide_get_file_restore - get a single file restore by ID.
  • slide_browse_file_restore - browse the files/folders exposed by a file restore.
  • slide_list_file_restore_pushes - list push operations for a file restore, filterable by time range.
  • slide_get_file_restore_push - get the status of a single file restore push.

Restores (Image)

  • slide_list_image_exports - list image exports, filterable by creation date.
  • slide_get_image_export - get a single image export by ID.
  • slide_browse_image_export - browse the files/folders exposed by an image export.

Restores (Virtual Machine)

  • slide_list_virtual_machines - list virtual machines created from a snapshot, filterable by creation date.
  • slide_get_virtual_machine - get a single virtual machine by ID.

Snapshots

  • slide_list_snapshots - list snapshots, filterable by agent, location/deletion state, and time range.
  • slide_get_snapshot - get a single snapshot by ID.
  • slide_get_snapshot_service_verification - get service-verification results for a snapshot.

Users

  • slide_list_users - list users, filterable by creation date.
  • slide_get_user - get a single user by ID.
  • slide_get_user_avatar - get a user's avatar image (base64 data URL).

Scope

This is a deliberately read-only, non-credential-exposing v1 surface, covering all 43 of Slide's non-secret-exposing GET endpoints. Slide is backup/DR infrastructure - several of its real endpoints return live secrets, and every mutating endpoint is out of scope for v1. None of the excluded material is implemented here, by design, not by oversight. Every tool is classified isAdmin: true in the Conduit wiring, given the sensitivity of backup/DR infrastructure data (client environments, device inventories, network topology).

Secret-bearing fields - stripped from an otherwise-useful response, never implemented as a pass-through:

  • Agent.passphrases[].passphrase (the live agent-encryption passphrase) - stripped from slide_list_agents / slide_get_agent. The passphrase's name and agent_passphrase_id are kept.
  • Network.ipsec_conns[].psk (the live IPsec pre-shared key) - stripped from slide_list_networks / slide_get_network.
  • Network.wg_peers[].wg_private_key (the live WireGuard private key) - stripped from the same two tools. wg_public_key is not secret and is kept.
  • VirtualMachine.vnc_password (the live VNC password) - stripped from slide_list_virtual_machines / slide_get_virtual_machine. The vnc connection-info array (host/port/websocket URI) and vnc_enabled are not secret and are kept.
  • ImageExport.password (the live Samba password for the exported share) - stripped from slide_list_image_exports / slide_get_image_export. This field isn't one of Slide's headline "secret" endpoints, but it's the same class of live credential material as the four above, so it's held to the same bar.

Hard-excluded (mutating) - every POST/PATCH/PUT/DELETE endpoint, never implemented: creating/updating clients, networks, devices, agents, VLANs; starting backups; creating file/image/VM restores and push operations; managing IPsec connections, port forwards, and WireGuard peers; agent passphrase add/delete; device reboot/poweroff; and all other writes across every tag. This is real destructive/mutating infrastructure (delete client, delete network, delete restore, reboot device) - out of scope for v1 by design.

Out of v1 scope (not credential/provisioning, just not part of this connector's structured-data surface):

  • GET /v1/billing/credit-memo/{id}/pdf (BillingCreditMemoPDF) - returns raw application/pdf binary, not structured data.
  • GET /v1/billing/invoice/{id}/pdf (BillingInvoicePDF) - same.

They can be added as a follow-up if there's demand, after a deliberate scope decision - not by default.

Credential scope

This connector's own code is read-only by construction — but Slide also offers a real way to make the underlying credential read-only too, and we recommend using it.

Slide documents six account roles: Account Owner, Account Admin, Business Continuity Technician, Billing, and Read Only (read-only access to all resources). An API token inherits the role of whoever generates it in the Slide Console (Settings → API Keys).

Recommended: generate this connector's API token from a dedicated user with the Read Only role, not from an Account Owner/Admin user. This means that even if the token is ever exposed outside Conduit's control (a credential-store compromise, a misconfigured log, etc.), it cannot be used to delete backups, restores, networks, or devices — matching this connector's own read-only code with a read-only credential, rather than relying on the connector's code as the only safeguard.

Two separate claims, kept at different confidence levels:

  • Structurally verified (checked directly, stated with full confidence): this connector's own code makes zero mutating calls (client.ts has exactly one HTTP verb function, doGet), and strips five live secret fields (agent passphrase, IPsec PSK, WireGuard private key, VM VNC password, image-export Samba password) from every response before it reaches a tool result — see secret-redaction.test.ts.
  • Vendor-documented, not independently verified (hedged deliberately): whether the Read Only role's restriction is enforced server-side against every mutating endpoint (vs. merely hidden in the console UI) has not been tested against a live Read Only account. This role is also opt-in, not default — a token from an Account Owner/Admin user (the common case for a fresh account) has no such restriction.

Do not read this connector, or this README, as having established that every Slide token is read-only — only that this connector's own code never attempts a mutation, and that Slide offers (but does not default to) a way to make the credential itself read-only as well.

Development

npm install
npm run build
npm test
npm run lint   # tsc --noEmit

Docker

docker build -t slide-mcp .
docker run -p 8080:8080 -e SLIDE_API_TOKEN=... slide-mcp

Reviews

No reviews yet

Be the first to review this server!