Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
MCP server for Slide's backup/BDR (business continuity/disaster recovery) API.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
SLIDE_API_TOKEN, MCP_TRANSPORT, AUTH_MODE, LOG_LEVELLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"slide": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SLIDE_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-ai/slide-mcp:v1.0.2"
],
"env": {
"SLIDE_API_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add slide --env SLIDE_API_TOKEN=your-value --env MCP_TRANSPORT=your-value --env AUTH_MODE=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e SLIDE_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-ai/slide-mcp:v1.0.2Completa los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"slide": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SLIDE_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-ai/slide-mcp:v1.0.2"
],
"env": {
"SLIDE_API_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"slide": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SLIDE_API_TOKEN",
"-e",
"MCP_TRANSPORT",
"-e",
"AUTH_MODE",
"-e",
"LOG_LEVEL",
"ghcr.io/wyre-ai/slide-mcp:v1.0.2"
],
"env": {
"SLIDE_API_TOKEN": "your-value",
"MCP_TRANSPORT": "your-value",
"AUTH_MODE": "your-value",
"LOG_LEVEL": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
MCP_TRANSPORT envAUTH_MODE envLOG_LEVEL envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub WYRE-AI, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: SLIDE_API_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.0.2) llegó al registro hace 17 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Docker en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Readfirst
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
What to read and check before changing a file: project rules, risks, checks and tests per file.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
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 to api.slide.tech. In gateway mode the token arrives per-request via the X-Slide-Api-Token header and a request missing that header is rejected. In local/stdio mode, and in HTTP AUTH_MODE=env, it's read from SLIDE_API_TOKEN.
Copy .env.example and set the variables below. Leave CONDUIT_S2S_SECRET empty in that file.
| Env var | Description | |||
|---|---|---|---|---|
SLIDE_API_TOKEN | Static bearer API token, issued in the Slide Console. Required for stdio and for HTTP AUTH_MODE=env. The gateway Compose service does not set it. | |||
MCP_TRANSPORT | stdio (default) or http. | |||
AUTH_MODE | env (default, reads SLIDE_API_TOKEN) or gateway (requires X-Slide-Api-Token on each /mcp request and never falls back to the environment). The Docker image and Compose file set gateway. | |||
CONDUIT_S2S_SECRET | Required for HTTP. HMAC key for X-Gateway-S2S on /mcp. Generate with openssl rand -hex 32. If this is empty or a known placeholder (changeme, your-s2s-secret, replace-with-a-real-secret, and the other public example values), the HTTP server logs an error and exits non-zero. The value is never logged. Compose will not start when it is unset or empty. | |||
MCP_ALLOW_INSECURE_DEV | Set to exactly 1 to start HTTP without CONDUIT_S2S_SECRET. Logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only (a wider MCP_HTTP_HOST is ignored). A known placeholder secret still refuses to start. Local development only. | |||
MCP_HTTP_HOST | Bind address when MCP_TRANSPORT=http. Defaults to 127.0.0.1. Honored when CONDUIT_S2S_SECRET is set. The container image sets 0.0.0.0. With no secret, the listener is 127.0.0.1 only. | |||
MCP_HTTP_PORT | HTTP port. Defaults to 8080. | |||
LOG_LEVEL | debug \ | info (default) \ | warn \ | error. |
/health and /healthz stay unauthenticated and do not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t= ,v1= , where the hex is HMAC-SHA256 of the literal string t= keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before the Slide token is read.
TS=$(date +%s)
SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}') curl -sS http://127.0.0.1:8080/mcp \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -H "X-Gateway-S2S: t=${TS},v1=${SIG}" \ -H "X-Slide-Api-Token: $SLIDE_API_TOKEN" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
In AUTH_MODE=gateway, /mcp also requires X-Slide-Api-Token. That header is the only credential source for the request. A missing header is HTTP 401 and does not fall back to SLIDE_API_TOKEN.
AUTH_MODE=env still requires a valid X-Gateway-S2S header, then uses SLIDE_API_TOKEN when the request does not carry X-Slide-Api-Token.
X-Gateway-S2S check and (in AUTH_MODE=gateway) the X-Slide-Api-Token presence check pass, a Content-Length above the cap returns 413 with a JSON-RPC error; bodies without Content-Length are capped by the MCP SDK transport. Unauthenticated requests still get 401 first.tools/call arguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return an isError tool result and are never dispatched.These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).
slide_list_accounts - list accounts, filterable by creation date.slide_get_account - get a single account by ID.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.slide_list_alerts - list alerts, filterable by device, agent, resolved status, and creation date.slide_get_alert - get a single alert by ID.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.slide_list_backups - list backup attempts, filterable by agent, snapshot, device, and time range.slide_get_backup - get a single backup attempt by ID.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.slide_list_clients - list clients (the MSP's end customers), filterable by creation date.slide_get_client - get a single client by ID.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.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).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.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.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.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.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).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.
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:
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, imaSolo se muestra el principio; lee el resto en el repo