Help & Documentation

Agent Access connects an outside AI assistant to your account through a secure Model Context Protocol (MCP) server. Once connected, the assistant can read your data to answer questions, and — with a read & write key — make changes on your behalf. It always runs as you, scoped to your own account.

• Opt-in and off by default. Nothing is exposed until you generate a key.
• Two access levels: read only (the agent can never change anything) or read & write (it can also create, edit, and archive).
• Scoped to your account only. Every request runs under the same row-level security as the app — the agent can't reach anyone else's data.
• Works with any MCP client that supports remote servers over Streamable HTTP. Claude Desktop and Claude Code are the common ones.
• Changes the agent makes sync to your devices like any other edit, and are marked as made by an AI agent.

Agent Access is a cloud feature, so a few things need to be in place before it works.

• A Cine Power Planner account, signed in.
• An active subscription — Agent Access is a paid feature.
• Cloud Sync consent granted — every change the agent makes needs it. The agent works on the same cloud copy your devices sync, so local-only accounts can't use it.
• A one-time data-access acknowledgement, recorded when you generate your first key.

Keys are created and managed in one place, and each one is shown only once.

1. Open Settings → Security & Privacy → Agent access.
2. Choose an access level: Read only, or Read & write.
3. Optionally fill in Key name so you can recognise it later (e.g. "Claude Desktop").
4. Pick when it Expires: 7 days, 30 days, 90 days (the default), 1 year, or No expiry.
5. Tick the acknowledgement that you understand what the agent can access.
6. Click Generate key.
7. Copy the key immediately — it's shown only once. Store it in a password manager.

The connection is the same for every client: one server address plus your key as a Bearer token.

• Server address (always the same): https://cine-power-planner.com/mcp
• Authentication: send your key in an 'Authorization: Bearer <your-key>' header.
• Transport: remote MCP over Streamable HTTP.

1. Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → enter the server address above and provide the key as the Bearer token (in the connector's authentication settings; the exact wording varies by version).
2. Claude Code (terminal): run — claude mcp add cine-power-planner https://cine-power-planner.com/mcp --transport http --header "Authorization: Bearer <your-key>"
3. Any other MCP client: point it at the server address and set the 'Authorization: Bearer' header. Anything that supports remote MCP servers over Streamable HTTP works.
4. Test it: ask your assistant to check your account status (the get_account_status tool). It should report your account as connected.

With any key, the assistant can answer questions about your data. A few examples of what works well:

• Projects — "What projects do I have running?", "Who's the gaffer on Nightfall?", "What gear is on the Studio X list?"
• Schedule — "What's shooting in July?", "Do any of my projects overlap next week?" (one call scans your whole calendar).
• Gear & availability — "Is my ALEXA 35 free June 10–14, or is it on a job?", "What do I own from ARRI?"
• Device specs — "How much power does a Sony FX6 draw?", "What's the close focus of a 32 mm Master Prime?" (searches the built-in catalog).
• Quotes & banking — "What are my open quotes worth?", "Which quotes went out in June?" — plus your bank accounts and transactions.
• Sub-rentals and incoming rental requests for your public gear list. A person's e-mail and phone on a project come with its crew, cast and locations.
• 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 headings, INT/EXT, time of day and page eighths, each with its shots (size, angle, movement, lens).
• Call sheets — "What's the call time on Friday?", "Where is basecamp on day 3?" — read back without opening the whole project.
• 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?" Reads the Characters tab: character and actor, playing age, casting status, contact details, blocked dates, and — on request — wardrobe sizes, measurements, appearance, your custom columns and the contact log.
• Locations — "Where are we shooting?", "What’s the parking at the villa?", "Which location is nearest a hospital?" Locations come back grouped as the app groups them (a master with its sets), and any one of them with the full scout sheet: access and load-in, parking, department bases, power, hazards, permits, costs, contacts.
• Camera package & requirements — "What camera package is on Nightfall?", "Which lenses are on the requirements?"

With a read & write key, the assistant can also make changes. Review each proposed change in your client before approving it.

• Create, edit, and archive projects, owned gear, sub-rentals, and quote drafts. A project the assistant creates starts in the units you chose under Settings › General › Units, like one you create in the app; if you never chose, it starts metric.
• Surgical project edits: add / update / remove a single gear item or a single crew member, set prep / shoot / return dates, or update project requirements — without touching the rest of the project.
• Seed call sheets onto a project from information you have (see the next section).
• Build the cast roster — "Add Anna to Nightfall, played by Lea Roth, offer is out", "Mark Marlow as booked", "Lea can’t do 1–3 September." Blocked dates are stored as unavailability, which is what the Day-Out-of-Days grid and the availability lights read. Your project’s own custom cast columns are set by their column title. Headshots can be set when the assistant supplies them as an image link or a WebP image of at most 400 KB (up to 10 per person); a new set replaces the old gallery.
• Build the location list — "Add the Villa Rossi, confirmed, Via Roma 1", "Add the kitchen and the courtyard as sets under it." A set inherits its master’s address, contacts, parking and hospital wherever its own value is empty, so only the differences need filling in. Deleting a master asks first whether its sets survive on their own or go with it.
• Set up a timesheet (pay rate + working-time and surcharge conditions) linked to a project — you or the crew then log daily hours against it in the Time Tracking tab.
• Read a document into the app with no AI API key — attach a receipt, a sales invoice you issued, a call sheet / Disposition, or a rental quote in your chat. The assistant reads the file itself and queues a draft for review in Accounting → Expenses, Accounting → Invoices, the project's Call Sheets tab, or the project's Quote Comparison. Nothing is saved until you accept it there; 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 — the assistant confirms recipient, items, and rates with you first.
• Staff a project — "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.

A common workflow: turn shoot details you already have — an email, a brief, a schedule — into a call sheet. Ask naturally, and the assistant creates the project (if needed) and seeds a call sheet with whatever you provide.

Agent Access is built so you stay in charge of what an assistant can reach, and can cut it off instantly.

• Your key is a credential — anyone holding it can reach your account at that key's access level. Store it like a password; never share it or commit it to a repo.
• Keys are scoped to your account only. The server runs each request as you, under the same row-level security as the app.
• The server keeps no standing access to your account — it mints a short-lived token per request and never stores your project content.
• A metadata-only activity log records which tool ran and when (never your data). It's deleted automatically after 180 days; the Agent access panel shows when each key was last used.
• Records the app encrypts on your devices (contacts, invoices, expenses and more) never reach the assistant — the Agent access server sees only encrypted data and has no key to it.
• Revoke any key at any time from Settings → Security & Privacy → Agent access. Deleting your account removes every key and the activity log.

The assistant is told what it has no access to, so it says so instead of guessing or inventing an answer. Use the app for these.

• Contacts, invoices and expenses — the app encrypts them on your devices before they sync, and the Agent access server has no key, so the assistant can neither read nor change them. It says so (ENCRYPTED) instead of guessing. How the encryption works and where its limits are: Privacy & Data → Data Encryption at Rest. A person's e-mail and phone on a project stay available through its crew, cast and locations.
• PDF export and rendering — call sheets, briefings and reports are generated in the app.
• Floor plans, moodboards, and file or photo uploads — self-tapes, location photos and sketches (links to a self-tape can be stored, the file cannot). Cast headshots are the one exception: they can be set, but never read back.
• Project documents, gear sets, and damage reports.
• Reading logged timesheet hours back — it can create a timesheet, but the hours live in the Time Tracking tab.
• Editing scenes and shots — the shot list is readable, not yet writable.
• Accounting and quote data, and receipt or invoice imports, on multi-company-accounting accounts (projects, gear, sub-rentals, shot lists, and call-sheet and rental-quote imports still work).

The most common messages you might see from your assistant, and what they mean:

• "Invalid, expired, or revoked key" — the key is wrong or was revoked. Generate a new one and reconnect your client.
• "Subscription required" — Agent Access needs an active subscription on your account.
• "Consent required (mcp_access)" — grant the one-time data-access acknowledgement in the Agent access panel, then retry.
• The assistant can't see a recent change — it reads your cloud copy. Make sure Cloud Sync is on and has finished syncing on the device where you made the change.
• Accounting or quote questions are refused — those tools are unavailable on multi-company accounting accounts in this version.
• "ENCRYPTED" — you asked about contacts, invoices or expenses. They are encrypted on your devices, so the assistant cannot read them; use the app for these.