Expose 2slides.com tools for MCP clients (e.g., Claude Desktop).

Before using this MCP server, you need to obtain an API key from 2slides.com/api.

Edit ~/Library/Application Support/Claude/claude_desktop_config.json and add:

{
  "mcpServers": {
    "2slides": {
      "command": "npx",
      "args": ["2slides-mcp"],
      "env": {
        "API_KEY": "YOUR_2SLIDES_API_KEY"
      }
    }
  }
}

Then fully restart Claude Desktop. In a chat, open the tools panel and you should see the tools below.

• slides_generate (POST /api/v1/slides/generate)

  • Args: themeId (string), userInput (string), responseLanguage (string), mode (optional: sync | async, default sync)
  • Example:

    {
      "themeId": "st-1756528793701-fcg5fblt2",
      "userInput": "generate sample content",
      "responseLanguage": "English",
      "mode": "async"
    }

  • Notes:
    • mode: "sync" waits for generation to complete and returns the result directly (default).
    • mode: "async" submits the job and returns a jobId; poll with jobs_get.

• jobs_get (GET /api/v1/jobs/{jobId})

  • Args: jobId (string)
  • Example:

    { "jobId": "D8h9VYDGdTlZ6wWSEoctF" }

• themes_search (GET /api/v1/themes/search)

  • Args: query (string), limit (number, optional, max 100)
  • Example:

    { "query": "8 stages", "limit": 10 }

All tools return the 2slides API JSON as formatted text. Use jobs_get with the jobId from slides_generate to poll status or get the downloadUrl when available.

• If tools don’t appear in Claude, verify the config path is absolute and restart the app.
• Check Claude MCP logs:

tail -n 50 -f ~/Library/Logs/Claude/mcp*.log

• For stdio MCP servers, avoid logging to stdout; this server only logs errors to stderr. See the official guidance below.

• Build an MCP server (official docs): https://modelcontextprotocol.io/docs/develop/build-server
• 2slides: https://www.2slides.com
• 2slides Templates: https://www.2slides.com/templates