Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "getdeck": {
      "type": "http",
      "url": "https://getdeck.co/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GETDECK_TOKEN}"
      }
    }
  }
}

claude mcp add --transport http getdeck https://getdeck.co/api/mcp --header "Authorization: Bearer ${GETDECK_TOKEN}"

[mcp_servers.getdeck]
url = "https://getdeck.co/api/mcp"
bearer_token_env_var = "GETDECK_TOKEN"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "getdeck": {
      "type": "remote",
      "url": "https://getdeck.co/api/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:GETDECK_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "getdeck": {
      "type": "http",
      "url": "https://getdeck.co/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GETDECK_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=getdeck&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2V0ZGVjay5jby9hcGkvbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyICR7R0VUREVDS19UT0tFTn0ifX0%3D"
}

{
  "servers": {
    "getdeck": {
      "type": "http",
      "url": "https://getdeck.co/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GETDECK_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "getdeck": {
      "httpUrl": "https://getdeck.co/api/mcp",
      "headers": {
        "Authorization": "Bearer ${GETDECK_TOKEN}"
      }
    }
  }
}

extensions:
  "getdeck":
    enabled: true
    name: "getdeck"
    type: streamable_http
    uri: "https://getdeck.co/api/mcp"
    headers:
      "Authorization": "Bearer ${GETDECK_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${GETDECK_TOKEN}. The registry never accepts secret values.

Quality 80 / 100good

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene64 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_themes (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_layouts (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_layout (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
pass
tools.token_costabout 1,384 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

7 tools, about 1,384 tokens to load them all · tool set 46b0f03123ba · checked 2026-10-20 07:21 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository

provenance55

liveness100

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-99% +updated-27d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://getdeck.co/api/mcp` streamable-http	api_key `${GETDECK_TOKEN}`	yes	99%	555 ms	2026-07-28	2026-10-20

Tools (7)

`export_pptx`	Turn a deck into a downloadable .pptx file. Requests like "make it a PowerPoint", "PPT로 뽑아줘", or "export this deck" mean this tool. Takes the layout ids and the text for each slot, and returns a signed download link. Coordinates come from our measurements, so the file matches what the gallery shows — but the boxes are fixed, so text longer than slots[].max_chars will be clipped.
`get_layout`	Return one layout as a ready-to-use, self-contained document: HTML, theme CSS, and its slot definitions. Call this once the user knows which layout they want, or with ids returned by suggest_deck.
`get_starter_kit`	Call this when joining several fetched layouts into one deck file. Requests like "merge these into one file", "bundle it as a deck", or "make it one HTML" mean this tool. Returns the base CSS, assembly rules, spacing tokens, and a viewport snippet for standalone viewing.
`get_theme`	Return one theme in full: its complete CSS and design tokens.
`list_layouts`	Search or filter the layout catalog to find a specific layout. Returns metadata only, no HTML. Also the tool for "what is new", "any new layouts?", "what got added since last month" - pass `since` and it returns only what landed after that date. If the user asked for a whole deck rather than one slide, call suggest_deck first instead of this.
`list_themes`	Search or filter the theme catalog. Returns metadata and key colors only, not the full CSS.
`suggest_deck`	Compose a deck and return a preview link the user can open in the browser right away. The user sees what the finished deck looks like without a single file being generated. Use this for requests like "make me a pitch deck", "I need a sales deck", "10 slides for an investor update", "put together a product overview", or "show me a deck outline" - anything where the user has a topic but has not picked layouts yet. ALSO use it when the user already has layouts in hand - "이 레이아웃들 모아서 프리뷰 만들어줘", "combine these layouts into a preview", "추천 프리뷰 만들어줘", "show these together as a deck" - pass them as layout_ids and it returns ONE deck preview link for the whole set. Never answer that kind of request with a list of individual layout links: one deck preview is the deliverable. Returns one theme + a slide order + the preview link, plus a `clarify` question to put to the user so the composition and theme are their call, not a guess. Always pass the preview link through to the user verbatim, ask clarify.question with its options, and wait for the answer - then call this tool again with deck_id / theme_id as clarify.answer_with says. Do not start generating files while a clarify question is unanswered. Once it is settled, fetch each layout id with get_layout, then call get_starter_kit to join them into one deck.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "studio.dodraft/getdeck",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://getdeck.co/api/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Bearer <api key>. Issue a key at https://getdeck.co/mypage after signing in."
        }
      ]
    }
  ],
  "version": "0.1.1",
  "websiteUrl": "https://getdeck.co",
  "description": "160+ finished slide layouts and 41 themes your agent can search, fetch and build a deck from"
}