AI Agent Access (MCP)

AI Agent Access (MCP)

Connect an AI assistant — like Claude, Claude Desktop, or Claude Code — to your Cine Power Planner account through a secure Model Context Protocol (MCP) server. Once connected, the assistant can answer questions about your projects, gear, schedule, and finances, and (with a read & write key) help manage them.

Requires an active subscription. Available to signed-in users.

Quick start

1. Generate a key: Settings → Security & Privacy → Agent access → choose an access level → Generate key (shown once — copy it immediately).
2. Connect your client to https://cine-power-planner.com/mcp with the key as a Bearer token (client-specific steps below).
3. Test it: ask your assistant to run get_account_status — it should report your account as connected.

Generate a key

1. Go to Settings → Security & Privacy → Agent access.
2. Choose an access level:
   • Read only — the agent can read your data but can never change anything.
   • Read & write — the agent can also create, edit, and archive records.
3. (Optional) Name the key so you can recognise it later (e.g. "Claude Desktop").
4. Tick the acknowledgement that you understand what the agent can access.
5. Click Generate key. The key is shown once — copy it now and store it securely (a password manager is ideal). You won't be able to see it again.

Each key has an expiry and can be revoked at any time from the same panel.

Connect your AI client

The server address is always:

https://cine-power-planner.com/mcp

with an Authorization: Bearer <your-key> header.

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → enter the URL above and provide the key as the Bearer token (in the connector's advanced/authentication settings, depending on your version).

Claude Code (terminal):

claude mcp add cine-power-planner https://cine-power-planner.com/mcp \
  --transport http --header "Authorization: Bearer <your-key>"

Other MCP clients: any client that supports remote MCP servers over Streamable HTTP works — point it at the URL and set the Authorization header.

What the agent can do

Ask about your data (read-only key is enough)

• Projects — "What projects do I have running?", "Who's the gaffer on Nightfall?", "What gear is on the Studio X list?", "How is the budget looking on my current job?"
• Shot list — "What are we shooting in scene 12?", "How many shots are left on Nightfall?", "Give me the scene breakdown for day 2." Scenes come back with their headings, INT/EXT, time of day and page eighths, and each scene's shots with size, angle, movement and lens.
• Call sheets — "What's the call time on Friday?", "Where's basecamp on day 3?" — the assistant reads back the call sheets on a project without opening the whole thing.
• Cast — "Who's playing Anna?", "Which parts are still not cast?", "Is Lea free the week of 8 September?", "What shoe size is our lead?" The assistant reads the Characters tab: character and actor, playing age, where each role stands in casting, contact details, blocked dates, and — when you ask for the detail — wardrobe sizes, measurements, appearance notes, your own custom columns and the contact log. Headshots and self-tapes stay in the app.
• Locations — "Where are we shooting?", "What's the parking situation at the villa?", "Which location is nearest to a hospital?", "Is the kitchen confirmed yet?" You get the location list grouped the way the app groups it — a master location with its sets under it — and, for any one location, the full scout sheet: access and load-in, parking, department bases, power, hazards, permits, costs, contacts. For a set, values it inherits from its master are filled in and flagged as inherited.
• Camera package & requirements — "What camera package is on Nightfall?", "Which lenses did I put on the requirements?"
• Schedule — "What's shooting in July?", "Do any of my projects overlap next week?" — one call scans the calendar across all your projects.
• Gear & availability — "Is my ALEXA 35 free June 10–14, or is it on a job?" — checks your projects and sub-rentals in that window. Also: "What do I own from ARRI?"
• Device specs — "How much power does a Sony FX6 draw?", "What's the close focus of a 32mm Master Prime?" — searches the built-in equipment catalog.
• Finances — "How much did I invoice in June?", "What are my open quotes worth?", "Biggest expense categories this year?" — plus your invoices, expenses, quotes, bank accounts, and transactions.
• Contacts, sub-rentals, rental requests — look up crew contacts, rental transactions, and incoming requests for your public gear list.

Make changes (read & write key)

• Create, edit, and archive projects, owned gear, sub-rentals, quote drafts, and contacts.

• Surgical project edits: add / update / remove a single gear item, add / update / remove a single crew member, set prep / shoot / return dates, or update project requirements — without touching the rest of the project.

• Crew — "Put Anna Weber on Nightfall as gaffer at €650/day", "Take Tom off the crew list." Removing someone unstaffs them from that project only; their contact record stays in your address book.

• Call sheets — "Start a project Nike Spring and make a call sheet for July 10: call at 7am, basecamp at the Warehouse Lot, scenes 12–13 on the rooftop, hotel is the Grand." The assistant creates the project (if needed) and seeds a call sheet from whatever details you give — you only ever need a shoot date. Crew, cast, and gear fill in from the project when you open the call sheet in the app; refine and export to PDF there.

• Cast — "Add Anna to Nightfall, played by Lea Roth, offer is out", "Mark Marlow as booked", "Lea can't do 1–3 September, she's in theatre", "Note her shirt size as M." The assistant builds and maintains the cast roster — including your project's own custom columns, which you name by their column title. Blocked dates are entered as unavailability, which is what the app's Day-Out-of-Days grid and the availability lights read. Headshots and self-tape files can't be uploaded this way (links can).

• Locations — "Add the Villa Rossi as a location, confirmed, Via Roma 1", "Add the kitchen and the courtyard as sets under it — the kitchen is on the second floor", "Put the hospital and the parking notes on the villa", "Mark the beach as a backup." Sets under a master inherit the master's address, contacts, parking, hospital and the rest, so you only fill in what actually differs. Deleting a master asks you first whether its sets should survive on their own or go with it. Photos and sketches are added in the app.

• Timesheets — "Set up a timesheet for Nike Spring: gaffer, €650/day, German TV/FFS rules, night and weekend surcharges on." The assistant creates a timesheet with your pay rate and working-time conditions and links it to the project. You (or the crew) then log daily hours against it in the Time Tracking tab, where it computes pay from those conditions. Only the project is required — everything else has sensible defaults.

• Read a document into the app — no AI API key needed. Attach a receipt, vendor invoice, sales invoice, call sheet / Disposition, or rental quote in your chat and ask for it to go in. Your assistant reads the original file itself (it sees the actual PDF or photo, not a text scan of it), the server checks the extracted fields against the same rules the app uses, and a draft appears in the matching place:

  You attach	Where the draft lands
  Purchase receipt / vendor invoice	Accounting → Expenses
  A sales invoice you issued	Accounting → Invoices
  Call sheet / Disposition	the project's Call Sheets tab
  Equipment rental quote	the project's Quote Comparison

  Nothing is saved until you review it. Each import shows up as a "waiting for review" notice and opens in the review screen you already use for dropped files — same confidence badges, same gear matching, same duplicate detection. You accept or discard it there.

  This is separate from the in-app AI scanning in Settings, which uses your own API key. Both work; this one needs no key because your assistant does the reading. Pending imports are capped at 200 and clear themselves after 7 days.

• Accept a pending collaboration invite.

• Manage your public rental catalog link, and answer an incoming gear request with a quote. Sending a quote emails the requester — your assistant is instructed to confirm recipient, items, and rates with you first.

Changes made by the agent sync to your devices like any other edit and show up in the app immediately.

Current limits

• Accounting and quote data is unavailable if your account uses multi-company accounting (projects, gear, sub-rentals, and contacts still work). Support is planned.
• Gear-availability matching is by name — if a project's gear list spells an item differently than your inventory, mention both spellings when asking.
• Quote drafts created by the agent never receive a final quote number — numbering happens only when you send the quote.
• Document imports of expenses and invoices are unavailable on multi-company-accounting accounts (call sheets and rental quotes still work).
• An imported document is never attached as a file — only the extracted fields are carried over, because the file itself stays in your chat client.
• Some parts of the app are read-only or unavailable to the assistant, and it will tell you so rather than guess: PDF export and rendering, floor plans, moodboards, file and photo uploads (including cast headshots, self-tapes and location photos), project documents, gear sets, damage reports, and reading logged timesheet hours back. Shot lists are readable but not yet editable — ask in the app to change a scene or shot.

Tips for good results

• Ask naturally — the assistant picks the right tools on its own. You never need to name a tool, though you can.
• For broad questions, give a time frame: "…in July", "…next month", "…this year".
• With a read & write key, review each proposed change in your MCP client before approving it — archive and delete actions are flagged as destructive so your client asks for confirmation.

Privacy & safety

• A read-only key can never change your data — use it when you only want the agent to look things up.
• Every key requires your explicit consent to data access before it's issued.
• The agent acts strictly as you, sees only your data, and every action is rate-limited and logged (metadata only — never the contents).
• Keys expire automatically; revoke a key the moment you stop using a device or client — revocation takes effect immediately.
• Your AI client asks you to approve actions the agent takes — review changes before approving, especially deletions and anything that sends email.

Troubleshooting

Revoke a key

Settings → Security & Privacy → Agent access → Revoke next to the key. Any agent using it loses access immediately. Issue a new key to reconnect.

---

Last Updated: 2026-09-08 Version: 0.790.2