MCP · Model Context Protocol

MCP Server

Remote Streamable HTTP MCP at https://nanobananavideo.com/mcp. Your agent generates videos with the same credits as the Nano Banana studio. No REST API plan required.

Connector URL

MCP endpoint
https://nanobananavideo.com/mcp

Landing page and protocol share this URL. Browsers get the setup guide; agents POST JSON-RPC.

Authentication

OAuth 2.1 + PKCE, Claude custom connectors register dynamically, open the consent screen, and store a Bearer token. Metadata:

  • /.well-known/oauth-protected-resource
  • /.well-known/oauth-authorization-server

Personal token, from Dashboard → MCP. Send Authorization: Bearer nbmcp_…. REST API keys (nb_…) also work.

Cursor example

mcp.json
{
  "mcpServers": {
    "nano-banana-video": {
      "url": "https://nanobananavideo.com/mcp",
      "headers": {
        "Authorization": "Bearer nbmcp_YOUR_TOKEN"
      }
    }
  }
}

Tools

Tool What it does
get_accountPlan, credits, rate limits
list_modelsseedance2, veo3, sora2 and their limits
generate_text_to_videoPrompt → video (30–90s). Args: prompt, model, duration, aspect_ratio, resolution
generate_image_to_videoHTTPS image URL + motion prompt → video
get_video_statusPoll a video_id
list_videosRecent generations on this account

Credits & limits

MCP generations use your studio credits and the same adaptive rate limiter as the dashboard. Insufficient credits or a paused subscription return a tool error the agent can show to the user.

Visual setup guide: nanobananavideo.com/mcp