404ops Agent Gate

404ops Agent Gate gives AI agents a standards-based, token-scoped way to read your WordPress site and, if you allow it, to propose changes. Nothing an agent proposes is applied until you approve it.

Features

• A standards-style /llms.txt that lists the site, the API and each public post type's published entries. A site that asks not to be indexed lists no content.
• A token-scoped REST API under /agent-gate/v1/. A read token lists and reads published, public content. A write token may request creates, edits and deletes, which wait in the Approval Queue.
• Tools granted one at a time to each token: search, media, terms, comments, users, menus, the Site Health summary, and plugins and themes. Nothing is granted by default.
• Per-token post types, so each token is confined to the post types it may read or write.
• An MCP endpoint at /wp-json/agent-gate/v1/mcp. On HTTPS sites, MCP clients can sign in with OAuth 2.1 (PKCE required) and act with your permissions, never more.
• An Approval Queue that shows what approving each change would do, with a diff for edits and a warning if the post changed since the request.
• An audit log of every API request, including requests refused at sign-in.
• Tokens stored as hashes only. A token unused for 90 days is marked stale, and sites can stop idle tokens after a set number of days.
• Agents cannot install plugins, change users or roles, edit settings or edit files.
• Image uploads from a URL are fetched only over HTTPS, only from public addresses, and only as JPEG, PNG, GIF or WebP files up to 10 MB.

Free version

The free version is available on WordPress.org once it is listed there.