Hosted MCP tool reference
The available tools, their inputs and the boundaries they enforce.
Destination selection
ai2wp_sites takes no input and returns authorized site_id/domain pairs. An all-domains token requires site_id on every other tool. A single-site token may omit site_id, but cannot select a different destination. Authorization is recalculated from current account access.
Prepare a website or Figma source
ai2wp_source_guide accepts source_type (website or figma) and the selected site_id. It returns preparation steps and the relevant guide without fetching design content, creating a brief or consuming a conversion. Figma extraction uses your separate official Figma connection. AI2WP does not authenticate to Figma on your behalf.
Read the design manifest schema
ai2wp_manifest_schema accepts the selected site_id and returns the versioned design manifest JSON Schema, its limits and a minimal valid example. It does not contact WordPress or consume a conversion. Serialize the manifest as input.manifest_json for preflight and create-page. With plugin 0.6.1 or later, an invalid_design error also returns field (the failing path, such as nodes[0].children[1].attrs) and expected (such as object or array). Error messages never repeat your manifest content.
Inspect access and read the brief
ai2wp_site returns the destination, token scope and account entitlements. ai2wp_brief requires job_id and returns an existing conversion brief owned by the same account and destination. Create that brief from Conversion in your dashboard before starting a conversion.
Read and write WordPress
ai2wp_wordpress accepts operation, input and an optional job_id. Operations are inspect-site, read-page, list-pages, preflight, audit-page, create-page, update-section and update-styles. Use ai2wp_manifest_schema for manifest_json and the matching workspace skill for other operation-specific input structures. Pass job_id for conversion work; free writes require the reserved brief. Write operations require a write-scoped token. Publishing is not exposed.
Read post-publication results
ai2wp_followup takes an owned job_id and the selected site_id. It returns recently verified publication state, available source/WordPress xSpeed measurements and optional next steps. Read-only tokens can use it. It does not start duplicate scans, publish pages or configure xSpeed. Call it again after publication or when the user returns.
Publication walkthrough
Performance comparisons
Report progress
ai2wp_report requires job_id, stage and a short summary. Stages are analyzing, structure_planned, draft_created, review_needed, reviewed and blocked. This changes the brief’s reported status, not independent visual verification. It requires write access.
Report a problem
ai2wp_feedback requires an owned job_id, category, stage, code and a short summary. Send reproduction steps and expected versus observed behavior. Do not submit source HTML, credentials, private URLs or full conversations. Reports enter the owner issue inbox and do not automatically deploy fixes.
Transport and limits
The endpoint accepts authenticated Streamable HTTP POST requests. Tokens last 30 days. The account request budget is 120 MCP requests per minute across all its tokens. Feedback has a separate account allowance of 20 reports per hour. Expired credentials, unavailable destinations and exhausted allowances are rejected before WordPress work proceeds.