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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
MCP_TRANSPORT envAUTH_MODE envLOG_LEVEL env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 WYRE-AI 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: SLIDE_API_TOKEN
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.2)은 16일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Docker도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Tethered Trust
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:↓ 주간 다운로드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.
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요