Connect Decktify to Claude

Decktify ships an MCP server, so Claude Code and Claude Desktop can work with your decks directly: list them, edit slides, create share links, and read viewer analytics.

1. Create an API key

1. Log in to Decktify and open your dashboard.
2. Click API keys in the top right corner.
3. Name the key and click Create key. Copy it immediately, it is shown only once.

2. Add to Claude Code

Run this from inside the project folder you want connected, using the key from step 1:

cd /path/to/your-project
claude mcp add --scope local --transport http decktify https://decktify.com/api/mcp \
  --header "Authorization: Bearer dktf_YOUR_KEY"

--scope local registers the key for that folder only. Where you run the command decides which project gets it, so cd first, and give each project its own key. Run claude mcp list from inside the folder to confirm, and restart any session you already had open there.

Then ask Claude things like "list my decks", "what did viewers of the investor deck look at", or "create a share link for the board deck".

3. Add to Claude Desktop (optional)

Add this to claude_desktop_config.json. Unlike Claude Code, this config is machine-wide rather than per project, so it holds a single Decktify account:

{
  "mcpServers": {
    "decktify": {
      "type": "http",
      "url": "https://decktify.com/api/mcp",
      "headers": { "Authorization": "Bearer dktf_YOUR_KEY" }
    }
  }
}

4. Several accounts, or a shared repo (optional)

If you work across more than one Decktify account, or want teammates on the same repo to use their own key, check a .mcp.json into the repo that reads the key from an environment variable. The config travels with the project, the credential does not:

{
  "mcpServers": {
    "decktify": {
      "type": "http",
      "url": "https://decktify.com/api/mcp",
      "headers": { "Authorization": "Bearer ${DECKTIFY_API_KEY}" }
    }
  }
}

Available tools