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)

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

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 5 skills as §2 plus the MCP wiring — no separate claude mcp add.

<details> <summary>Claude Code on the web (claude.ai/code)</summary>

Add this to your repo's .claude/settings.json, commit, and push — cloud sessions auto-install at startup:

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

mcp.pika.me isn't in the default Trusted allowlist — switch the environment's network access to Full, or use Custom with mcp.pika.me added. (Anthropic network access docs)

</details>

2. Skills — 5 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.

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