Free browser-only planning tool
Arcads MCP playbook builder
Choose the client, review-ready output, batch cap, credit boundary, approval gate, and human owner. Get a copyable operating playbook without connecting an account or consuming credits.
1 · Set the boundaries
Browser-only builder. Your selections stay in this browser unless you explicitly submit the optional private-audit form. Never enter credentials or private assets.
2 · Review the playbook
ARCADS MCP OPERATING PLAYBOOK — DRAFT PURPOSE Use Arcads MCP for one controlled, review-ready creative workflow. This draft does not authorize generation, publishing, or spend. MCP CLIENT Claude Desktop: Use Arcads’ documented custom-connector path. APPROVED OUTPUT Approved hook variation batch: Create a capped set of variations from one approved reference and claims boundary. SOURCE MATERIAL One owner-approved product brief and reference asset BATCH AND CREDIT BOUNDARY • Maximum outputs per production run: 5 • Credit boundary: Client-defined maximum Arcads credits per run • Arcads subscription and generation credits remain client-owned and client-paid. APPROVAL GATE Approve every production run: A named operator approves the final inputs and batch cap before each credit-consuming run. HUMAN OWNER Creative operations owner PROHIBITED USES Unapproved claims, private customer data, automatic publishing, and media spend CONNECTION CHECKLIST 1. Confirm the chosen client supports the hosted Arcads MCP server. 2. Add https://mcp.arcads.ai using the client’s custom-connector flow. 3. The client authorizes its own Arcads account; no password or token enters this document. 4. Confirm an active Arcads subscription and sufficient credits for the capped test. 5. Verify the connected tools without submitting private assets or starting a production batch. OPERATING SEQUENCE 1. Creative operations owner checks source ownership, claims, privacy, and the desired output. 2. Apply the approval gate and record the approved batch cap. 3. Run only the accepted playbook in the connected MCP client. 4. Stop when the cap is reached, authorization fails, credits are insufficient, or output leaves scope. 5. Stage every result for human review; do not publish or spend automatically. 6. Record useful output identifiers and exceptions without storing credentials. ACCEPTANCE TESTS 1. Missing approval creates no production generation. 2. The run cannot exceed 5 requested outputs. 3. Prohibited or out-of-scope material stops before generation. 4. Authorization or credit failure returns an actionable stop state. 5. Every generated asset is routed to Creative operations owner for review. 6. Publishing and media spend remain disabled. DEFAULT $299 PILOT BOUNDARY One compatible MCP client, one Arcads account, one approved playbook, connection validation, one capped test, acceptance checks, operating notes, and walkthrough. Arcads subscription, credits, creative rights, claims review, publishing, and media spend are excluded.
Why define the playbook first?
A working MCP connection is not an operating policy.
A safe first workflow names who can approve generation, what source material is allowed, how many outputs may be requested, when to stop, and who reviews the result.
Confirm current prerequisites and connector steps in the official Arcads MCP guide.
- No credentials in the draft
- No run without approval
- No unbounded batch
- No hidden credit exposure
- No automatic publishing
- No exception without an owner
Need implementation?
Connect and prove one Arcads MCP playbook for $299.
FlowPatch turns an accepted boundary into one validated client setup, capped test, operating notes, and walkthrough.
See the setup service