All servers · Markets & trading · Maps, location & weather · Payments & accounting
Shoot Plan
uk.co.theamateur/shoot-plan · v0.1.0
New (7 days)Has write/delete tools
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | tools |
| Tool definitions | 11 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers.
Connect
streamable-http · https://theamateur.co.uk/mcp/shoot-plan
claude mcp add --transport http shoot-plan https://theamateur.co.uk/mcp/shoot-plan{
"mcpServers": {
"shoot-plan": {
"url": "https://theamateur.co.uk/mcp/shoot-plan"
}
}
}Tools as reported by the server
shoot_plan_capabilitiesReturn truthful Shoot Plan scope, availability, privacy and commercial state.shoot_plan_exampleReturn a synthetic example plan generated by the real planner, with its provenance.shoot_plan_quoteCalculate a deterministic public quote from non-private project metadata. Do not send a script or brief.shoot_plan_createCreate a plan for an authenticated organisation after authoritative payment confirmation.shoot_plan_listList the authenticated organisation's Shoot Plans, most recently changed first, without returning private intake or full plan content. Archived plans are left out unless includeArchived is true. Each plan's taskId is the ID every other plan tool takes. Structured result: {plans:[...]}.shoot_plan_statusReturn a plan's status, version, whether its included revision is used, its customer-facing order reference, and progress (essential shots ticked, next shot, when the last tick was made). Read-only. Use the full taskId from shoot_plan_list (not planId). A unique eight-character task prefix or orderRshoot_plan_getReturn a full plan: shots in filming order (priority must = essential), setup groups per location or visit, checklist, coverage risks, progress (item keys already ticked), progressSummary with counts, each tick's time and source (web, field or agent), and timeSummary when the plan has timing. Structshoot_plan_timingStructured plans only (not older free-text plans). Compare planned and actual filming time between consecutive ticks in field mode. plannedSeconds is the planned time of those measured tick-to-tick steps, not the whole plan; planPlannedSeconds is the whole plan's planned shot work when present. Readshoot_plan_revisewrite/deleteUse the plan's one included revision. This cannot be undone and uses the allowance, so call shoot_plan_revision_preview first and confirm with the person. For structured plans, change filming time or transfer time (constraintUpdates.availableMinutes, locationTransferMinutes), framing, or structuredCshoot_plan_revision_previewStructured plans only; older free-text plans cannot be previewed. Preview a revision without using it: what would change, which checked shots would be cleared, and whether it still fits. For example constraintUpdates.availableMinutes: 30 answers "what if I only had 30 minutes?". Never uses the inclushoot_plan_progress_syncTick or untick shots and checklist items. Each op: itemKey "shot:<shotId>" or "check:<itemId>" from shoot_plan_get, basePlanVersion = the plan's version, a new random UUID v4 as opId, state "complete" or "incomplete". Retry-safe: resending the same opId does nothing twice. An op made against an olde
Website · JSON · Text for agents · Registry updated 2026-10-19