media-meta-mcp

Registre officiel Médias et design

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @nopilot/media-meta-mcp
Claude Code
claude mcp add media-meta-mcp -- npx -y @nopilot/media-meta-mcp@1.0.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "media-meta-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@nopilot/media-meta-mcp@1.0.1"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. media-meta
  2. The local-first difference
  3. What it reads
  4. Tools (MCP)
  5. Install & run
  6. Engine usage (npm)
  7. Development
  8. Dependencies & licenses
  9. Publishing

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. Location history, device fingerprints, timestamps — exactly the metadata you should not paste into a web form.

media-meta runs entirely on your machine:

hosted EXIF websites / APIsmedia-meta
Where your photos gouploaded to their servernever leave the process
Works offlinenoyes
HEIC / AVIF / WebPrarely (JPEG-era mostly)first-class
Dependencies—engine has zero runtime deps
Source availablemostly closedMIT, full tests

Three hard guarantees (enforced by design and tests):

  1. Deterministic action tools, not AI wrappers — no LLM calls anywhere; identical input produces identical output.
  2. Pure local computation — zero network requests; even the test fixtures are programmatically generated minimal HEIC/AVIF/WebP files (no downloaded binaries — the fixture builders ship in the package).
  3. Runs locally, no hosted gateway — stdio or localhost HTTP, bind 127.0.0.1 by default.

What it reads

  • HEIC / HEIF / AVIF: ISOBMFF meta box → iinf item info + iloc item locations → Exif item (TIFF payload, incl. the 4-byte offset prefix per ISO 23008-12) and XMP (mime item). Both endian-ness TIFF.
  • WebP: RIFF container → EXIF chunk (with or without the 4-byte TIFF-offset prefix) and XMP chunk.
  • EXIF groups: IFD0 (Make, Model, Orientation, DateTime, ...), Exif sub-IFD (ExposureTime, FNumber, ISO, PixelXDimension, ...), GPS sub-IFD (lat/lon refs + rationals, altitude, ...).
  • Container box/chunk listing, brand detection (heic/heix/mif1/msf1/avif/avis/...), structured warnings for truncated/dangling payloads (reported, never thrown mid-parse).

Not covered (by design): pixel decoding, ICC profiles, thumbnail bitmaps. This is a metadata reader.

Tools (MCP)

image_metadata_read

One local file in → { container, brand, exif: { bigEndian, IFD0, Exif?, GPS? }, xmp?, boxes?, warnings } out. Options to trim xmp/boxes from the response.

Install & run

npm install -g @nopilot/media-meta-mcp
media-meta-mcp                          # stdio (default)
media-meta-mcp --transport http --port 9440   # stateless Streamable HTTP on 127.0.0.1

MCP client config (stdio):

{
  "mcpServers": {
    "media-meta": { "command": "media-meta-mcp" }
  }
}

Engine usage (npm)

import { readMetaFile, readMetaBuffer } from '@nopilot/media-meta-engine';

const meta = await readMetaFile('IMG_0001.heic');
// → { container: 'heic', brand: 'heic',
//     exif: { bigEndian: true, IFD0: { Make: 'Apple', Model: 'iPhone 15 Pro', Orientation: 6, ... },
//             Exif: { ISOSpeedRatings: 200, ... }, GPS: { GPSLatitude: [37, 30, 0], ... } },
//     xmp: '<?xpacket ...', boxes: [...], warnings: [] }

Fixture builders (also exported — generate legal minimal files with zero network):

import { buildHeicFixture, buildWebp, buildExifPayload } from '@nopilot/media-meta-engine';
const bytes = buildHeicFixture(); // ftyp+meta(iinf/iloc)+mdat with EXIF+XMP items

Development

npm install
npm test              # build + typecheck + 16 vitest tests + determinism harness
npm run determinism   # byte-equality spot checks only
npm run publish:dry   # npm publish --dry-run for both packages

Dependencies & licenses

Runtime dependencies:

packageversionlicenserole
(engine)——zero runtime dependencies — pure first-party byte parsing
@modelcontextprotocol/sdk^1.32.2MITofficial MCP TypeScript SDK (server package only)
zod^4.6.7MITtool input schema
express^5.2.1MITHTTP transport host

All transitive runtime dependencies (server package) are MIT/Apache-2.0/BSD/ISC — no GPL/AGPL anywhere in the tree. No image decoders (libheif/mozjpeg/etc.) are used or bundled: metadata boxes are parsed directly, which is exactly why the engine can stay dependency-free.

License of this project: MIT (see LICENSE).

Publishing

This repo ships to zero registries by itself. See PUBLISH.md for the manual npm publish + MCP registry submission steps.

Questions fréquentes

Qu'est-ce que media-meta-mcp ?

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

Comment installer media-meta-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add media-meta-mcp -- npx -y @nopilot/media-meta-mcp@1.0.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour media-meta-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

media-meta-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient media-meta-mcp ?

Il est publié par latbert. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.