Overview

MCP (the Model Context Protocol) gives an AI agent a set of SpiderPublish tools it can call directly in a conversation. This section is the tool reference; for setup see MCP Setup.

Packages

  • @spideriq/mcp-publish — the SpiderPublish toolset (~124 tools): pages, posts, docs, navigation, media, settings, templates, themes, components, marketplace, deploy, and domains.

  • @spideriq/mcp — the full SpiderIQ toolset (kitchen sink), which additionally includes the 27 form_* tools and the other SpiderIQ products.

Both install from the registry at npm.spideriq.ai. The form tools live in the kitchen-sink package to keep @spideriq/mcp-publish under the tool-count ceiling some agents impose.

The two-step (gated) tools

Tools follow the same safe-publishing model as the rest of the platform:

  • Destructive tools (*delete*, *publish*, *unpublish*, *restore*, deploy, apply-theme) default to dry_run=true. The first call returns a preview and a confirm_token; call again with the token to apply.

  • Create / update tools apply immediately by default — pass dry_run=true to preview first.

Every tool accepts an optional workspace parameter to target a specific bound workspace.

Tool groups

  • Content Tools — pages, posts, authors/tags/categories, docs, navigation, media, settings.

  • Design, Deploy & Domain Tools — components, templates, themes, marketplace, site templates, deploy, domains.

  • Form Tools — building and publishing forms.

  • Skills — the higher-level skill packages that bundle these tools with guidance for agents.

Calling a tool

Once the MCP server is connected, you address tools in natural language and the agent picks them. For example:

"List my draft pages, then publish the one titled 'Pricing' after showing me a preview."

The agent calls content_list_pages, then content_publish_page with dry_run=true, shows you the preview, and only confirms when you approve.

Learn the model first

Agents should call template_get_help (the GET /content/help reference) once per session to learn the content model, block types, and recipes before authoring. template_inspect_block_fields returns the exact fields for a block type so the agent doesn't guess field names.

Next steps

  • MCP Setup — connect the server to your agent.

  • Content Tools — pages, posts, docs, navigation, media, settings.

  • Safe Publishing — the dry-run / confirm model the gated tools follow.

  • Skills — the guidance layer that bundles these tools for agents.