Skip to content
FIGGSHIELD

Figgshield overview

What Figgshield is — an MCP server and CLI tool for generating video with Kling and images with Nano Banana 2 inside Claude — plus a five-minute quickstart to add it and generate.

View as Markdown

Figgshield is an MCP server and CLI tool. You add it to Claude (as a connector) or the Claude Code CLI, then generate video with Kling and images with Nano Banana 2 by asking in plain language. Figgshield runs the job, meters the credits, and hands back a file. The web app is only for account management — signing in, choosing a plan, and managing API keys.

There are two models and one credit balance:

ModelKindCreditsOptions
Klingvideo35 (5s) · 70 (5s + audio or 10s)durations 5/10s, 720p/1080p, optional audio
Nano Banana 2image81K / 2K / 4K

Ways to use it

SurfaceHowAuth
Claude (Desktop / web)Add Figgshield as a connector under Settings → ConnectorsBrowser sign-in (OAuth)
Claude Code CLIclaude mcp add --transport http figgshield https://api.figgshield.ai/mcpclaude mcp login (OAuth) or an API key header
REST API (non-MCP)POST https://api.figgshield.ai/api/generations/create/Authorization: Bearer figg_... API key

Everything shares one account, one plan and one credit balance.

Every page of this documentation has a Markdown twin at the same URL with .md appended (this page: /documentation/index.md). There is also an llms.txt index, the complete docs in one file, and a machine-readable OpenAPI 3.1 specification.

Five-minute quickstart: add to Claude and generate

You need a Figgshield account with an active subscription — any plan works. Sign in at the app with Google, Apple or GitHub and pick a plan; then connect Claude.

1. Add the connector

In Claude Desktop or claude.ai, open Settings → Connectors → Add custom connector and paste the MCP endpoint:

https://api.figgshield.ai/mcp

Claude opens a browser sign-in. Approve the two scopes (figgshield:read, figgshield:write) and the connector is ready. See MCP server & tools for the full walkthrough, the config JSON and every tool.

2. Ask for a generation

Prompt Claude in plain language:

Generate a 5-second video of a quiet harbour at dawn, mist lifting off the water.

Claude calls Figgshield’s generate_video tool, which runs Kling, spends 35 credits, and returns a generation id plus an output_url once the clip is ready. For an image, just ask for one — Claude calls generate_image, which runs Nano Banana 2 for 8 credits.

3. Get the file

Video jobs take tens of seconds; Claude polls get_generation for you and hands back the download link. Images usually return in one step. Ask Claude to “show my recent generations” and it calls list_library; ask “how many credits do I have left” and it calls get_usage.

That is the whole loop: connect once, then ask. No keys to paste, nothing to poll by hand.

Prefer the CLI or a script?

  • Claude Code CLIclaude mcp add then claude mcp login, or a personal API key header.
  • Generations (REST) — the non-MCP path: create a key, POST a job, poll it, download the output.

Where to go next

  • MCP server & tools — add the connector, the five tools, example prompts, config JSON.
  • Claude Code CLI — loopback sign-in and the API-key alternative.
  • Authentication — SSO sign-in, OAuth for the connector, personal API keys.
  • Models — Kling and Nano Banana 2, parameters and credit costs.
  • Generations (REST) — the full REST job lifecycle for non-MCP clients.
  • Usage & credits — usage summary and the credit ledger.
  • Billing & top-ups — the four plans, annual billing, and top-ups.
  • Errors — every machine code, its HTTP status, and what to do about it.