Pika Plugins

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.

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:

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:

Then cursor-agent mcp login pika.

Codex CLI:

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  to target one agent, --all to install to every detected one.

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

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.

Claude Code on…