Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Flickr MCP

by MK3Coreversion 0.2.1i★ –iRuns on your computer
Registry nameio.github.MK3Core/flickr-mcp

Install

Overview

Description from the maker (original English)

Flickr MCP server — tag photos, write descriptions, set titles, and add photos to groups using AI.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "flickr": {
      "command": "npx",
      "args": [
        "-y",
        "flickr-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add flickr -- npx -y flickr-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "flickr": {
      "command": "npx",
      "args": [
        "-y",
        "flickr-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "flickr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "flickr-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account MK3Core, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32531 servers in this category
  • Published to the registry more recently than 12% of the other 32531 servers in this category
  • Basic checks equal to or better than 100% of the other 32531 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Flickr MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Reelsaw

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

Reelsaw

by osbytes

Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

flickr-mcp

An MCP server that gives AI assistants authenticated access to your Flickr photo library. Tag photos, write descriptions, set titles, manage group memberships, and run a full automated processing workflow — all driven by AI, applied to your photos.

Works with any MCP-compatible AI client: Claude, Cursor, Windsurf, and others.


What it does

Once connected, you can ask your AI assistant things like:

  • *"Process all my untagged photos"* — scans your whole library, tags and describes everything in one pass
  • *"Tag all the photos in my Japan album"*
  • *"Write a description for this photo"* (with a Flickr URL or photo ID)
  • *"Find my car photos and add them to relevant Flickr groups"*
  • *"Look at my recent uploads and add relevant tags to each one"*

The AI looks at your photos visually (via built-in image fetching), generates metadata from the actual image content and EXIF data, and either previews changes before applying or runs fully automated depending on the tool.


Requirements

  • Node.js 18 or later
  • A Flickr Pro account — Flickr requires Pro to register API applications
  • An MCP-compatible AI client

Setup

1. Register a Flickr API key

Note: Flickr requires a Pro account to register API applications (~$8/month or ~$72/year). If you're using Flickr seriously enough to want AI-assisted tagging, you likely already have one.

Go to flickr.com/services/apps/create/noncommercial and fill out the short form — any app name works, select "personal use." It takes about two minutes. Copy the API key and API secret from the next page.

2. Run the setup command
npx flickr-mcp setup

A browser window will open with a setup wizard. Paste your API key and secret, then follow the prompts to authorize access to your Flickr account. Your credentials are saved to ~/.config/flickr-mcp/credentials.json and never leave your machine.

3. Add flickr-mcp to your AI client

The easiest way is to paste the following prompt directly into your AI assistant. It contains everything needed — the config entry, the setup reminder, and a pointer to the full docs:

Add an MCP server to my config with these details:

- Name: flickr

- Command: npx

- Args: ["flickr-mcp"]

The full config entry is:

`json

"flickr": {

"command": "npx",

"args": ["flickr-mcp"]

}

`

Add this to the mcpServers block in my MCP config file, then let me know where you put it and remind me to restart the client.

Full documentation and source: https://github.com/MK3Core/flickr-mcp

Your assistant knows where its own config file lives and will place the entry correctly regardless of which client you're using. After it confirms, restart the client.

Prefer to do it manually?

Claude Code — add to ~/.claude/settings.json (global) or .claude/settings.json in a project:

{

"mcpServers": { "flickr": { "command": "npx", "args": ["flickr-mcp"] } } }

Claude Desktop

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{

"mcpServers": { "flickr": { "command": "npx", "args": ["flickr-mcp"] } } }

Cursor / Windsurf — check your client's MCP settings panel, or ask your assistant to find and edit the config file for you.


Full automated workflow

The quickest way to process your entire library is two tool calls:

  1. `flickr_get_unprocessed_photos` — scans every photo in your library and returns a list of anything missing tags, a description, or a real title. Raw camera filenames like DSC_0042 or Lightroom export suffixes like IMG_1234-Edit are flagged automatically.
  1. `flickr_process_photo` — applies title, description, tags, and group assignments to a single photo in one atomic call. The AI fetches the image visually, reads EXIF for camera/lens/location data, generates up to ~20 focused tags following Flickr best practices, writes a concise description, and adds the photo to relevant groups — joining them automatically if needed.

Just ask: *"Process all my untagged photos"* and the AI will page through the unprocessed list and handle each one.


Available tools

These are the tools your AI assistant can call once the server is running. You don't interact with them directly — just describe what you want in plain language.

Reading your library
ToolDescription
flickr_list_photosList your photostream, paginated
flickr_get_photoFull photo details, optionally including the image itself for visual analysis
flickr_get_exifCamera metadata: make, model, lens, GPS, shutter speed, ISO
flickr_search_my_photosSearch your own photos by keyword or tag
flickr_get_albumsList your albums
flickr_get_album_photosList photos inside an album
Editing metadata
ToolDescription
flickr_add_tagsAdd tags to a photo (previews before applying by default)
flickr_remove_tagRemove a tag from a photo
flickr_set_metadataSet a photo's title and/or description (previews before applying by default)
Group management
ToolDescription
flickr_search_groupsSearch Flickr groups by keyword — returns name, member count, pool size
flickr_join_groupJoin a Flickr group programmatically (accepts group rules automatically)
flickr_add_to_groupAdd a photo to a group pool (previews before applying by default)
Automated workflow
ToolDescription
flickr_get_unprocessed_photosScan your entire library and return photos missing tags, descriptions, or real titles
flickr_process_photoApply title + description + tags + group assignments in one call, with auto-join

Individual write tools (flickr_add_tags, flickr_set_metadata, flickr_add_to_group) show a dry-run preview before applying. flickr_process_photo runs without preview by default — it's designed for batch automation.


Tagging approach

The AI follows Flickr-specific best practices when generating tags:

  • Target ~20 tags per photo — enough to reach the right audiences without diluting reach
  • Broad + specific subject pairing: "dog" and "golden retriever", not just one or the other
  • Location chain: continent, country, region, city, venue where available
  • Gear tags from EXIF: camera body and focal length (e.g. "sony a7 iv", "85mm")
  • Never: noise tags ("photo", "image", "picture"), irrelevant popular tags, or tag spam — Flickr's spam policy can hide photos from search

Privacy and scope

This server can only access your own photos. It has no ability to read, search, or modify other users' content. The write access it requests is limited to your account.

Your API credentials are stored locally at ~/.config/flickr-mcp/credentials.json and are never sent anywhere except Flickr's own API.


Rate limiting

The server uses a token bucket that targets 3,000 requests/hour (Flickr's limit is 3,600). Burst of up to 10 requests is allowed. Image fetches count against the budget. Under normal use you will not hit this limit.


Running from source

git clone https://github.com/MK3Core/flickr-mcp

cd flickr-mcp npm install npm run build node dist/index.js setup

Then point your MCP client at node /path/to/flickr-mcp/dist/index.js instead of npx flickr-mcp.


Support

flickr-mcp is free and open source. If it saves you time, a GitHub sponsorship is always appreciated — it helps justify spending more time on projects like this.


Contributing

Issues and pull requests are welcome. The codebase is intentionally small — around 700 lines of TypeScript across six files.

src/

index.ts Entry point setup.ts OAuth setup flow auth.ts OAuth 1.0a implementation + credential storage rate-limiter.ts Token bucket (3,000 req/hour) flickr-client.ts Flickr API wrapper tools.ts All tool definitions and handlers

Ask PopNx