Photo Shoot Planner
Related Servers
Alternatives to Photo Shoot Planner
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that turns Claude into a full image production studio, enabling creation, editing, resizing, and brand-consistent asset generation across multiple platforms.6MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server with file management, HTTP requests, system info, and environment variable tools, plus a management UI and dual transport for Claude Desktop and Claude.ai.221 npmMIT
- FlicenseBqualityCmaintenanceA Python MCP server providing weather and date tools for travel planning, compatible with Google ADK and Claude Desktop.2-
- FlicenseNot gradedqualityDmaintenanceA production-ready MCP server ecosystem providing Claude AI with 150+ specialized tools across enhanced memory, data analytics, security, design, and infrastructure domains with PostgreSQL, Redis, Qdrant, and Docker orchestration.-
- FlicenseNot gradedqualityCmaintenanceRemote MCP server for Claude to generate images and videos using Higgsfield AI. Supports photo, reference-based image, and video generation.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server for Claude Code that provides web search via Perplexity Sonar and image generation through OpenRouter, with cost-aware tool design and budget controls.-
TDQS
Scored across 14 tools
Each tool targets a distinct concern (astronomy, location, weather, route, budget, checklists), so most boundaries are clear. get_astronomy and get_sky_timeline have some overlap in sky computation, but get_astronomy focuses on a single instant while get_sky_timeline samples a window, which descriptions clarify.
Tools follow a consistent verb_noun pattern (get_, assess_, compare_, plan_, find_, recommend_, calculate_, build_, generate_, validate_, create_). The verbs are varied but predictable; the only minor inconsistency is that some verbs (get_) are fetch-based while others (validate_, create_) are generative, but the pattern holds throughout.
14 tools is well within the ideal 3-15 range and each tool maps to a distinct production phase: site selection, astronomy, weather, logistics, budget, call sheet, and planning deliverable. Every tool appears necessary to the stated photoshoot planning workflow.
The surface covers the full lifecycle from location/astronomy/weather discovery through route/lodging logistics, cost/budget, and production deliverables (call sheet, releases, readiness score, and field plan). No obvious dead ends; the suite forms a coherent planning pipeline from ideation to execution.