Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for Slide's backup/BDR (business continuity/disaster recovery) API.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
SLIDE_API_TOKEN, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 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"
}
}
}
}在终端中运行这条命令
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.2运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"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"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
MCP_TRANSPORT envAUTH_MODE envLOG_LEVEL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日
注册名称已通过 GitHub 账户 WYRE-AI 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:SLIDE_API_TOKEN
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.2)于18天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Doricomcp
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Read and edit a live Dorico 6 score by conversation, through Dorico's own interfaces.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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, ima只显示了开头部分;其余内容请在仓库中阅读