InstantCard staff assistant (MCP)

Chat with Claude to do real InstantCard work: bulk-create cards from any files, look up templates and fields, render print-true previews — with staged approvals and a full audit log.

Connect it to your Claude account (one time)

The URL is the only thing you fill in. If you see Advanced settings with OAuth Client ID and OAuth Client Secret, leave them completely empty. Those are not your login — the server issues its own client ID automatically the first time you connect, and your Everest email and password are asked for on the sign-in page at step 3. Putting your email in the Client ID box gives you invalid_client / Invalid client_id and the connection cannot proceed.

Sign-in only works for Everest admin accounts. If your password fails here but works on core, ask David to check your admin role.

What to say (examples)

• "Here are three files from the customer — a spreadsheet and two photo folders. Create cards for Riverside Police on their approved template."
  Ask by name rather than pasting an id. A number in staff docs is a number that ends up in a prompt that writes — the org id this example used to carry belongs to a live customer.
• "Before committing everything, do just the first card and show me the preview."
• "What templates does org 20015176 have, and what fields does the approved one need?"
• "Which org is Riverside Police?" or "who is jane@acme.org with?" — you don't need to know the org id; a name or an email is enough.
• "Disable Bob's login, he's left the department" — locks the sign-in but keeps the account and its history, and can be undone.
• "They've rebranded — rename that account" — the organization keeps its id, users, templates and cards.
  It flags an existing account with the same name, and lists the saved shipping addresses still holding the old one: those store their own copy, and that copy is what prints on the label.
• "Remember that retired-officer badges keep the original badge number" — records a house note that every future session starts with, for everyone. "What house notes do we have?" lists them; "forget note 12" retires one.
• "Show my settings" · "Show recent activity"

The safety model (why you can trust it)

• Nothing writes without you. The assistant stages a plan and shows a table; cards are only created after your explicit OK — and it can commit one sample card first so you see a real render before the rest.
• Print-true previews. Preview images come from InstantCard's own production renderer, not a mock-up.
• Per-person permissions & caps. What you can commit and your batch size come from your profile; admins manage profiles in chat.
• Audit log. Every action is recorded under your name — "show recent activity" displays it.

Bulk photos

Claude chats accept a limited number of attached files. For big photo sets, zip them and attach the zip — Claude reads the contents. For very large jobs (hundreds of photos), split into batches; your per-plan cap applies.

Troubleshooting

• "Sign-in failed" — Everest admin accounts only; check with David.
• "Invalid client_id" (a black page reading {"error":"invalid_client"}) — the connector was added with something typed into Advanced settings → OAuth Client ID, usually an email address. Delete the connector and add it again with those Advanced fields left empty. Editing them in place does not always take; removing and re-adding does.
• Connector shows disconnected — Settings → Connectors → Connect again (tokens refresh automatically; a full re-login is rare).
• Preview "still rendering" — the server renders asynchronously; ask again in ~30 seconds.