strip-ai-metadata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clean_filesA | Removes hidden metadata from photos (JPG, PNG, WebP, AVIF, HEIC), videos (MP4, MOV), PDFs and camera RAW files (CR2, CR3, NEF, ARW, DNG, RAF, RW2, ORF, PEF): GPS location, camera and serial numbers, owner and author names, dates, XMP/IPTC, C2PA Content Credentials and AI prompts. Works on files or folders on this computer. Originals are not changed: a clean copy is saved as name-clean.ext unless in_place is true. Runs locally; nothing is uploaded. |
| inspect_filesA | Lists what photos, videos, PDFs and RAW files reveal without changing them: GPS location, camera, serial numbers, author, dates, C2PA Content Credentials, AI generator tags and AI prompts. Use it to check a file before sharing or to confirm a clean copy is clean. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are cleanly opposed: clean_files mutates files by stripping metadata, while inspect_files only reports metadata without changing anything. Descriptions explicitly cross-reference the pair (inspect to confirm a clean copy is clean), so an agent can never mistake one for the other.
Both names follow the same verb_noun snake_case convention (clean_files, inspect_files) and share the _files noun, giving a predictable, uniform pattern.
Two tools is on the thin side of the typical range, but for a focused local metadata-stripping utility the inspect+clean pairing is exactly the necessary surface with nothing extraneous. It is minimal rather than bloated.
The domain lifecycle is covered: inspect before sharing, clean, then inspect again to verify. Minor gaps exist, such as no selective per-tag removal or dry-run/batch summary report, but agents can work around these by re-inspecting cleaned output.