Compatible with every major AI agent and IDE
What is the PhotoPrism MCP Server?
Connect your self-hosted PhotoPrism instance to any AI agent to interact with your personal media collection through natural language.
What you can do
- Advanced Search — Query your library using keywords, colors, or dates with the
search_photostool. - Visual Previews — Generate direct URLs for thumbnails in various sizes using
get_thumbnail_url. - Video Streaming — Access streaming links for your stored videos with
get_video_url. - OAuth Management — Handle authentication tokens and user information securely with
create_oauth_tokenandget_oauth_userinfo.
How it works
- Subscribe to this server
- Enter your PhotoPrism URL and API Token
- Start searching and viewing your media from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Photography Enthusiasts — Quickly find specific shots without manual scrolling through thousands of files
- Self-Hosters — Integrate your private cloud with your favorite AI tools for a seamless media experience
- Content Creators — Retrieve assets from your library directly within your coding or writing workflow
Built-in capabilities (7)
Create an OAuth2 token
Get OAuth2 Authorization
Get OAuth2 UserInfo
Get a thumbnail image URL for a photo
Get a video streaming URL
Revoke an OAuth2 token
Search for photos in PhotoPrism
Why CrewAI?
When paired with CrewAI, PhotoPrism becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call PhotoPrism tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
PhotoPrism in CrewAI
PhotoPrism and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect PhotoPrism to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for PhotoPrism in CrewAI
The PhotoPrism MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
PhotoPrism for CrewAI
Every tool call from CrewAI to the PhotoPrism MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for photos by specific filters like color or camera model?
Yes! Use the search_photos tool with the q parameter. You can use filters like 'color:blue' or 'camera:iPhone' just as you would in the PhotoPrism web interface.
What thumbnail sizes are available for my photos?
The get_thumbnail_url tool supports several standard sizes: tile_50, tile_500, fit_720, fit_1280, and fit_1920.
Does this integration support video playback?
Yes. The get_video_url tool constructs a streaming URL for a specific file hash, allowing you to view your videos directly from the provided link.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Open-Meteo Air Quality
4 toolsMonitor the air your users breathe: PM2.5, PM10, ozone, pollen counts, and official AQI indexes (European & US) — real-time pollutant intelligence for health-conscious AI agents.

NOAA Marine — Tides, Currents & Coastal Data
6 toolsUS coastal oceanographic data: real-time water levels (tides), tide predictions, ocean currents, water temperature, coastal meteorological conditions, and multi-decade sea level rise trends from NOAA CO-OPS stations.

Froged
11 toolsManage customer success, track events, and handle omnichannel support via AI agents with Froged.

Zoho ZeptoMail
7 toolsSend and manage transactional emails with Zoho ZeptoMail and AI agents.
