Authentication

Two authentication methods. Pick the one that fits your integration.

OAuth 2.1 (MCP & Interactive)

Best for: Claude Desktop, Cursor, Windsurf, and any MCP client. Also used by the web console.

OAuth handles authentication automatically. When you connect an MCP client to https://api.slideforge.dev/mcp, it triggers a Google sign-in flow. No API key needed.

Token refresh is automatic
Session lasts 1 hour of inactivity (7 days max)
$3 free credit provisioned on first login

API Key (Scripts & CI/CD)

Best for: Server-side integrations, automation, CI/CD pipelines, and any non-interactive use.

Create a key at Console → API Keys. Keys start with sf_live_.

Usage

curl https://api.slideforge.dev/v1/themes \
  -H "Authorization: Bearer sf_live_YOUR_KEY"

Keys don't expire (revoke anytime from Console)
One key per use case recommended (easier to rotate)
Never commit keys to version control

Which should I use?

Use case	Method
Claude Desktop, Cursor, Windsurf	OAuth (automatic)
Python/Node.js scripts	API key
CI/CD pipelines	API key
Custom MCP client	Either (OAuth preferred)
Web frontend	OAuth (via Auth0 session)

Base URLs

API: https://api.slideforge.dev

MCP: https://api.slideforge.dev/mcp

Web: https://slideforge.dev