Shoot Plan

Name: Shoot Plan
Author: uk.co.theamateur

MCP serverMCP

Practical filming plans for AI assistants, with tools to draft, check and export shot plans.

by uk.co.theamateurhomepage ↗v0.1.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"shoot-plan","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability42/42 checks ok

Endpoints

https://theamateur.co.uk/mcp/shoot-planmcp streamable http · checked on a schedule

Registry facts

Not distributed through a package registry we index.

when	check	result	http	latency	detail
6 h ago	mcp initialize	ok	200	64 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
15 h ago	mcp initialize	ok	200	27 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
23 h ago	mcp initialize	ok	200	43 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
31 h ago	mcp initialize	ok	200	59 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	40 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	82 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
2 d ago	mcp initialize	ok	200	32 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
3 d ago	mcp initialize	ok	200	24 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
3 d ago	mcp initialize	ok	200	43 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools
3 d ago	mcp initialize	ok	200	39 ms	server the-amateur-shoot-plan 2026-10-01.v1 · protocol 2025-06-18 · 34 tools

Tools observed via MCP handshake

shoot_plan_capabilities — Return truthful Shoot Plan scope, availability, privacy and commercial state.
shoot_plan_example — Return a synthetic example plan generated by the real planner, with its provenance.
shoot_plan_quote — Calculate a deterministic public quote from non-private project metadata. Do not send a script or brief.
shoot_plan_create — Create a plan for an authenticated organisation after authoritative payment confirmation.
shoot_plan_list — List the authenticated organisation's Shoot Plans, most recently changed first, without returning private intake or full plan content. Archived plans are left o
shoot_plan_status — Return a plan's status, version, whether its included revision is used, its customer-facing order reference, and progress (essential shots ticked, next shot, wh
shoot_plan_get — Return a full plan: shots in filming order (priority must = essential), setup groups per location or visit, checklist, coverage risks, progress (item keys alrea
shoot_plan_timing — Structured plans only (not older free-text plans). Compare planned and actual filming time between consecutive ticks in field mode. plannedSeconds is the planne
shoot_plan_revise — Use the plan's one included revision. This cannot be undone and uses up that revision, so call shoot_plan_revision_preview first and confirm with the person. Fo
shoot_plan_revision_preview — Structured plans only; older free-text plans cannot be previewed. Preview a revision without using it: what would change, which checked shots would be cleared,
shoot_plan_progress_sync — Tick 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
shoot_plan_check — Checks whether a shot plan will cut together before you film or generate it. It looks for crossed lines of action, mismatched eyelines, missing reactions, speak
shoot_plan_missing_details — Lists the questions to put to the person who knows the film, so that more of the plan can be checked. Each question uses the plan's own names, says which paths
shoot_plan_apply_fix — Applies one fix, taken from a shoot_plan_check result, to a plan and checks the revised plan again. Some fixes trade one thing for another (each says its trade_
shoot_plan_format — Returns what you need to write or repair a plan that the checks can read: links to the JSON Schemas, the shortest valid plan, a worked example of a two-person s
shoot_plan_fit_to_budget — Cuts a plan down to what the shoot can afford, without dropping a shot marked `must`: it takes out the least necessary shots one at a time, re-checking the plan
shoot_plan_shot_list — Turns a plan into a shot list a crew can work from. Input: plan; format, "json" (default, dpl.shot-list/1) or "markdown"; vocabulary, an optional industry vocab
shoot_plan_export_for_generation — Prepares a plan for generating its pictures with a generator of your own: it returns the editorial intent of the film (eil.intent/1) and one generation brief pe
shoot_plan_draft_start — Starts a shot plan for you to write: from a short brief it returns a valid skeleton plan (the places to write start with TODO), the layers to write it in, shot-
shoot_plan_draft_next — Says where a draft stands and the one next thing to do, so you can write a plan layer by layer and have each layer checked as you go. It reads the plan you send
shoot_plan_draft_gate — The final check on a drafted plan: is it finished and ready to shoot? It returns ready or not ready, with a record of what was checked and what was not. A plan
shoot_plan_validate_takes — Checks a log of takes against the plan it was shot from, before you rely on it. It finds shots that are not in the plan, take numbers used twice, one op_id used
shoot_plan_merge_takes — Joins two take logs for the same film into one, for when two phones, an AI assistant and a script supervisor each kept a log while offline. Joining is by op_id,
shoot_plan_coverage_status — Answers "did we get it?" before the crew leaves a location: from the plan and the take log it says which must-have shots have no good take, which reactions or c
shoot_plan_edit_guide — Writes the editing guide for a film, scene by scene: what each shot is for, where to cut and why, which cutaway or insert covers which jump or crossed line, the
shoot_plan_export_edit — Makes a first assembly edit from the plan and the take log, as a file your own editing software opens: OpenTimelineIO (otio), FCPXML (fcpxml), a CMX 3600 edit d
shoot_plan_call_sheet — Makes the call sheet for a shoot from a plan's schedule: for the whole schedule, or for one shoot day, who is called, where and when, with the set-ups in order.
shoot_plan_shoot_pack — Makes the pack to take on the shoot day: the call sheet with, for each scene, its shots, the action, the look and the sound notes. Use it when the crew needs on
shoot_plan_summary — Gives a short account of a plan, about 300 words, so that you can pick the work up again without being sent the whole plan: the title, the planned runtime again
shoot_plan_slice — Cuts out part of a plan, so that you can send a smaller plan when your context is short: the scenes, the shots or the sequence you name, with everything they re
shoot_plan_diff — Says what changed between two versions of a plan, so that you can catch up from a few lines instead of reading both. It compares by id, not by position, so reor
shoot_plan_record_decision — Records a decision about one finding from shoot_plan_check (accepted, overridden or wont_fix), with the reason and who decided, so that you do not raise it agai
shoot_plan_to_dpl — Converts one of your organisation's purchased Shoot Plan plans into a dpl.plan/1 plan in the short-form profile, so you can pass it to shoot_plan_check. It is t
shoot_plan_allowance — Says what this account has used and has left of its monthly project allowance, the date it starts again, and, when the limit is reached, how to carry on sooner.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

content.writingWriting & Editing100%productivity.tasksTasks & To-do95%dev.docs-lookupDocumentation Lookup54%documents.conversionDocument Conversion51%commerce.paymentsPayments51%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryuk.co.theamateur/shoot-plan

first seen 13 d ago · fetched 3 d agoopen ↗

Field history (9 recent events)

6 d ago · declared · summary → "Practical filming plans for AI assistants, with tools to draft, check and export shot plans."
6 d ago · declared · description → "Practical filming plans for AI assistants, with tools to draft, check and export shot plans."
6 d ago · declared · version → "0.1.1"
13 d ago · declared · homepageUrl → "https://theamateur.co.uk/developers/shoot-plan/"
13 d ago · declared · summary → "Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers."
13 d ago · declared · protocols → ["mcp"]
13 d ago · declared · version → "0.1.0"
13 d ago · declared · description → "Practical filming plans for AI assistants. Shot-plan checks are not yet available to customers."
13 d ago · declared · publisherName → "uk.co.theamateur"