Title: Albert – Connect AI Assistants to WordPress Author: Albert Published: 25 fevereiro, 2026 Last modified: 25 setembro, 2026 --- Pesquisar plugins ![](https://ps.w.org/albert-ai-butler/assets/icon-256x256.png?rev=3505242) # Albert – Connect AI Assistants to WordPress Por [Albert](https://profiles.wordpress.org/albertai/) [Baixar](https://downloads.wordpress.org/plugin/albert-ai-butler.1.4.2.zip) * [Detalhes](https://br.wordpress.org/plugins/albert-ai-butler/#description) * [Avaliações](https://br.wordpress.org/plugins/albert-ai-butler/#reviews) * [Instalação](https://br.wordpress.org/plugins/albert-ai-butler/#installation) * [Desenvolvimento](https://br.wordpress.org/plugins/albert-ai-butler/#developers) [Suporte](https://wordpress.org/support/plugin/albert-ai-butler/) ## Descrição ChatGPT and Claude, connected in three steps. Your AI assistant knows your site, writes real blocks, and only does what you allow ### Let your AI assistant actually run your WordPress site You already ask ChatGPT or Claude to plan posts, rewrite copy and answer questions about your business. Then you paste the result into WordPress by hand, and fix the formatting. Albert removes that step. Connect your AI assistant to your site once, and it writes, edits and files your content directly, in real WordPress blocks, inside limits you set. No copy and paste, no plugin-specific chat window, no code. ### Connect in three steps Copy your site’s connection URL, paste it into your assistant, approve the request. That is the whole setup, and it is the same for every assistant. Albert walks you through it per assistant, with the exact steps for the one you use, so there is nothing to look up. ### Albert speaks block editor Most AI plugins hand WordPress a wall of HTML and leave you to clean it up. Albert does not. * **Real blocks, not raw HTML.** Headings, lists, quotes, images, buttons, columns and groups come back as proper blocks you can edit like anything else. * **One block at a time.** Change, add, move or remove a single paragraph without your assistant rewriting the whole page. * **No “this block contains unexpected content”.** Albert checks blocks as they are written and corrects the assistant before the content reaches your post. * **Classic editor too.** On a classic site, content is read and saved as HTML instead. Both work. ### Your assistant knows your site An assistant that does not know your site invents things: brand colours you never chose, a tone that is not yours, categories that do not exist. * **Write your instructions once.** Your tone, your vocabulary, anything it must never touch. Albert sends them with every conversation. * **Your site describes itself.** Language, timezone, theme colours and fonts, post types, taxonomies and shop settings go along too, but only when your theme genuinely declares them. * **See exactly what is sent**, and switch off any part an assistant does not need. * **Your text is information, never orders.** Content from your site can shape subject matter and tone. It can never change what an assistant is allowed to do. ### You decide what it may do Not every guest needs a key to every room. * **Every action listed and labelled** Read, Write or Delete, with its own switch. Changes save instantly. * **Write and delete start switched off.** You turn on exactly what you want, and nothing else. * **Your WordPress roles still apply.** An assistant can never do more than the person who approved it. * **New actions arrive switched off**, so a plugin update never quietly widens what an assistant can reach. * **Revoke any connection at any time.** ### Personal data stays private Albert hides your visitors’ and customers’ details, names, email addresses, phone numbers and postal addresses, before anything reaches an assistant. Choose **Strict**, **Balanced** or **Off**. New sites start on Strict. Reveal the real details only when you ask, and only if your own account is allowed to see them. ### See everything that happened * **Every call is recorded**: which action, which assistant, which user, how long it took. * **Blocked is not Failed.** A request your own rules refused reads differently from one that broke. * **Needs your attention** surfaces standing problems on the dashboard, and stays quiet when there are none. ### Works with the assistant you already use Claude Desktop, claude.ai, Claude Code, ChatGPT, Cursor, VS Code, or anything else that speaks the Model Context Protocol. Albert turns your site into an MCP server, so the same connection URL works everywhere and you are never locked to one vendor. Connections use OAuth 2.0 with short-lived, self-refreshing tokens. No password is ever shared with an AI company. ### What your assistant can do * **Posts and pages**: find, view, create, update and delete, block by block. * **Media**: browse the library, set featured images, and receive files your assistant sends you directly. * **Users and taxonomies**: find and manage users, categories, tags and custom terms. * **WooCommerce**: look up products, orders and customers when WooCommerce is active. * **Anything you build**: register your own actions with the WordPress Abilities API. ### Go further with Albert Premium [Albert Premium](https://albertwp.com) adds per-role and per-user permission rules, your own custom post types, and a full activity log with filters and retention. Read the setup guide at [albertwp.com/docs](https://albertwp.com/docs/). Every well-run site deserves a proper butler. Albert checks credentials at the door, and shows the guest only the rooms you opened. ### Privacy Policy Albert does not collect, store, or transmit any user data to external servers. All authentication tokens are stored locally in your WordPress database. When you authorize an AI assistant, that assistant will have access to perform actions on your WordPress site according to the permissions you grant. You control which abilities are enabled and can revoke any session at any time. ### Credits Developed by Mark Jansen – Your Mark Media Website: https://yourmark.nl Plugin URL: https://wordpress.org/plugins/albert/ Built with: * league/oauth2-server for OAuth 2.0 implementation * Model Context Protocol (MCP) for AI assistant connectivity * WordPress Coding Standards ## Capturas de tela [⌊The Albert dashboard: setup status, how many abilities are switched on, recent AI assistant activity, and anything that needs a decision from you⌉⌊The Albert dashboard: setup status, how many abilities are switched on, recent AI assistant activity, and anything that needs a decision from you⌉[ The Albert dashboard: setup status, how many abilities are switched on, recent AI assistant activity, and anything that needs a decision from you [⌊The Connections screen: your MCP endpoint, who is connected, who may connect, and step-by-step setup for Claude, ChatGPT, Cursor and the rest⌉⌊The Connections screen: your MCP endpoint, who is connected, who may connect, and step-by-step setup for Claude, ChatGPT, Cursor and the rest⌉[ The Connections screen: your MCP endpoint, who is connected, who may connect, and step-by-step setup for Claude, ChatGPT, Cursor and the rest [⌊The Abilities screen: every action an AI assistant can take, labelled Read, Write or Delete, each with its own instant-save switch⌉⌊The Abilities screen: every action an AI assistant can take, labelled Read, Write or Delete, each with its own instant- save switch⌉[ The Abilities screen: every action an AI assistant can take, labelled Read, Write or Delete, each with its own instant-save switch [⌊The Context screen: write instructions for your assistant and see exactly what Albert tells it about your site, section by section⌉⌊The Context screen: write instructions for your assistant and see exactly what Albert tells it about your site, section by section⌉[ The Context screen: write instructions for your assistant and see exactly what Albert tells it about your site, section by section [⌊The Skills screen: the task guides Albert ships, so you can read the exact guidance a connected assistant follows⌉⌊The Skills screen: the task guides Albert ships, so you can read the exact guidance a connected assistant follows⌉[ The Skills screen: the task guides Albert ships, so you can read the exact guidance a connected assistant follows ## Instalação #### Automatic installation 1. Go to **Plugins > Add New** in your WordPress dashboard. 2. Search for **Albert**. 3. Click **Install Now**, then **Activate**. 4. Go to **Albert > Connections** and add yourself as an allowed user. 5. Copy the connection URL and paste it into your AI assistant. 6. Approve the request when prompted. You are connected. #### Manual installation 1. Download the plugin ZIP from WordPress.org. 2. Go to **Plugins > Add New > Upload Plugin**. 3. Upload the ZIP and click **Install Now**, then **Activate**. 4. Follow steps 4 to 6 above. #### After activating Write and delete actions start switched off. Go to **Albert > Abilities** and switch on what you want your assistant to be able to do. Everything else works out of the box. ## Perguntas frequentes ### Which AI assistants can I connect? Claude Desktop, claude.ai, Claude Code, ChatGPT, Cursor, VS Code, and any other assistant that supports the Model Context Protocol. The connection steps are the same for all of them, and Albert shows the exact steps for the one you pick. ### Do I need to know anything technical? No. Copy a URL, paste it into your assistant, approve the request. There are no config files, no API keys to generate and no code. ### Can my AI assistant break my site? It can only do what you switched on. Write and delete actions start off, new actions added by an update also start off, and every action still obeys your WordPress roles, so an assistant can never do more than the person who approved it. You can revoke a connection at any time, and the activity log shows everything that was done. ### Will the content look right in the block editor? Yes. Albert writes real WordPress blocks, headings, lists, images, columns and the rest, not a wall of HTML pasted into one paragraph. It validates blocks as they are written, so you do not get the “this block contains unexpected content” warning. Classic editor sites are supported too. ### Does my AI assistant see my visitors’ and customers’ personal data? Not by default. Albert hides names, email addresses, phone numbers and postal addresses before anything is sent. Choose Strict, Balanced or Off, and reveal the real details only when you ask. ### How does Albert know anything about my site? You write instructions once, and Albert sends them with every conversation along with your language, timezone, theme colours and fonts, content types and shop settings. You can preview exactly what is sent and switch off any part of it. ### Is my AI assistant connection secure? Yes. Connections use OAuth 2.0, the same standard as Google and GitHub. Your assistant gets a short-lived token that refreshes itself, and no password is ever shared. Revoke any connection from the Connections screen. ### Does it cost anything? Albert is free. [Albert Premium](https://albertwp.com) is optional and adds per- role and per-user permission rules, custom post type support, and a full activity log with filters and retention. ### Do I need WooCommerce? No. Albert works with WordPress core out of the box. WooCommerce actions appear automatically when WooCommerce is active. ### Can I add my own actions? Yes. Register them with the WordPress Abilities API and they appear on the Abilities screen alongside Albert’s own. See [albertwp.com/docs](https://albertwp.com/docs/). ### Does this work with multisite? Albert is built for single-site installations. Multisite support is on the roadmap. ### What are the requirements? WordPress 6.9 or higher, PHP 8.1 or higher (8.3+ recommended), MySQL 8.0+ or MariaDB 10.5+, HTTPS (OAuth 2.0 requires it), and any permalink setting other than Plain. ### Where do I get support? Documentation at [albertwp.com/docs](https://albertwp.com/docs/), or the [WordPress.org support forums](https://wordpress.org/support/plugin/albert/). ## Avaliações ![](https://secure.gravatar.com/avatar/92b7d005d1ba6b94b4e69814a40933f600fdcdcb097f2e1b5e4ae23d53535ee0? s=60&d=retro&r=g) ### 󠀁[Fantastic plugin for developers](https://wordpress.org/support/topic/fantastic-plugin-for-developers-3/)󠁿 [primerpizza](https://profiles.wordpress.org/primerpizza/) 5 agosto, 2026 2 respostas This plugin is the first time in months I've been exited about anything WordPress- related. I only just installed and tested it and I already cannot imagine developing without it.Thanks for your work, Mark Jansen. ![](https://secure.gravatar.com/avatar/d07c4df4d79430f3e31b6058b838903c57f63639111c76fb80431831c61c663e? s=60&d=retro&r=g) ### 󠀁[a clean way to let ChatGPT actually do things in WordPress](https://wordpress.org/support/topic/a-clean-way-to-let-chatgpt-actually-do-things-in-wordpress/)󠁿 [Marinus Klasen](https://profiles.wordpress.org/mklasen/) 15 junho, 2026 I needed something to sit between ChatGPT/Claude and WordPress so end users could drive the site by just talking, like “create a project for this client” or “add this document” (based on the conversation context). I was dreading wiring up MCP and OAuth myself. Turns out I didn’t have to! My non-technical users connect their assistant by pasting one MCP URL and signing in with their normal WordPress account through oauth, and because of that, every action respects existing WordPress capabilities, so the AI can’t do anything the user couldn’t. Albert builds on the WordPress Abilities API, so I added my own AI-callable actions by writing a few small classes (id, description, input schema, permission callback) and they showed up as MCP tools right away and in Albert’s admin page with enable/disable toggles. ![](https://secure.gravatar.com/avatar/f8836eece576026e99b8d35323043da4431ffd244efa961fa07f52ea414c2811? s=60&d=retro&r=g) ### 󠀁[First! Great plugin to connect WordPress to GPT.](https://wordpress.org/support/topic/first-great-plugin-to-connect-wordpress-to-gpt/)󠁿 [Danny van Kooten](https://profiles.wordpress.org/dvankooten/) 2 junho, 2026 I was looking for a better way to give GPT access to my WordPress site. Previously I would allow it to connect using WP CLI over SSH, but it's hard to manage (scoped) permissions that way. With Albert I was able to allow my AI agent access to my WordPress sites with very granular permissions, so I could be sure it would not accidentally perform a destructive action. Installation was smooth. Plugin setting pages look clean. No PHP errors or notices in my logs. Glad I took the plunge and gave this plugin a try. [ Leia todas as 3 avaliações ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/) ## Colaboradores e desenvolvedores “Albert – Connect AI Assistants to WordPress” é um programa de código aberto. As seguintes pessoas contribuíram para este plugin. Colaboradores * [ Albert ](https://profiles.wordpress.org/albertai/) * [ Mark Jansen ](https://profiles.wordpress.org/mark-jansen/) [Traduzir o “Albert – Connect AI Assistants to WordPress” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/albert-ai-butler) ### Interessado no desenvolvimento? [Navegue pelo código](https://plugins.trac.wordpress.org/browser/albert-ai-butler/), consulte o [repositório SVN](https://plugins.svn.wordpress.org/albert-ai-butler/) ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/albert-ai-butler/) por [RSS](https://plugins.trac.wordpress.org/log/albert-ai-butler/?limit=100&mode=stop_on_copy&format=rss). ## Registro de alterações #### 1.4.2 Fixes AI assistants that could not connect to some sites. **Improvements** * AI assistants can’t connect when your permalinks (Settings → Permalinks) are set to “Plain”. Albert’s Dashboard now tells you when that’s the case, with a link to change it. Any other permalink setting works. **Fixes** * Claude Code and some other AI assistants stopped at the sign-in step with an error about your site’s sign-in details. They now find everything they need and connect. * AI assistants such as ChatGPT could not connect to sites whose page addresses include /index.php/ (for example example.com/index.php/about/). Albert now uses addresses that work with your permalink setting. **Developer** * The authorization server metadata now advertises `jwks_uri`, served from a new` albert/v1/oauth/jwks` REST route that publishes the token signing key’s public half as an RFC 7517 JSON Web Key Set. Clients that validate the metadata before authenticating (Claude Code’s MCP SDK requires `jwks_uri` to be a string, though RFC 8414 marks it optional) previously failed discovery outright. * Discovery now answers the RFC 8414 §3.1 and RFC 9728 §3.1 canonical path-insertion URLs (`/.well-known/oauth-authorization-server/` and `/.well-known/ oauth-protected-resource/`), not only the OIDC append form. These are root `.well-known` URLs, so on hosts that intercept a root `/.well-known/` the mid-path append form remains the one that works. * Every URL Albert advertises (issuer, endpoints, `resource_metadata`, the MCP endpoint under `albert/mcp/external_url`, `ClientRegistration::get_endpoint_url()`) now routes through `index.php` when the permalink structure does, and uses `rest_get_url_prefix()` instead of a hard-coded `wp-json`. New `ServerMetadata::url()`. Pretty-permalink sites get the same URLs as before, so existing connections are unaffected. * `ServerMetadata::base_url()` now delegates to `Server::get_base_url()`, so `albert/ mcp/external_url` is read once per request and validated in one place. **Credits** * [Marinus Klasen](https://profiles.wordpress.org/mklasen/) for reporting the Claude Code sign-in problem. * [Sébastien](https://wordpress.org/support/users/seb94100/) for reporting the / index.php/ connection problem, with the logs that pinpointed it. #### 1.4.1 Fixes AI assistants failing to connect, including on managed hosts (such as SiteGround and Servebolt) that handle the sign-in discovery address themselves. **Fixes** * AI assistants using the newest sign-in method could fail to connect. They connect again now. * AI assistants could not sign in on some managed hosts (such as SiteGround and Servebolt) that answer part of the sign-in discovery themselves. Albert now serves it where those hosts pass it through, so sign-in works with no manual setup. **Developer** * Discovery is now RFC 9728 / RFC 8414 conformant: `resource_metadata` in `WWW- Authenticate`, one Protected Resource Metadata source listing the issuer, and the issuer served at a mid-path `.well-known` URL that hosts intercepting a root`/. well-known/` leave alone. Adds the `albert_oauth_discovery` Site Health test. * The issuer is now a path, so a connected client that re-runs discovery re-authorises once; live connections keep working. #### 1.4.0 Release date: 2026-09-03 Albert 1.4.0 tells connected assistants what your site actually is, so they stop guessing. Assistants can also send you files directly, and every admin screen has been rebuilt on one design system. Day-one support for WordPress 7.1. #### Features * New **Albert → Context** screen. Write instructions for connected assistants, and send your site’s language, timezone, theme colours and fonts, content types and shop settings with every conversation. * Preview exactly what is sent, and switch off any section an assistant does not need. * Text from your site (your instructions, post content, product descriptions) is now marked as information rather than orders, so it can never change what an assistant is allowed to do. * Assistants can send you a file directly. Where Albert could previously only fetch media from a web address, an assistant that already has the file now requests a single-use upload link and posts the bytes straight to your media library. * New size limit for those uploads under **Albert → Settings → Uploads**. * New **Albert → Skills** screen, listing the task guides Albert and its add-ons ship. Guides tell an assistant how to handle a job on your site, such as writing blocks correctly. Open one to read the exact guidance an assistant follows. * Assistants now read those guides themselves. Each is offered by name at the start of a conversation, and only when it applies to your site. * New Site Health check that reports when the MCP endpoint is not registered, instead of failing with a 401 that looks like an authentication problem. #### Enhancements * Every Albert screen has been rebuilt: Dashboard, Settings, Connections, Abilities and the two new screens now share one design system, one set of controls and one visual language. * Albert picks up the admin colour scheme from your WordPress profile instead of always being blue. * A row of links across the top of every Albert screen replaces trips back to the sidebar. * The Connections screen now shows the endpoint, who is connected, who may connect, and setup steps per assistant. You can name or rename a connection inline. * Choosing who may connect is a searchable picker rather than a dropdown listing every user, so it stays fast on large sites. * You can name a connection at the moment you approve it. * Invitations nobody accepts now expire, connections approved but never used are dropped, and idle connections can be expired on a schedule. All configurable, all logged. * A call Albert refused now reads as **Blocked** rather than Failed. A tool that ran and truthfully answered “there is no such post” counts as a success. * An assistant that uses a wrong parameter name is now told which name it used and which names the tool takes. Previously the wrong name was silently discarded and the assistant could get a successful answer that ignored half its request. * An expired session now tells the client its token expired, instead of a bare refusal indistinguishable from never having connected. * A failed connection records which of six reasons it actually was, rather than one generic message for all of them. * Many tools carry a short note about the mistake that is easiest to make with them. Assistants read these only when they use the tool. * New installs start on Strict privacy. Existing sites keep their setting. * Settings are now sanitised on the way into the database, so a value written by code or WP-CLI is checked exactly like one typed into the form. * A setting fixed in code shows as read-only and names what owns it, rather than appearing editable and being silently overwritten. * The Abilities and Skills screens switch to a stacked list on narrower screens, so nothing is hidden behind a sideways scrollbar on a laptop or tablet. Pick a layout yourself and it stays picked. * Accessibility pass across the admin: contrast on faint borders and switches, keyboard reachability, focus after dismissing an item, touch target sizes and screen reader announcements. * On WordPress 7.1, server-only details are stripped from tool descriptions before they reach an assistant. This covers tools added by other plugins too. #### Bugfixes * Fixes the block editor guide never reaching your site. It has been in the source since 1.2.0 but was left out of every release package, so assistants have been writing blocks without the guidance the 1.2.0 release described. The Skills screen is what made it visible, by counting the guides out loud. * Fixes the Abilities table scrolling sideways on smaller screens. Below roughly 1450px the columns overflowed, and the on/off switch sits at the right-hand end, so the one control the screen exists for was the first thing to disappear. * Fixes assistants being unable to read product categories, or any category or tag set without an explicit REST base. Albert asked the wrong question and reported them as unavailable. * Fixes `albert/find-taxonomies` and `albert/find-terms` failing every call on WordPress 7.1, which made taxonomy discovery impossible. * Fixes Albert’s MCP endpoint failing to register when another plugin bundles its own copy of the MCP library. Albert now shares one copy, so both endpoints work. * Fixes data migrations being skipped after a deactivate, update, reactivate cycle, which left the update permanently marked as done without having run. * Fixes the dashboard reporting that all abilities were enabled, because the total and the enabled figure were the same number counted twice. * Fixes privacy mode not saving, because the screen and the save routine disagreed about the option name. * Fixes a privacy mode set in code showing as editable. * Fixes the nightly cleanup hiding connections that still worked. A connection idle overnight disappeared from the admin while continuing to call the site, so it could not be revoked. * Fixes connections being counted elsewhere by a looser rule with no expiry check. * Fixes declared minimums and maximums not being enforced outside the browser, and negative numbers losing their sign instead of being clamped. * Fixes the activity list fade permanently covering its last row. * Fixes “ability not found” notices on the dashboard. * Fixes the `.well-known` discovery document not advertising the authentication method Albert issues desktop clients with. * Fixes a rejected endpoint override filter falling back silently. The endpoint card now says where the address comes from. #### Security * Revoking a single session now revokes that session’s refresh token. It previously ended only the access token, so the assistant reconnected on its own within the hour while the screen said the session had been revoked. Revoking all sessions was never affected. * `albert/upload-media` now checks file types against the current user’s own allowed types instead of the site-wide default. An `unfiltered_upload` capability can no longer widen what it accepts. * Failed database writes when issuing OAuth authorisation codes, access tokens and refresh tokens are no longer ignored. All three now fail immediately instead of surfacing later as an unrelated error. * `WWW-Authenticate` is now sent on every 401 from the MCP endpoint. Previously an expired token skipped the header entirely. #### Developer * New `Albert\Context` module, with filters `albert/context/enabled`, `albert/context/ instructions`, `albert/context/sections`, `albert/context/site` and `albert/context/ skills`. * New `albert/skills/registry` filter registers a skill as data, with declared preconditions. A skill is offered only when its preconditions hold, and an unrecognised condition fails closed. * New `albert/get-skill` ability returns a guide’s Markdown body by slug, gated on `edit_posts`. * New `albert/create-upload-link` ability and `POST|PUT /albert/v1/media/uploads` endpoint, backed by the reusable `Core\Tokens\TokenService`. New `albert/media/ upload_link_max_bytes` filter. * Abilities’ “Supplier” is renamed to “Source”: `AbilitiesRegistry::get_sources()` and `albert/abilities/sources`. The old method, filter and payload keys still work, deprecated rather than removed. * New `albert/abilities/invoked` action, relayed from WordPress 7.1’s `wp_ability_invoked`. Fires for every invocation whatever the outcome, including denied and short-circuited calls. Inert below 7.1. * New `Albert\Logging\Outcome` classifies every logged outcome as `success`, `warning` or `error`. The ability log gains `failure_stage` and `privacy_mode`, and drops` ip_address`, `referrer` and `request_id`. * New `albert/logging/api_surface_codes` filter, so an add-on’s own not-found codes classify correctly. * Settings API: add-ons can name their own card, attach a unit with `suffix`, add detail with `info`, and declare `min` and `max` once to drive both the control and the sanitiser. New filters `albert/settings/value/{option}`, `albert/settings/ value_source/{option}` and `albert/settings/validator/{option}`. `show_in_rest` now works. * New dashboard filters: `albert/dashboard/stats`, `albert/dashboard/attention`,` albert/dashboard/suggestions`, `albert/dashboard/recommendations` and `albert/ dashboard/show_resources`. * New OAuth filters `albert/oauth/access_token_ttl`, `albert/oauth/refresh_token_ttl` and `albert/oauth/auth_code_ttl`, plus an `albert/oauth/token_request_failed` action carrying the specific failure reason. * Every object-typed input schema now registers with `additionalProperties => false`, set once in `BaseAbility::prepare_input_schema()`, so add-ons inherit it. * New design system. `albert-tokens.css` holds colour, spacing, type, radius and motion in `oklch()`; `albert-primitives.css` holds shared components. Add-ons declare `albert-primitives` as a stylesheet dependency. * **Breaking for add-ons.** The 56 value-named custom properties in `admin-settings. css` (`--albert-primary`, `--albert-font-lg`) are replaced by role-named ones(`-- albert-color-accent`, `--albert-font-size-section-title`) with no alias layer. Albert Premium Service ships the matching migration and must be updated alongside this release. * The bundled MCP adapter moves to 0.6.1 and now loads unscoped through Jetpack Autoloader instead of being prefixed with Mozart. Albert, WooCommerce and the standalone MCP Adapter plugin share one adapter and each keep their own server. Mozart, `vendor-prefixed/` and the `Albert\Vendor\` namespace are gone. * WordPress 7.1 support is feature-detected in `Albert\Support\WpCompat`. Tool schemas pass through `wp_prepare_json_schema_for_client()`, `is_mcp_public()` adopts the `meta.mcp.public ?? meta.public` precedence, and `get_all_raw()` reads the registry directly so a third-party filter cannot make Albert lose track of a registered ability. * Object-typed input schemas no longer claim their default is an array. * Stylesheets and scripts are versioned on file modification time, so a change during a release cycle is never served stale. * CI compiles and lints the admin screens on every pull request, and adds WordPress 7.0 and trunk rows. #### Credits * [Marinus Klasen](https://github.com/mklasen) for the idea behind direct file uploads. * [Jonathan de Jong](https://github.com/jonathan-dejong) for reporting the taxonomy failures, the output schema failures and the MCP adapter conflict. #### 1.3.1 A security update for how AI assistants connect. **Security** * Connecting an assistant now requires the exact web address it will return you to. The old catch-all that accepted any address is gone, and every connection request is matched against that exact address. * The approval screen now shows where the assistant will send you, and how recently the app was set up, so an unexpected request is easier to spot. * Apps that connect through their own link (such as some desktop assistants) are checked more strictly and secured without relying on a shared secret. * Stricter checking of return addresses, a limit on how many a single app can register, and a cap on the total number of connected apps. **Developer** * New `albert/oauth/allowed_redirect_schemes` filter to restrict redirect URI schemes to an explicit allowlist. #### 1.3.0 Two headline changes: the Abilities screen has been rebuilt from scratch, and personal data is now kept private from AI assistants automatically. **Features** * Rebuilt Abilities screen — a fast, modern list with search, filter by category or supplier, sort, and pagination, matching the rest of the WordPress admin. * Switch abilities on or off instantly, one at a time or in bulk — no Save button. * A detail panel on every ability showing its inputs, the permission it needs, and when it last ran. * Privacy mode — personal data (names, email addresses, phone numbers, and postal addresses) is redacted from AI results before it leaves your site. Choose Strict, Balanced, or Off to control how much is hidden. * Reveal the real personal details only when you explicitly ask, gated by your own WordPress capabilities. **Improvements** * The Abilities screen was rebuilt for accessibility throughout — full keyboard and screen-reader support, with clearer focus states and contrast. * The three core tools an assistant uses to discover and run abilities can no longer be switched off, and repair themselves on load, so a connection never breaks after an update. **Developer** * New extension points on the Abilities screen let add-ons plug straight in — this powers Albert Premium’s per-role and per-user permission rules. * New `albert/privacy/*` filters let add-ons protect their own fields — the WooCommerce add-on uses these to strip payment and card data. #### 1.2.0 Albert now understands the WordPress block editor — a big step up in how AI assistants read and write your content. **Features** * Block editor support — assistants work with real WordPress blocks instead of raw HTML. They read a post as a clean, structured outline and compose new content with proper blocks: headings, paragraphs, lists, quotes, images, buttons, columns, and groups. * Edit one block at a time — change, add, move, or remove a single block without disturbing the rest of the page. No more rewriting a whole post to fix one paragraph. * Classic editor support — content on classic-editor sites is read and saved as HTML, so Albert works whichever editor you use. * Built-in guidance — Albert ships a playbook and reference data that teach connected assistants how your site’s blocks work, so they produce better content out of the box. **Improvements** * Cleaner content, fewer errors — Albert validates blocks as they’re written and steers the assistant to correct mistakes, so you avoid the block editor’s “this block contains unexpected content” warnings. * Assistants only use the blocks your site, and the connected user, are actually allowed to use. * Long posts are paged automatically, so big content is never cut off mid-way when an assistant reads it. * Safer updates — abilities added by a plugin update now start switched off. An update will never silently expand what an AI assistant can do on a site you’ve already set up. #### 1.1.1 A bug-fix release. **Fixes** * OAuth discovery endpoints (`/.well-known/oauth-protected-resource`, `/.well-known/ oauth-authorization-server`) are now reachable when the request arrives with a trailing slash. Some hosts add one at the edge, after which WordPress’s canonical redirect would strip it again, producing a redirect loop or a 404. The endpoints now respond identically with or without the slash. **Credits** * Reported by [Marinus Klasen](https://profiles.wordpress.org/mklasen/). #### Earlier versions Releases before 1.1.1 are listed in `changelog.txt`, bundled with the plugin. ## Meta * Versão **1.4.2** * Última atualização **3 semanas atrás** * Instalações ativas **30+** * Versão do WordPress ** 6.9 ou superior ** * Testado até **7.1.3** * Versão do PHP ** 8.1 ou superior ** * Idioma * [English (US)](https://wordpress.org/plugins/albert-ai-butler/) * Tags * [AI](https://br.wordpress.org/plugins/tags/ai/)[ai assistant](https://br.wordpress.org/plugins/tags/ai-assistant/) [ChatGPT](https://br.wordpress.org/plugins/tags/chatgpt/)[Claude](https://br.wordpress.org/plugins/tags/claude/) [mcp](https://br.wordpress.org/plugins/tags/mcp/) * [Visualização avançada](https://br.wordpress.org/plugins/albert-ai-butler/advanced/) ## Classificações 5 de 5 estrelas. * [ 3 avaliações com 5 estrelas ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/?filter=5) * [ 0 avaliação com 4 estrela ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/?filter=4) * [ 0 avaliação com 3 estrela ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/?filter=3) * [ 0 avaliação com 2 estrela ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/?filter=2) * [ 0 avaliação com 1 estrela ](https://wordpress.org/support/plugin/albert-ai-butler/reviews/?filter=1) [Sua avaliação](https://wordpress.org/support/plugin/albert-ai-butler/reviews/#new-post) [Ver todas avaliações](https://wordpress.org/support/plugin/albert-ai-butler/reviews/) ## Colaboradores * [ Albert ](https://profiles.wordpress.org/albertai/) * [ Mark Jansen ](https://profiles.wordpress.org/mark-jansen/) ## Suporte Problemas resolvidos nos últimos dois meses: 2 de 3 [Ver fórum de suporte](https://wordpress.org/support/plugin/albert-ai-butler/)