Your token was shown when you first signed up. You can also find it on the account page — or generate a new one there anytime (it automatically revokes the previous token).
Run this in your terminal. Replace YOUR_TOKEN_HERE with your API token.
3
Add the agent prompt
Paste this into your IDE's system instructions (Cursor: Rules for AI, Claude Code: CLAUDE.md, VS Code: custom instructions). The agent drafts blog posts and wiki pages — you approve before it publishes.
You are a scsiwyg assistant with access to the scsiwyg MCP server for blogs and wikis.
## Blog posts
When the user asks you to blog — e.g. "blog: I just fixed the auth loop" — draft a short, authentic post in their voice.
- 150–350 words, first-person, specific and honest
- Use publish_post to publish. Do not call it without user approval.
## Wiki pages
When the user asks you to document something — e.g. "add a wiki page about our API patterns" — create or update a wiki page.
- Use publish_wiki_page for new pages, update_wiki_page to edit existing ones
- Set parent_slug to place pages in the tree hierarchy
- Add confidence (low/medium/high) and sources when appropriate
- Use get_wiki_tree to understand the existing structure before adding pages
Then type “blog: I just fixed the auth loop” in your IDE chat. The agent drafts, you approve, it publishes.
Drop this rule into your IDE so it automatically uses scsiwyg MCP whenever you mention blogging or documentation. Your IDE will know which tools to call without being told.
File: .cursor/rules/scsiwyg.mdc
---
description: Use scsiwyg MCP for all publishing tasks
alwaysApply: true
---
# Publishing with scsiwyg MCP
When the user mentions writing a blog post, creating wiki pages, documenting something, or anything content-related, always use the **scsiwyg MCP** first.
## Blog tools
- `list_my_sites` – list the user's sites
- `get_my_site` / `set_default_site` – manage the active site
- `list_posts` – browse existing posts
- `get_post` – read a specific post
- `create_site` / `update_site` – manage sites
- `publish_post` / `update_post` / `delete_post` – manage post lifecycle
- `list_contributors` / `add_contributor` / `remove_contributor` – manage contributors
## Wiki tools
- `get_wiki_tree` – see the full page hierarchy before making changes
- `publish_wiki_page` – create a wiki page (set parent_slug for hierarchy)
- `update_wiki_page` – edit content, move pages, rename slugs
- `delete_wiki_page` – delete a page (children reparent to grandparent)
- `list_wiki_pages` – list pages, optionally filtered by parent
- `get_wiki_page` – read a single page with children and metadata
## Image tools
- `generate_image` – generate a cover image with DALL-E 3 (returns a Blob URL)
- `upload_image` – upload a base64 image to Vercel Blob (returns a Blob URL)
- Pass the returned URL as `cover_image` to `publish_post` or `update_post`
## Knowledge graph tools
- `get_knowledge_graph` – see how posts and tags connect across the blog
- `get_related_posts` – find posts related to a slug by shared tags
- `get_tag_map` – tag usage with post counts and view totals
- `find_content_gaps` – discover underserved topics to write about next
## Blog workflow
1. Check the default site with `get_my_site` or `list_my_sites`
2. Optionally generate a cover: `generate_image` → save the URL
3. Draft and publish with `publish_post slug: "..." cover_image: "<url>" ...`
4. Use `find_content_gaps` to plan the next post
## Wiki workflow
1. Check existing pages with `get_wiki_tree`
2. Create pages with `publish_wiki_page` — set parent_slug to nest under a parent
3. Add confidence (low/medium/high) and sources for provenance tracking
4. Use see_also to cross-reference related pages
Cursor rules use the .mdc format with frontmatter. Place in your project or ~/.cursor/rules/ for global.
Multiple scsiblogs
All tools accept an optional username parameter to target a specific scsiblog. Omit it to use your default. Create one scsiblog per project.
create_site username: "my-devlog"Create a new scsiblog
set_default_site username: "my-devlog"Set as default