Pika Creative Suite

Give any AI agent a face, a voice, and a full creative studio.
Image, video, music, editing — one identity, one auth, one bill, across every agent you use.

> /pika:podcast https://pika.art
  scraping page (capture_website)...
  writing 4-act script (Host A · Host B)...
  rendering 4 video acts × ~15s (native multi-shot)...
  done.
View video: https://cdn.pika.art/agent/.../podcast-final.mp4

Three independent ways to install

Pika ships as three independent surfaces. Pick one, mix two, or use all three — same Pika Agent identity, same auth, same credit pool across every install.

These aren't tiers — they're orthogonal mechanisms. A Claude Code user can pick the plugin, the skills, or just the raw MCP. A Cursor user picks skills + MCP. A custom agent picks just MCP.

Install

1. MCP — just the 58 atomic tools

The lightest install. No skill files written to disk. OAuth handles auth automatically on first tool call. Each client expects a slightly different shape — pick the one for your tool:

Claude Code / Claude Desktop — .mcp.json:

{ "mcpServers": { "pika": { "type": "http", "url": "https://mcp.pika.me/api/mcp" } } }

CLI equivalent: claude mcp add --transport http pika https://mcp.pika.me/api/mcp.

Cursor — ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). Cursor uses bare url, no type field:

{ "mcpServers": { "pika": { "url": "https://mcp.pika.me/api/mcp" } } }

Then cursor-agent mcp login pika.

Codex CLI:

codex mcp add pika --url https://mcp.pika.me/api/mcp

Claude.ai connectors — add the endpoint URL in Settings → Connectors. Any other MCP client — follow your client's docs for the config shape; the endpoint is always https://mcp.pika.me/api/mcp.

2. Skills — 9 curated workflows + MCP wiring

vercel-labs/skills detects your installed agents and writes each skill to the right path. Pass --agent <name> to target one agent, --all to install to every detected one.

npx skills add Pika-Labs/Pika-Plugins

Then add the MCP block from §1 to your agent. The skills assume the MCP server is registered as pika.

3. Claude plugin — marketplace install

claude plugin marketplace add Pika-Labs/Pika-Plugins
claude plugin install pika@pika-plugins

Full quit + reopen Claude Code, then run /mcp and authenticate pika. The plugin bundles the same 9 skills as §2 plus the MCP wiring — no separate claude mcp add.

{
  "extraKnownMarketplaces": {
    "pika-plugins": {
      "source": { "source": "github", "repo": "Pika-Labs/Pika-Plugins" }
    }
  },
  "enabledPlugins": {
    "pika@pika-plugins": true
  }
}

Authenticate

One time per install. Inside your agent, run /mcp, find pika, hit Authenticate. Your browser opens to the Pika sign-in page, the token caches locally, the MCP reconnects.

export MCP_AUTH_TOKEN="dk_..."
claude   # or cursor, codex, etc.

Featured workflows

Curated /pika:* skills (Surfaces §2 and §3) — one prompt to a finished, shareable video. All consume Pika credits.

Skills activate from natural language too — saying "make a podcast about https://pika.art" fires /pika:podcast automatically.

Capabilities — 58 atomic tools

Behind every curated skill is a flat tool surface (Surface §1) you can drive directly. Inside Claude Code the MCP tool prefix is mcp__plugin_pika_pika__*; other agents follow their own prefix convention. Counts are canonical primitives only — 9 deprecation aliases ship for back-compat but aren't counted.

Full schema → tools-manifest.json.

Requirements

• A Pika account (sign up at pika.me) — carries your persona, voice, avatar, and memory
• One of: an MCP-compatible client (any agent), a skill-aware agent (50+ supported), or Claude Code ≥ v2.0.12 (for the plugin path)

FAQ

How does pricing work? All generation consumes Pika credits from your Pika account. Free credits ship with every account; top up at pika.me. Atomic-tool calls and curated /pika:* skills draw from the same balance.

Is my voice clone, avatar, and memory private? Yes. Persona, cloned voice, avatar, and memory are scoped to your Pika account and accessible only to your authenticated MCP sessions. They are not used to train shared models. Manage or delete at pika.me.

Can I bring my own provider API keys? No — Pika manages provider routing internally so you don't juggle API keys, rate limits, or billing across vendors. One Pika account, one billing surface, every model.

Issues / questions → Pika-Labs/Pika-Plugins/issues

Links

• Changelog — release history
• Tool schema — all 58 atomic tools with full param surfaces
• Pika Developer Portal — keys and SDK references
• Security policy
• Open-source skill modules → Pika-Labs/Pika-Skills
• Pika consumer products — pika.me, iOS app

License

Apache 2.0 — see LICENSE. Speaks the open Model Context Protocol; finishing pipeline built on ffmpeg and Playwright.