sigrix-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGRIX_BASE_URL | No | Optional base URL for the Sigrix API. Defaults to https://sigrix.io. | https://sigrix.io |
| SIGRIX_SELLER_TOKEN | Yes | Your Sigrix seller API token. Create it in Account → Settings. It can create, edit and submit your own drafts for review. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List the categories Sigrix accepts for a listing, each with a slug, a name and a one-sentence description of what belongs in it. Pass a slug from here as |
| list_my_listingsA | List the seller's own listings — prompts, personas and skills, any status — newest first. Each row carries id, item_type, name, status, category, tags, timestamps and the web editor URL. Optionally narrow to one item_type. |
| get_listingA | Read one of the seller's listings in full, as the web editor loads it: every content field and the current status. item_type is prompt, persona or skill. |
| create_draftA | Create a new draft listing owned by the seller and return its id and web editor URL. item_type is prompt, persona or skill; name is the title (at most 80 characters); description should be at least 200 characters; category is a slug from list_categories. Fill the content fields afterwards with update_draft. The draft is private until submitted. Nothing goes live from this tool: a submitted listing enters Sigrix's moderation queue as pending_review and a moderator decides. |
| update_draftA | Update fields on a draft (or a listing returned for corrections). |
| check_draftA | Dry-run submit: ask Sigrix what would refuse this draft, without submitting and without changing anything. Returns the publish gate's own answer — |
| submit_for_reviewA | Submit a draft for moderation. The listing moves to pending_review and a moderator reviews it; the seller is notified of the decision. Refused with the gate's own message when something is still missing — run check_draft first. Nothing goes live from this tool: a submitted listing enters Sigrix's moderation queue as pending_review and a moderator decides. |
| import_skill_mdA | Create a draft skill listing from a SKILL.md file on disk. |
| export_skill_mdA | Read one of the seller's skill listings back as the SKILL.md it compiles to — the same file a buyer downloads. Returns the markdown; when |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| draft_prompt_listing | Draft a prompt listing from an idea and take it to review through the sigrix tools. |
| draft_persona_listing | Draft a persona listing from an idea and take it to review through the sigrix tools. |
| draft_skill_listing | Draft a skill listing (SKILL.md) from an idea and take it to review through the sigrix tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct lifecycle stage or resource: category lookup, listing list/get, draft create/update/check/submit, and SKILL.md import/export. The only near pair, create_draft and import_skill_md, is clearly separated by source (blank draft vs file-based import). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun snake_case pattern (list, get, create, submit, update, check, import, export). The naming is predictable and makes the action and target immediately clear. 'list_my_listings' is a slight deviation but still fits the pattern.
Nine tools cover the seller listing lifecycle without bloat: category discovery, listing listing/getting, draft creation/editing/validation/submission, and SKILL.md import/export. Each tool earns its place within the typical 3-15 range for a focused domain.
The surface covers category lookup, full CRUD for draft listings (create, get, update, list), validation, submission to moderation, and SKILL.md-specific import/export. The notable gap is a delete or archive tool, which agents could work around by leaving unwanted drafts unsubmitted, but it is still a missing lifecycle operation.