media-meta-mcp

● Active

io.github.latbert/media-meta-mcp

EXIF/XMP reader for HEIC/HEIF/AVIF/WebP images via pure local byte parsing

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "media-meta-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nopilot/media-meta-mcp@1.0.1"
      ]
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add media-meta-mcp -- npx -y @nopilot/media-meta-mcp@1.0.1
OpenAI Codex CLI
codex mcp add media-meta-mcp -- npx -y @nopilot/media-meta-mcp@1.0.1
VS Code
code --add-mcp '{"name":"media-meta-mcp","type":"stdio","command":"npx","args":["-y","@nopilot/media-meta-mcp@1.0.1"]}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Media & Creative
Version
1.0.1
Registry
active
Published
11/16/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: media-meta-mcp is maintained, open source.

Maintained
Active
Last commit 6 days ago (Nov 16, 2026), 0 open issues.
Official registry
Active
Published as io.github.latbert/media-meta-mcp in the official MCP registry, version 1.0.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local npm package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 16, 2026
License
MIT

TypeScript

From the README

media-meta Deterministic modern-image metadata reader: EXIF + XMP from HEIC / HEIF / AVIF / WebP, as a zero-dependency npm engine (@nopilot/media-meta-engine) plus a local-first MCP server (@nopilot/media-meta-mcp). Why this exists: the JS ecosystem's EXIF workhorses are frozen in the JPEG/TIFF era — exif-parser (~4.7M weekly downloads) last shipped in 2017, and the actively maintained exif-reader (~500k weekly) still takes a raw TIFF buffer and leaves container decoding (where modern formats actually keep their metadata) to someone else. Phones default to HEIC; the modern web runs on WebP/AVIF. Reading their metadata in Node today means gluing together container parsers and EXIF decoders yourself — this package is that, done once, tested, and MIT. Verified gap (2026-11-15): exif-reader@2.0.3 (latest) source declares a single exif(buffer) entry that parses a TIFF header at offset 0 (index.js; types Exif = { bigEndian, Image?, Photo?, Iop?, GPSInfo?, Thumbnail? }); its README documents JPEG usage via the separate jpg-stream package. There is no HEIC/HEIF/AVIF/WebP container support — no ISOBMFF box walking, no RIFF chunk parsing, zero occurrences of heic|heif|avif|webp|ftyp in the package. The differentiation stands. The local-first difference Online EXIF viewers and hosted metadata APIs want your photos uploaded.…

Read the full README on GitHub →

The most-starred Media & Creative servers in the index, with their live-check result.

ServerStarsLast pushLive check
HyperFrames by HeyGen87,943Nov 2026Needs sign-in
HyperFrames by HeyGen86,475Nov 2026Needs sign-in
Pascal 3D Editor25,651Nov 2026Needs sign-in
screenpipe22,421Nov 2026Local / not checked
FunASR21,097Nov 2026Local / not checked

media-meta-mcp: questions people ask

Is media-meta-mcp a remote or a local MCP server?
According to its entry in the official MCP registry, media-meta-mcp ships as a local package (npm) that your client starts on your machine.
Is media-meta-mcp safe to use?
Looks healthy: media-meta-mcp is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is media-meta-mcp still maintained?
Active: the repository's last commit 6 days ago. Last push Nov 16, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 17, 2026.
How do I add media-meta-mcp to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. schema-mcpJSON Schema toolkit: version diff with breaking-change classification, draft-07/2020-12 validation
  2. tabular-mcpCSV/JSONL/xlsx toolkit: schema inference, dirty-row reports, format conversion, seeded sampling
  3. tz-mcpTimezone toolkit: convert and compare instants across IANA zones with DST-safe arithmetic
  4. cron-mcpCron toolkit: validate 5/6-field expressions (L/#nth), next fire times in any IANA timezone
Browse all Media & Creative →

Add the badge to your site

Show visitors that media-meta-mcp is listed here — it’s also the link we check for a free listing.

media-meta-mcp — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-latbert-media-meta-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="media-meta-mcp — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![media-meta-mcp — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-latbert-media-meta-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-latbert-media-meta-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-latbert-media-meta-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-latbert-media-meta-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-latbert-media-meta-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-latbert-media-meta-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-latbert-media-meta-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).