Pages
Create, update, publish, lock, export, and duplicate pages. Full version history, SEO fields, and block-level editing — all through a single tool call.
12 tools87 atomic MCP tools for publishing, deploying, and managing multi-tenant sites — straight from Claude, Cursor, or any MCP client.
No global install needed. The MCP server runs via npx from SpiderIQ's private registry.
npx --registry=https://npm.spideriq.ai @spideriq/mcp-publish
Add the JSON config to your MCP client — Claude Desktop, Cursor, or any compatible editor.
Settings → MCP → Add Server → paste config
Set your project token. One PAT per project, scoped with five-lock defense.
SPIDERIQ_TOKEN=spideriq_pat_your_token
Start prompting. Create pages, deploy sites, manage content — all from your AI agent.
"Create an About page and deploy to production"
Every tool follows the same pattern: atomic writes, dry_run previews, confirm_token deploys. YAML responses save 40–76% tokens vs JSON.
Create, update, publish, lock, export, and duplicate pages. Full version history, SEO fields, and block-level editing — all through a single tool call.
12 toolsShadow DOM components with scoped CSS and JS. Create, update, publish, rollback, and propagate across tenant sites.
10 toolsTwo-phase deploy: dry_run returns a single-use confirm_token with 5-min TTL. Preview first, then confirm. All or nothing.
5 toolsLiquid templates, theme overrides, layout customization per tenant. Override any section with full Liquid support.
6 toolsBlog posts, navigation menus, directories, media uploads, marketplace, custom domains, and site settings.
30+ toolsOne conversation. Six tool calls. A fully deployed page — live on your custom domain in under 30 seconds.
dry_run → preview → confirm_token. All changes go live simultaneously or none do. Single-use tokens with 5-min TTL.
Every component renders in its own Shadow DOM. No style leaks between tenants. CSS scoped, JS sandboxed.
PAT → project_id → client_id → brand_id → deploy_token. Every API call verified across all five locks.
Responses in YAML cut 40–76% tokens vs JSON. Smaller context windows, faster agent loops, lower cost per run.