You wrote the prompt in Claude Code. Then you re-typed it into a web form.
The Sigrix MCP server removes the second half. It is open source, it installs in one command, and it turns your Sigrix seller token into tools your AI client can call.
you, in your AI client
|
draft -----> private draft
check -----> what's missing
fix -----> saved
submit -----> review queue
|
a human decidesSet it up once
1. Get a token. Open Settings and create a seller API token. It is shown once.
2. Paste the command. The same card shows you the exact line for your client, with the token already in it:
claude mcp add sigrix -e SIGRIX_SELLER_TOKEN=sgx_... -- uvx sigrix-mcpClaude Desktop and Cursor get a configuration block instead — same card, same place.
3. Ask for a listing. "Draft a persona for onboarding emails and submit it."
What it does and doesn't do
| It does | It doesn't |
|---|---|
| Create, edit and submit your own drafts | Publish anything — a moderator still decides |
| Tell you what's missing before you submit | Invent rules of its own; the answers are ours |
| Read your listings | Read your purchases, or anyone else's listings |
Import and export SKILL.md | Open any other part of your account |
About the token
It reaches your listings and nothing else. Not your payouts, not your buyers, not the admin pages — a token is narrower than the account that made it.
Lost it, or pasted it somewhere public? Regenerate or revoke it from the same card. The old one stops working on the next request.
Nothing about review changes
A listing submitted from your editor lands in pending_review, exactly like one submitted from the publish wizard, and the moderator queue shows which way it arrived. You can keep editing it in the browser the whole time.
Prefer the wizard? It hasn't gone anywhere. This is a second door to the same room.
One practical essay, every other Tuesday.
Patterns, sample listings, and short essays from the Sigrix editorial team. One-click unsubscribe, no noise.
0 Comments
Join the discussion. Be kind and stay on topic.