Flickr logo flickr.com

Live

Flickr API and MCP server

Flickr's API keys are only for Pro subscribers, and commercial use needs a separate key from Flickr. Sign in to Flickr once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Flickr.

Flickr has no API for this. So we run one for you.

Flickr's own API, a GitHub MCP server and Cotlet compared
What you need Flickr's APIGitHub MCP serverCotlet
Tags, albums, privacy, comments No Partly Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Flickr changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 17, 2026. Sources: Flickr Help: Flickr API · Flickr Services: API methods · Flickr APIs Terms of Use · Zapier: Flickr triggers and actions

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Flickr in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Flickr to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Flickr and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/flickr with its own method and path, such as PUT /api/v1/flickr/photos/{photo_id}/privacy, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Flickr API and MCP server do?

13 tools on your own Flickr account. Agents call them as operations of the MCP tools flickr_read and flickr_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Flickr tools in Cotlet's MCP server and REST API
Tool What it does Access
list_albums Your albums with title, photo count and cover photo. read
list_photos Your photos, newest upload first, with title, tags, privacy and album membership. read
get_photo One photo with title, description, tags, privacy, albums, groups and counts. read
list_comments Comments on one photo or on your recent photos, oldest first, with author and whether you replied. read
list_groups Groups you belong to, with member count and whether you can add photos. read
update_photo Set a photo's title, description and tags. write
add_photo_to_album Add one of your photos to an album. write
remove_photo_from_album Take a photo out of an album without deleting it. write
create_album Create an album with a title and a first photo. writeasks first
upload_photo Upload a photo from a file URL with title, tags and a privacy setting. writeasks first
set_photo_privacy Choose who can see a photo: everyone, Friends, Family, both or only you. writeasks first
comment_on_photo Add a comment to a photo, as you. writeasks first
add_photo_to_group Add one of your photos to a group you belong to. writeasks first

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All Flickr use cases

Is it safe to connect Flickr?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Flickr API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Flickr is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Flickr have an API?

Flickr has a full REST API with methods for photos, albums, comments, groups and uploads, but no official MCP server (checked 17 Oct 2026). Only Flickr Pro subscribers can request new API keys, and commercial use needs a separate commercial key, by prior arrangement with Flickr.

How do I get access?

Sign up free, open Flickr under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Flickr yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Flickr sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_album, upload_photo, set_photo_privacy, comment_on_photo, add_photo_to_group wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agent make photos public by mistake?

Not by default. upload_photo defaults to private, and set_photo_privacy asks for your OK on every call until you switch that off for the tool. A non-public photo added to a group becomes visible to its members, so add_photo_to_group asks too.

Should I use a Flickr MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Flickr changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Flickr?

No. Cotlet is independent and not affiliated with Flickr.

Give your agent access to Flickr.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free