AI agents

Besides REMO itself, you can let an outside assistant work with your studio: Claude, ChatGPT, or a tool you build. It reads your studio through REMO, and anything it wants to change becomes a card for you to decide.

Connect from a chat app

1. In your assistant, add a connector and paste this address: https://mcp.remo-app.com/mcp
2. REMO opens in your browser. Sign in if it asks.
3. REMO asks you to approve it, with a page headed, for example, Connect Claude to REMO. Choose the studio and what the assistant may do, then press Connect.

You go back to your assistant, which now lists REMO's tools. No key is needed.

Only a studio's owner or an admin can connect an assistant.

If it stops working right after you connect, connect again. Some apps finish the connection twice, and REMO ends a connection it sees finished twice, to be safe.

What an assistant can do

Permission	Meaning
Read	Jobs, the pipeline, the schedule, who is free, the team, the catalog and the Handbook. Always on
Finance	Revenue and outstanding invoices
Propose changes	Assign or swap a photographer, move a shoot, move a job's stage, assign or confirm an editor, send to AutoHDR, deliver a job, and a list of Handbook changes as one card
Act without asking	The same changes made at once where your automation runs hands-off, and setup changes — services, prices, hours, coverage, policy — applied at once, for a set number of days. Off unless you turn it on

Unless you let it act, an assistant never changes anything on its own. It asks; you decide, in the Feed. It can propose Handbook changes as a card, or apply them when you let it act. It can't nudge your crew.

Letting an assistant act

Turn on Act without asking when you connect, or later from the Agents list with Let it act. It lasts seven days unless you set another window at the foot of the list, and you can end it any time. While it acts, a scheduling change your automation would run hands-off is made at once and shows in the Feed under the assistant's name; one your automation asks about first still comes to you as a card. Delivering a job is always a card. A change the assistant makes sends the same notices your automation would — a moved shoot still confirms to the client. Only an owner or an admin can turn it on.

An assistant can also set up or migrate a studio in one go: it hands REMO a list of Handbook changes — services and prices, size tables, tax on items, crew tiers, hours, coverage, booking rules — and REMO checks every one against the studio before anything moves. Without act, the whole list is one card for you to apply. With act, it applies at once, as one entry in the Handbook's history under the assistant's name, and the Feed says so. A list that fails on one change applies nothing; the assistant is told which one and why. The automation dials are never in a list.

Three changes always come to you as a card, even when the assistant may act: turning payment before download on or off, turning the abandoned-booking reminders on or off, and turning off review before delivery. The first two change what your clients see; the third removes a check on your finals. If a list holds one of them, the whole list waits as a card and the assistant is told why; it can send the list again without that change to apply the rest at once. Your crew's two rules apply like any other change. Changes can also depend on each other across sections of the Handbook, so apply a list in one piece rather than sending its parts separately.

A list an assistant applied can be put back while the parts it changed still read as it left them: open the Handbook's history and press Undo this change. The undo is itself an entry, so you can undo it too.

If the undo would put back something you have taken away since, it stops and tells you what to restore first, and changes nothing. A tax category you archived comes back from the Archived list in Settings → Billing → Tax. A crew tier you removed comes back by adding its name again under Settings → General → Crew tiers. Then press Undo this change again.

An assistant you let act can also bring your people in. It can import a client list — each person lands as an imported client, with no invite sent — and add crew for you to invite, who wait in People under Ready to send until you press Send. Nothing is emailed until you do. Both are entries in the Handbook's history, and Undo this change removes the imported clients who have not been invited or booked since and withdraws the invites nobody has accepted; it tells you who it kept. If the list included someone you already had as a client, the undo leaves them as they were and says how many.

Keeping an eye on it

Open the Handbook's Agents section and press Manage agents, or go to Advanced → Settings → Developer. Each connection shows who connected it, what it may do, and when it last called. Revoke cuts it off on its next call.

A connection ends by itself when the person who made it leaves the studio or stops being an admin. One that goes unused for 60 days ends too; connect again to bring it back.

Connect a developer tool

Developer tools use a key. Press Connect an agent, choose A developer tool (the other choice is A chat app), name it, and choose its permissions. REMO shows the key once.

Claude Code

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

Or in .mcp.json, with the key in an environment variable so it never lands in a repository:

{
  "mcpServers": {
    "remo": {
      "type": "http",
      "url": "https://mcp.remo-app.com/mcp",
      "headers": { "Authorization": "Bearer ${REMO_MCP_KEY}" }
    }
  }
}

Claude API

Add an mcp_servers entry with authorization_token set to the key, and an mcp_toolset for it in tools.

Limits

• Each connection has an hourly call limit, 120 unless you change it. Over it, the assistant is told when it may call again.
• The endpoint answers one request at a time and never streams.