{"id":1089734,"date":"2026-06-11T14:11:51","date_gmt":"2026-06-11T14:11:51","guid":{"rendered":"https:\/\/www.slotix.ai\/docs-agent-pilot\/"},"modified":"2026-06-11T14:11:51","modified_gmt":"2026-06-11T14:11:51","slug":"docs-agent-pilot","status":"publish","type":"post","link":"https:\/\/www.slotix.ai\/it\/docs-agent-pilot\/","title":{"rendered":"Agent Pilot \u2014 Connect Claude to WordPress"},"content":{"rendered":"
\n
\n
\n

WordPress Plugin<\/p>\n<\/div><\/div>\n\n

Agent Pilot<\/h1><\/div><\/div>\n\n

Turn your WordPress site into a secure remote MCP (Model Context Protocol) server<\/strong>. Connect Claude \u2014 from claude.ai on the web, Claude Desktop, or Claude Code \u2014 and let it operate your site: search posts and products, draft and edit pages on-brand, manage WooCommerce, moderate comments and more. Every connection is authorized over OAuth 2.1<\/strong>, bound to a WordPress user, capability-checked and fully audited.<\/p>\n<\/div><\/div>\n\n

\"Agent<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n
\n
\n
\n

What is Agent Pilot?<\/h2><\/div><\/div>\n\n

Agent Pilot is a compliant Model Context Protocol<\/strong> server for WordPress and WooCommerce. It exposes your site to AI agents as a set of well-defined tools, secured by a full OAuth 2.1<\/strong> handshake rather than a shared API key.<\/p>\n<\/div><\/div>\n\n

The hard part of giving an AI access to your site is doing it safely. Every access token is bound to a specific WordPress user, and every tool re-checks that user's capabilities before it runs \u2014 so Claude can never do more than the person who authorized it. Everything it does is written to an audit log you can review and revoke at any time.<\/p>\n<\/div><\/div>\n\n

What you get:<\/strong><\/p>\n

    \n
  • A standards-based MCP server over OAuth 2.1 (PKCE, refresh tokens, Dynamic Client Registration)<\/li>\n
  • 25 built-in tools across four permission scopes: read, content authoring, WooCommerce and site management<\/li>\n
  • Multi-user & multi-instance \u2014 connect several Claude instances as different WordPress users<\/li>\n
  • Per-role and per-user tool control from a dedicated Tools screen<\/li>\n
  • Surgical find-and-replace edits, safe on Divi and Elementor pages<\/li>\n
  • Consent screen, destructive-action confirmation, full audit log, rate limiting, IP allowlist and key rotation<\/li>\n
  • Self-hosted and encrypted at rest \u2014 no telemetry, your data never touches our servers<\/li>\n<\/ul>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n
    \n
    \n
    \n

    Key Features<\/h2><\/div><\/div>\n<\/div>\n<\/div>\n\n
    \n
    \n

    Standards-based, client-agnostic<\/h3><\/div><\/div>\n\n

    A compliant MCP server over the Streamable-HTTP transport with full OAuth 2.1 \u2014 authorization code, PKCE, refresh tokens and Dynamic Client Registration. Works with claude.ai custom connectors, Claude Desktop and Claude Code out of the box.<\/p>\n<\/div><\/div>\n<\/div>\n\n

    \n

    25 tools across four scopes<\/h3><\/div><\/div>\n\n

    Read, content authoring, WooCommerce and site management \u2014 plus an optional Chatbot Pilot knowledge-base scope and any tools other Pilot plugins contribute (invoicing, mail, security, SEO, subscriptions).<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n\n

    \n
    \n

    Per-role & per-user control<\/h3><\/div><\/div>\n\n

    A dedicated Tools screen enables or disables each tool \u2014 or a whole scope \u2014 for any WordPress role or individual user. Administrators get everything by default; every other role starts empty and is granted exactly what it needs.<\/p>\n<\/div><\/div>\n<\/div>\n\n

    \n

    Surgical page-builder edits<\/h3><\/div><\/div>\n\n

    wp_replace_in_post<\/code> makes targeted find-and-replace edits, so Claude can fix a typo on a Divi or Elementor page without rewriting thousands of lines of builder markup.<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n\n

    \n
    \n

    Multi-user & multi-instance<\/h3><\/div><\/div>\n\n

    Connect several Claude instances at once \u2014 Claude Desktop as an editor, Claude Code as an administrator \u2014 each bound to its own WordPress user. The audit log attributes every action to the right person.<\/p>\n<\/div><\/div>\n<\/div>\n\n

    \n

    Defense in depth<\/h3><\/div><\/div>\n\n

    A consent screen, scope-to-capability double checks, per-call confirmation for destructive actions, a full audit log, rate limiting, an optional IP allowlist and one-click key rotation.<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n

    \n
    \n
    \n

    Admin Interface<\/h2><\/div><\/div>\n\n

    Everything runs from a clean set of admin screens \u2014 connect clients, review live activity, and tune exactly what each agent may do.<\/p>\n<\/div><\/div>\n\n

    \"Agent<\/span><\/div>\n\n
    \"Agent<\/span><\/div>\n\n
    \"Agent<\/span><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n
    \n
    \n
    \n

    Configuration Guide<\/h2><\/div><\/div>\n\n

    Install & activate<\/h3><\/div><\/div>\n\n

    Upload the Agent Pilot ZIP under Plugins \u2192 Add New \u2192 Upload Plugin<\/strong> and activate it. On activation it creates its database tables, grants the manage_agent_pilot<\/strong> capability to administrators, and generates the OAuth signing keys automatically.<\/p>\n<\/div><\/div>\n\n

    Connect Claude<\/h3><\/div><\/div>\n\n

    Open Agent Pilot \u2192 Connectors<\/strong> and copy the MCP endpoint<\/strong> URL. In claude.ai or Claude Desktop, go to Settings \u2192 Connectors \u2192 Add custom connector<\/strong> and paste it, then approve the consent screen. For Claude Code, run:<\/p>\n<\/div><\/div>\n\n

    claude mcp add --transport http agent-pilot https:\/\/your-site.com\/wp-json\/agent-pilot\/v1\/mcp<\/code><\/p>\n<\/div><\/div>\n\n

    Choose who the agent acts as<\/h3><\/div><\/div>\n\n

    The consent screen runs as the logged-in WordPress user, and the resulting token inherits that user's capabilities. For a tightly-scoped connection, create a dedicated WordPress user with a limited role (plus the manage_agent_pilot<\/strong> capability so they can authorize), and approve the connector while logged in as that user \u2014 the agent can then do exactly what that user can, and nothing more.<\/p>\n<\/div><\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_ai_seo_pilot_schema_type":"auto","footnotes":""},"categories":[31],"tags":[],"class_list":["post-1089734","post","type-post","status-publish","format-standard","hentry","category-plugin-documentation"],"_links":{"self":[{"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/posts\/1089734","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/comments?post=1089734"}],"version-history":[{"count":0,"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/posts\/1089734\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/media?parent=1089734"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/categories?post=1089734"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.slotix.ai\/it\/wp-json\/wp\/v2\/tags?post=1089734"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}