photographi-mcp
Fast, private, and grounded technical photo analysis for AI applications.
photographi-mcp is an MCP server that enables AI models and LLM-powered tools to perform technical analysis on local photo libraries. It runs computer vision models directly on your hardware (powered by photo-quality-analyzer-core) to evaluate sharpness, focus, and exposure—enabling capabilities like automated culling, burst ranking, and metadata indexing without requiring a cloud upload.
⚡ Why photographi?
- Technical First: Purpose-built for objective metrics (sharpness, lighting, focus). It provides technical data for evaluating image quality.
- Token Efficient: Save model context by pre-filtering technical metadata locally. Only the most relevant insights are sent to the AI application, keeping sessions fast and lean.
- Privacy First: All analysis happens 100% locally on your machine.
- Low Latency: Built for efficient processing, allowing for rapid ranking and technical feedback on local photo folders.
👁️ What It Analyzes
- Smart Focus: Detects subjects and verifies they're sharp
- Exposure: Catches blown highlights and blocked shadows
- Gear-Aware: Knows your lens's sweet spot for optimal sharpness
- Composition: Evaluates framing and subject placement
- Quality Alerts: Flags motion blur, diffraction, high ISO noise
For the science and math behind it, see the Technical Documentation.
📸 See It In Action
Here are real examples from actual photo analysis:
Example 1: Excellent Photo
{
"overallConfidence": 0.89,
"judgement": "Excellent",
"keyMetrics": {
"sharpness": 0.94,
"exposure": 0.87,
"composition": 0.85
}
}
Verdict: Tack sharp on subject, well exposed, strong composition.
Example 2: Poor Photo
{
"overallConfidence": 0.20,
"judgement": "Very Poor",
"keyMetrics": {
"sharpness": 0.30,
"focus": 0.07,
"exposure": 0.0
}
}
Verdict: Missed focus on subject, severe underexposure/black clipping, and excessive headroom.
🛠️ Tools (MCP)
photographi-mcp enables AI models to perform deep technical audits through these standardized tools:
| Tool | AI "Intent" Example | Action / Insight Provided |
|---|---|---|
analyze_photo |
"Is this dog photo sharp enough for a print?" | Full technical audit of sharpness, focus, and lighting. |
analyze_folder |
"How's the overall quality of my 'Vacation' folder?" | Statistical summary identifying the best/worst image groups. |
rank_photographs |
"Find the best shot in this burst of the cake." | Ranks files by technical perfection to find the "hero" frame. |
cull_photographs |
"Move all the blurry photos to a junk folder." | Automatically cleans up failed shots into a subfolder. |
threshold_cull |
"Strictly separate keepers using a score of 0.7." | Binary sorting to isolate professional-grade assets. |
get_color_palette |
"What colors are in this sunset for my website?" | Extracts hexadecimal codes for dominant image aesthetics. |
get_folder_palettes |
"Generate a moodboard from my 'Forest' shoot." | Batch color extraction for an entire folder. |
get_scene_content |
"Which photos contain a 'cat' or 'mountain'?" | Rapid content indexing based on 80+ object categories. |
🚀 Get Started
Claude CLI (Fastest)
claude mcp add --scope user photographi uvx photographi-mcp
Claude Desktop (macOS)
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"photographi": {
"command": "uvx",
"args": ["photographi-mcp"]
}
}
}
GitHub Copilot CLI
Add to ~/.config/github-copilot/config.json:
{
"mcp_servers": {
"photographi": {
"command": "uvx",
"args": ["photographi-mcp"]
}
}
}
🔒 Privacy & Telemetry
photographi is built on a Privacy-First philosophy.
- Anonymized Aggregates Only: We never collect filenames, paths, or EXIF data.
- Total Transparency: Audit our collection logic directly in
analytics.py. - Opt-Out: Set the environment variable
PHOTOGRAPHI_TELEMETRY_DISABLED=1or use the--disable-telemetryflag.
📖 Documentation
- Setup & Config Guide: Detailed configuration and troubleshooting.
- The Science: Math and theory behind the quality scoring.
- Contributing: How to help improve the project.
- GitHub Issues: Report bugs or request features.
Metadata
Release files for photographi-mcp 0.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| photographi_mcp-0.2.6.tar.gz | 18.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| photographi_mcp-0.2.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 31.7 kB
Release files / photographi_mcp-0.2.6.tar.gz
| Download URL | photographi_mcp-0.2.6.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec52b521b1de4ca8e7b2f011efdfe474e2f696ccae9e93941408d290541d5f0f
|
|
BLAKE2b-256 checksum How to use checksums |
9c68710d9a45ad74b878c0b2e645af8ccff8e4d2034893d4c0cd7d24e5ac8083
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logRelease files / photographi_mcp-0.2.6-py3-none-any.whl
| Download URL | photographi_mcp-0.2.6-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3b1383bd62f5f51533c73906428d00b12fc034d9090da5c3ed70ea94d293857
|
|
BLAKE2b-256 checksum How to use checksums |
b763f685e5c283f75b66786da6ce798db62ecc47e2d462ebadfb69e2084ad18e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency log