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)
2. Click Add → Add custom connector, name it InstantCard Staff, and enter:
https://mcp.instantcard.net/mcp
3. Click Add, then Connect. A sign-in page opens —
use your Everest admin email and password (the same login as core.instantcard.net/admin).
4. Done. In any new chat, click the tools (🔧) menu and make sure
instantcard-staff is enabled. Then just ask: "what can you do with InstantCard?"
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 org
20015132 on template 39862."
- "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?"
- "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.
- 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.