| 开发者 |
albertai
mark-jansen |
|---|---|
| 更新时间 | 2026年4月20日 22:22 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
albert-ai-butler folder to /wp-content/plugins/Albert works with Claude Desktop, ChatGPT, and any AI assistant that supports the Model Context Protocol (MCP). The connection process is the same for all: copy the endpoint URL, paste it into your assistant, and authorize.
Three steps: add yourself as an allowed user, copy the MCP endpoint URL, and paste it into your AI assistant. No technical knowledge required.
Yes. Albert uses OAuth 2.0 — the same standard used by Google, GitHub, and other major platforms. Your AI assistant receives a time-limited access token that automatically refreshes. No passwords are shared. All operations respect WordPress's built-in capability and role system, and you control exactly which abilities are enabled.
Albert ships with 25+ abilities covering WordPress core:
Yes. The abilities page lists every action your AI assistant can perform on your site, clearly labelled as Read, Write, or Delete. You toggle each one on or off individually — changes save instantly, no form to submit. Filter the list by text, category, or supplier to find what you're looking for. Write and delete abilities are off by default — you choose exactly what to enable. All actions also respect WordPress user capabilities, so your AI assistant can never do more than the authorized user could do manually.
No. Albert works with WordPress core out of the box. WooCommerce abilities appear automatically when WooCommerce is active.
Yes. Developers can register custom abilities using the WordPress Abilities API to expose any functionality to AI assistants. See the documentation at GitHub.
Albert is designed for single-site installations. Multisite support is on the roadmap.
albert/abilities/suppliers filter.password field on the Create User ability is now correctly flagged as required, so AI assistants get a clear validation error when it's missing instead of a vague failure.albert-ai-butler/v1) than the MCP server and discovery metadata (albert/v1), causing connection failures when clients followed the OAuth discovery spec. All endpoints now use albert/v1 consistently.albert/rest_namespace filter allows sites with a namespace collision to override the REST namespace.