[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Flickr API and MCP server

> 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.

Photo sharing site where members upload photos, sort them into albums, tag them, set who can see each one and share them in groups.

## What is the Flickr API?

Cotlet's Flickr API exposes 13 endpoints for your own Flickr account: list albums, list photos, get photo, list comments, list groups, update photo, add photo to album, remove photo from album, create album, upload photo, set photo privacy, comment on photo and add photo to group. The list_albums endpoint returns your albums with title, photo count and cover photo. Each endpoint takes simple JSON inputs like photo_id, limit or cursor and works both as an operation of the flickr_read or flickr_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 13 (5 read, 8 write)
- **Updated:** 2026-10-22

Flickr has a full REST API with methods for photos, albums, comments, groups and uploads, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Flickr with 13 endpoints (5 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Flickr have an official 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.

| Task | Flickr official | Cotlet |
|---|---|---|
| List albums and the photos in them | Yes: Flickr API; needs a key from a Pro account and your own paging | Yes |
| Read a photo with its tags and privacy | Yes: Flickr API | Yes |
| Upload a photo | Yes: Flickr API upload endpoint, with an asynchronous mode | Yes |
| Edit title, description and tags | Yes: Flickr API; no MCP server for agents | Yes |
| Create albums and move photos between them | Yes: Flickr API photoset methods | Yes |
| Change who can see a photo | Yes: Flickr API | Yes |
| Comment on a photo or reply to a comment | Yes: Flickr API comment methods | Yes |
| Add a photo to a group pool | Yes: Flickr API group pool methods | Yes |

Sources: [Flickr Help: Flickr API](https://www.flickrhelp.com/hc/en-us/articles/4404070036884-Flickr-API), [Flickr Services: API methods](https://www.flickr.com/services/api/), [Flickr APIs Terms of Use](https://www.flickr.com/help/terms/api), [Zapier: Flickr triggers and actions](https://zapier.com/apps/flickr/integrations)

## For AI agents

```text
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.
Cotlet provides a hosted MCP server and REST API for Flickr: 13 tools (5 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=flickr, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    flickr_read, flickr_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/flickr, each operation at its own route, e.g. PUT /api/v1/flickr/photos/{photo_id}/privacy
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_albums, list_photos, get_photo, list_comments, list_groups, update_photo, add_photo_to_album, remove_photo_from_album, create_album, upload_photo, set_photo_privacy, comment_on_photo, add_photo_to_group
Confirm      create_album, upload_photo, set_photo_privacy, comment_on_photo, add_photo_to_group (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/flickr-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=flickr, requests Flickr in the Cotlet console and creates an API key there.
2. The user signs in to Flickr once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Flickr for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Flickr server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Flickr MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Flickr in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Flickr only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Flickr login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Flickr's terms; Cotlet is not affiliated with Flickr.
```

## What can an AI agent do in Flickr?

Cotlet is best for photographers and small studios on Flickr who need tagging, albums, privacy and comment replies done by their AI agent without running or fixing a server.

- **[Tag and title new photos](https://cotlet.dev/integrations/flickr-api-mcp-server/tag-and-title-photos.md)** (runs: weekly): "Find photos I uploaded in the last 7 days with no tags, look at each one, and add a clear title and 5 to 8 tags. Keep titles I already wrote." → `list_photos`, `get_photo`, `update_photo`
- **[Sort photos into albums](https://cotlet.dev/integrations/flickr-api-mcp-server/sort-photos-into-albums.md)** (runs: weekly): "Look at the photos from my last 7 days that are in no album. Group them by place and date, create an album for each new group and move the photos in. Show me the plan first." → `list_photos`, `list_albums`, `create_album`, `add_photo_to_album`
- **[Check and change photo privacy](https://cotlet.dev/integrations/flickr-api-mcp-server/change-photo-privacy.md)**: "List my public photos from before 2024 in the album Family trips. Make them visible to Family only, and tell me how many photos are still public afterwards." → `list_photos`, `get_photo`, `set_photo_privacy`
- **Reply to comments on your photos** (runs: daily): "Find new comments on my photos from the last 2 days that I have not answered. Draft a short, friendly reply to each, skip spam and ask me before posting." → `list_photos`, `list_comments`, `comment_on_photo`
- **Share new photos to groups**: "Add my 5 newest public photos tagged "street" to the groups Street Lisbon and Urban Light. Skip photos already in those groups." → `list_photos`, `list_groups`, `add_photo_to_group`

## Can Flickr automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Flickr connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to tag and title new photos, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/flickr/photos. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/flickr/photos with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Flickr.

### list_albums

Your albums with title, photo count and cover photo. Access: read. REST: `GET /api/v1/flickr/albums`. MCP: `flickr_read → list_albums`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns every album on your account, newest first, with its title, number of photos and cover photo. Use album_id from each item in the other endpoints. Photo count is the number Flickr shows on the album.

Example response:

```json
{
  "albums": [
    {
      "album_id": "72177720330012345",
      "title": "Lisbon 2026",
      "photos": 41,
      "cover_photo_id": "53917620011",
      "url": "https://www.flickr.com/photos/yourname/albums/72177720330012345"
    },
    {
      "album_id": "72177720330099880",
      "title": "Sunday market",
      "photos": 12,
      "cover_photo_id": "53917620040",
      "url": "https://www.flickr.com/photos/yourname/albums/72177720330099880"
    }
  ],
  "next_cursor": null
}
```

### list_photos

Your photos, newest upload first, with title, tags, privacy and album membership. Access: read. REST: `GET /api/v1/flickr/photos`. MCP: `flickr_read → list_photos`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `album_id` | string | no | Only photos in this album. |
| `uploaded_since` | date | no | Only photos uploaded on or after this date. |
| `privacy` | enum | no | public, friends, family, friends_family or private. Default: all. |
| `untagged` | boolean | no | Only photos with no tags. |
| `in_album` | boolean | no | false returns photos that belong to no album. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Lists photos from your photostream, newest upload first, the order of the Camera Roll. Filter by album, upload date, privacy, tag state or album membership to find what needs work. Each item is a summary; get_photo returns the full record. Pages hold up to 100 photos; pass next_cursor back as cursor.

Example response:

```json
{
  "photos": [
    {
      "photo_id": "53917620011",
      "title": "IMG_4412",
      "tags": [],
      "privacy": "public",
      "in_album": false,
      "uploaded_at": "2026-10-11T19:40:00Z",
      "url": "https://www.flickr.com/photos/yourname/53917620011"
    },
    {
      "photo_id": "53917620088",
      "title": "Grandma in the garden",
      "tags": [
        "family",
        "garden"
      ],
      "privacy": "public",
      "in_album": true,
      "uploaded_at": "2026-10-11T19:41:00Z",
      "url": "https://www.flickr.com/photos/yourname/53917620088"
    }
  ],
  "next_cursor": "eyJvZmZzZXQiOjUwfQ"
}
```

### get_photo

One photo with title, description, tags, privacy, albums, groups and counts. Access: read. REST: `GET /api/v1/flickr/photos/{photo_id}`. MCP: `flickr_read → get_photo`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | yes | Photo ID from list_photos. |

Returns one photo with its title, description, tags, who can see it, the albums and groups it is in, and its view, favorite and comment counts. Use it before editing or changing privacy so your agent sees what is already there.

Example response:

```json
{
  "photo_id": "53917620011",
  "title": "IMG_4412",
  "description": "",
  "tags": [],
  "privacy": "public",
  "albums": [],
  "groups": [],
  "views": 18,
  "favorites": 2,
  "comments": 1,
  "taken_at": "2026-10-11T18:12:00Z",
  "url": "https://www.flickr.com/photos/yourname/53917620011"
}
```

### list_comments

Comments on one photo or on your recent photos, oldest first, with author and whether you replied. Access: read. REST: `GET /api/v1/flickr/comments`. MCP: `flickr_read → list_comments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | no | Only comments on this photo. Leave out for your recent photos. |
| `since` | datetime | no | Only comments created after this time. |
| `unanswered` | boolean | no | Only comments you have not replied to. |
| `limit` | integer | no | 1 to 50. Default: 20. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns comments on one photo, oldest first, or the newest comments across your photos when photo_id is left out. Each comment says whether you already answered it, so a daily run replies only once. Pages hold up to 50 comments; pass next_cursor back as cursor.

Example response:

```json
{
  "comments": [
    {
      "comment_id": "72157720330000111-53917620088-1",
      "photo_id": "53917620088",
      "author": "Ana Lopez",
      "body": "Lovely light in this one. Which lens?",
      "created_at": "2026-10-12T08:14:00Z",
      "answered": false
    }
  ],
  "next_cursor": null
}
```

### list_groups

Groups you belong to, with member count and whether you can add photos. Access: read. REST: `GET /api/v1/flickr/groups`. MCP: `flickr_read → list_groups`.

No parameters.

Returns the Flickr groups your account belongs to, with the member count and whether the group lets you add photos. A group can also hold photos for approval by its admins, which is shown on each item. Use group_id in add_photo_to_group.

Example response:

```json
{
  "groups": [
    {
      "group_id": "1234567@N20",
      "name": "Street Lisbon",
      "members": 3120,
      "can_add_photos": true,
      "moderated": false
    },
    {
      "group_id": "7654321@N22",
      "name": "Urban Light",
      "members": 18450,
      "can_add_photos": true,
      "moderated": true
    }
  ]
}
```

### update_photo

Set a photo's title, description and tags. Access: write. REST: `PATCH /api/v1/flickr/photos/{photo_id}`. MCP: `flickr_write → update_photo`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | yes | Photo ID from list_photos. |
| `title` | string | no | New title. Leave out to keep the current one. |
| `description` | string | no | New description. Leave out to keep the current one. |
| `tags` | array | no | Tags as a list of strings. |
| `tags_mode` | enum | no | add or replace. Default: add. |

Changes the title, description and tags of one of your photos and leaves who can see it as it is. Set tags_mode to add to keep existing tags, or replace to swap them. update_photo runs without asking first: it reaches nobody new and is undone with one more call.

Example response:

```json
{
  "photo_id": "53917620011",
  "title": "Lisbon tram 28 at dusk",
  "description": "Tram 28 climbing Rua da Graça, shot from the stairs at golden hour.",
  "tags": [
    "lisbon",
    "tram",
    "dusk",
    "street"
  ],
  "privacy": "public",
  "status": "updated"
}
```

### add_photo_to_album

Add one of your photos to an album. Access: write. REST: `POST /api/v1/flickr/albums/{album_id}/photos/{photo_id}/to-album`. MCP: `flickr_write → add_photo_to_album`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `album_id` | string | yes | Album ID from list_albums. |
| `photo_id` | string | yes | Photo ID from list_photos. |

Adds one of your photos to an album. The photo stays in your photostream and in its other albums. add_photo_to_album runs without asking first: it reaches nobody new and remove_photo_from_album undoes it. An album link shows the photo to anyone who has it, so check privacy for non-public photos.

Example response:

```json
{
  "album_id": "72177720330012345",
  "album_title": "Lisbon 2026",
  "photo_id": "53917620011",
  "photos_in_album": 42,
  "status": "added"
}
```

### remove_photo_from_album

Take a photo out of an album without deleting it. Access: write. REST: `DELETE /api/v1/flickr/albums/{album_id}/photos/{photo_id}/from-album`. MCP: `flickr_write → remove_photo_from_album`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `album_id` | string | yes | Album ID from list_albums. |
| `photo_id` | string | yes | Photo ID from list_photos. |

Removes one photo from one album. The photo stays in your photostream and in its other albums. remove_photo_from_album runs without asking first: nothing is deleted and add_photo_to_album undoes it.

Example response:

```json
{
  "album_id": "72177720330012345",
  "photo_id": "53917620011",
  "photos_in_album": 41,
  "status": "removed"
}
```

### create_album

Create an album with a title and a first photo. Access: write, asks the user first. REST: `POST /api/v1/flickr/primary-photos/{primary_photo_id}/albums`. MCP: `flickr_write → create_album`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Album title. |
| `description` | string | no | Album description. |
| `primary_photo_id` | string | yes | Photo ID of the cover and first photo. |

Creates an album on your account with a title, an optional description and a first photo that becomes its cover. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "album_id": "72177720330099880",
  "title": "Sunday market",
  "cover_photo_id": "53917620040",
  "photos_in_album": 1,
  "url": "https://www.flickr.com/photos/yourname/albums/72177720330099880",
  "status": "created"
}
```

### upload_photo

Upload a photo from a file URL with title, tags and a privacy setting. Access: write, asks the user first. REST: `POST /api/v1/flickr/photos`. MCP: `flickr_write → upload_photo`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `file_url` | string | yes | Public URL of the image file to upload. |
| `title` | string | no | Photo title. |
| `tags` | array | no | Tags as a list of strings. |
| `privacy` | enum | no | public, friends, family, friends_family or private. Default: private. |

Fetches an image from file_url and uploads it to your account with the title, tags and privacy you set. Privacy defaults to private, so nothing goes public by accident. Free accounts hold up to 1,000 public and safe items and 50 non-public ones; Pro has no upload cap. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "photo_id": "53917620112",
  "title": "Sunday market, stall 14",
  "privacy": "private",
  "url": "https://www.flickr.com/photos/yourname/53917620112",
  "status": "uploaded"
}
```

### set_photo_privacy

Choose who can see a photo: everyone, Friends, Family, both or only you. Access: write, asks the user first. REST: `PUT /api/v1/flickr/photos/{photo_id}/privacy`. MCP: `flickr_write → set_photo_privacy`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | yes | Photo ID from list_photos. |
| `privacy` | enum | yes | public, friends, family, friends_family or private. |

Changes who can see one of your photos. A non-public photo that sits in a group is visible to that group's members, and anyone with an album link or a guest pass sees it too. Free accounts hold up to 50 non-public items. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "photo_id": "53917620088",
  "previous_privacy": "public",
  "privacy": "family",
  "status": "updated"
}
```

### comment_on_photo

Add a comment to a photo, as you. Access: write, asks the user first. REST: `POST /api/v1/flickr/photos/{photo_id}/replies`. MCP: `flickr_write → comment_on_photo`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | yes | Photo ID from list_photos. |
| `body` | string | yes | Comment text. |

Adds a comment to a photo, under your name. Use it to answer a comment from list_comments, or to comment on a photo you can see. The comment is public to everyone who can open the photo. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "72157720330000111-53917620088-2",
  "photo_id": "53917620088",
  "status": "published"
}
```

### add_photo_to_group

Add one of your photos to a group you belong to. Access: write, asks the user first. REST: `POST /api/v1/flickr/groups/{group_id}/photos/{photo_id}/to-group`. MCP: `flickr_write → add_photo_to_group`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `photo_id` | string | yes | Photo ID from list_photos. |
| `group_id` | string | yes | Group ID from list_groups. |

Adds one of your photos to a group's pool. A non-public photo becomes visible to all members of that group. Some groups hold photos until an admin or moderator approves them, and the response says so. Flickr allows a free account to post a photo to 30 groups and Pro to 60 where limits apply. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "group_id": "1234567@N20",
  "group_name": "Street Lisbon",
  "photo_id": "53917620011",
  "status": "added"
}
```

## How do I connect Flickr to Claude Code, Codex or Cursor?

Connecting Flickr takes three steps: sign up, sign in to Flickr once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Flickr to your agent.

1. **Create an account** Sign up and add Flickr in the console. Your API key is there too.

2. **Sign in to Flickr in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Flickr there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   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"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Flickr tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Find photos I uploaded in the last 7 days with no tags, look at each one, and add a clear title and 5 to 8 tags. Keep titles I already wrote.
```

### Call Flickr from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/flickr with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X PUT https://cotlet.dev/api/v1/flickr/photos/53917620088/privacy \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"privacy":"family"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "photo_id": "53917620088",
  "previous_privacy": "public",
  "privacy": "family",
  "status": "updated"
}
```

## Why use Cotlet for Flickr?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Flickr yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Flickr changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Flickr to Cotlet?

Yes. You sign in to Flickr yourself, in your own Cloud Browser, and we never save your password. Your agents only get Flickr once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**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 this an official Flickr integration?**

No, Cotlet is independent of Flickr. Flickr's own API is too limited for this work. Cotlet works through your own Flickr account, the way you use Flickr in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Flickr in your console: your agents lose access at once and you stay signed in. Signing out of Flickr in the browser works too, and Reset browser deletes the whole profile.

## Is there a Flickr MCP server on GitHub?

Yes. Community Flickr MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it a Flickr API key and token, and fix it when Flickr changes. Cotlet hosts the same kind of server for you, works in your own signed-in account, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Get a Flickr API key (Pro account needed), clone the repo, authorize it, add it to each MCP client | Sign up, sign in to Flickr once, add one MCP server or API key |
| When Flickr changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Flickr access | API key and token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until you renew the token by hand | Your Cloud Browser keeps you signed in; if Flickr logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Flickr changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Flickr API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Flickr API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| 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. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Flickr account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Flickr yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Flickr only after you enable it. When Flickr signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Flickr, sign out of Flickr in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Flickr's terms:** You use your own Flickr account and stay responsible for following Flickr's terms. Cotlet is independent and not affiliated with Flickr. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Flickr in the console and press Request access. Then you create your API key and connect Flickr there.

**Do I need to be technical?**

No. You sign in to Flickr once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Flickr to Cotlet?**

Yes. You sign in to Flickr yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Flickr once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Flickr sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Flickr cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Flickr's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Flickr sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Flickr login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Flickr offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need Flickr Pro to use Cotlet?**

No. Cotlet works in your own signed-in Flickr account, free or Pro, and does not need an API key. Flickr gives API keys to Pro subscribers only, and a free account holds up to 1,000 public and safe items and 50 non-public ones.

**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.

**Can my agent post or send messages in Flickr without asking me?**

No. Every call to create_album, upload_photo, set_photo_privacy, comment_on_photo or add_photo_to_group waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_photo, add_photo_to_album, remove_photo_from_album runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Flickr API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/flickr from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.