mcp.film

mcp.film / Production Ops / Getty Images MCP Server

Getty Images MCP Server

OfficialRemoteby Getty Imagespaidverified Sep 17, 2026

Official remote MCP for searching and downloading licensed Getty stills and footage.

What it does

Getty Images' hosted MCP server, launched 12 Aug 2026, exposes the creative, editorial, news, sport, and archival library to agents: search stills and video, read asset metadata, and download files under your organization's existing licence. For a film team it is the licensed-archive counterpart to generative video — the route an agent takes when a cut needs real news footage, sports plates, or historical material that no model can lawfully fabricate. Tools are meant to be discovered at runtime rather than hard-coded.

Connect

Remote endpoint (Streamable HTTP)
https://mcp.gettyimages.com/v1
Claude Code
claude mcp add --transport http getty-images https://mcp.gettyimages.com/v1
Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "getty-images": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.gettyimages.com/v1"
      ]
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "getty-images": {
      "url": "https://mcp.gettyimages.com/v1"
    }
  }
}
Auth: oauth — API key and secret from your Getty Images account representative — https://engage.gettyimages.com/MCP-contact-sales

Field notes

Enterprise-gated, not self-serve: access needs an active Getty agreement (Premium Access or Editorial Subscription) or a reseller partnership, acceptance of the Web Service Terms, and an API key plus secret issued by an account rep — there is no signup link, only contact-sales. Re-checked 17 Sep 2026 and nothing has moved in five weeks: same endpoint, same 20-queries-per-second throttle, same OAuth 2.0 client-credentials or authorization-code handshake, and still no published header form, client config snippet, or tool names. So claude_code stays null until the connect recipe is public; point your agent at the server and let it read the auth and tool descriptions there. Getty asks explicitly that you not hard-code tool names or parameters, because they are still changing. The sharp edge is licensing, not plumbing: search spans the whole library while downloads are bounded by your subscription, so an agent can surface an asset it has no right to deliver — check the licence before you cut it in. Nothing here generates; for a self-serve licensed-footage route see stockfilm, and for stills-with-an-open-API see magnific.

Also in Production Ops

Pairs well with