AI Site Manager MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_AI_KEY | No | Scoped API key. Required unless using a key file; do not set both WP_AI_KEY and WP_AI_KEY_FILE. | |
| WP_AI_BASE | No | HTTPS API namespace URL; supports WordPress installed in a subdirectory and `https://example.com/?rest_route=/ai-site-manager/v1` | |
| WP_AI_KEY_FILE | No | Absolute path to a plain-text key file. Alternative to WP_AI_KEY; do not set both. | |
| WP_AI_TIMEOUT_MS | No | Request timeout, 1000–600000 milliseconds | 120000 |
| WP_AI_AUTH_HEADER | No | Authorization header to use: `Authorization` or `X-AISM-Key` | Authorization |
| WP_AI_MAX_UPLOAD_BYTES | No | Local upload limit, up to 1 GiB; WordPress/host limits also apply | 33554432 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aism_sitesA | List configured site connections (names, API base URLs, default). Keys are never shown. |
| aism_discoverB | Discover the connected site, key scopes/expiry, resources, approved settings and limits. Call first. |
| aism_guideB | Read the deployed AI Site Manager usage guide. |
| aism_schemaB | Read native schemas and endpoint arguments before working with a resource. |
| aism_content_listA | List/search posts, pages, media, terms, comments or discovered custom resources. Includes pagination headers. Also supports types, taxonomies and statuses. |
| aism_content_getA | Read one content, media, term or comment object. Use context=edit for raw fields. |
| aism_content_createB | Create a post/page draft, term, comment or another native resource. Posts/pages default to draft. Upload files with aism_media_upload. |
| aism_content_updateA | Update only supplied fields. Supports posts/pages, media alt text/caption, taxonomy relationships and comment moderation. |
| aism_content_deleteA | Trash an object when supported. force=true permanently deletes it. Media and terms generally require force=true. Only delete objects authorized by the operator. |
| aism_revisionsB | Read a post/page revision list or one revision. Revision mutation is unavailable. |
| aism_media_uploadB | Upload a local file using multipart. Does not download remote URLs. Host file-type/size rules and media:write apply. |
| aism_settings_listA | List exact approved option names and schemas; does not return values. |
| aism_settings_getA | Read one approved option value and its schema. |
| aism_settings_updateA | Replace the ENTIRE value of one approved option. Read it immediately before editing; preserve unrelated object fields. No compare-and-swap exists. |
| aism_plugins_listA | List installed plugins and their identifiers/status. |
| aism_plugin_installA | Install a WordPress.org plugin inactive. Requires plugins:write and native install capability. Installation adds executable code. |
| aism_plugin_uploadA | Install a new local plugin ZIP inactive without replacing existing plugins. Requires plugins:write plus native install/upload capabilities. |
| aism_plugin_updateA | Update an installed plugin. Omit file_path to use the WordPress-advertised update, or supply a local ZIP with the same plugin folder/main file and a newer version (companion 1.2.0+). ZIP replacement preserves activation and requires plugins:write plus update/upload capabilities. AI Site Manager cannot update itself; multisite mutations are unavailable. |
| aism_plugin_actionA | Activate/deactivate/update/delete an installed plugin. Deletion requires plugins:delete and an inactive plugin. Updates use the WordPress-advertised package. AI Site Manager cannot manage itself; multisite mutations are unavailable. |
| aism_themes_listA | List installed themes with stylesheet identifiers, versions and active/inactive status. Requires themes:read and native theme access. |
| aism_theme_installA | Install a WordPress.org theme inactive. Core may install a missing parent. Requires themes:write and install_themes. Installation adds executable code. |
| aism_theme_uploadA | Install a new local theme ZIP inactive without replacing existing themes. Requires themes:write plus native install/upload capabilities. |
| aism_theme_actionA | Activate/update/delete an installed theme using its stylesheet identifier from aism_themes_list. Activate another theme to deactivate the current one. Deletion requires themes:delete and cannot remove the active theme or its parent. Updates use the WordPress-advertised package. Multisite mutations are unavailable. |
| aism_migration_manifestA | Read a site's migration manifest: site UUID, URLs, versions, themes, plugins, content counts per post type/taxonomy, capabilities and what is not migrated. Requires migration:read (companion 1.4.0+). |
| aism_migration_exportA | Read one raw export page from a site (terms, posts of any type including attachments/menus/templates, comments or site settings) for inspection. aism_migration_run and aism_migration_copy do this automatically. |
| aism_migration_planA | Compare two configured sites before migrating: versions, missing/outdated themes and plugins, post types and taxonomies the target cannot store yet, a previous migration, and recommended steps. Read-only. |
| aism_migration_transfer_packageA | Install a plugin or theme from the source on the target, inactive unless activate=true. from=source copies the exact installed files (custom and premium code included); from=wordpress.org installs by slug. Missing parent themes are transferred first. Installed plugins with an older version are updated from the source ZIP. Requires migration:read on the source and plugins:write/themes:write on the target. Adds executable code. |
| aism_migration_runA | Migrate a whole site in resumable steps: terms, media (original files), all content types including menus, templates, global styles and patterns, comments, site settings (front page, permalinks, widgets, customizer), then a finalize pass that remaps IDs and rewrites source URLs to the target. Returns within max_seconds; call again with the returned cursor until done is true. Re-running updates already migrated objects instead of duplicating them, so it also works as an incremental sync (with modified_after). Overwrites target settings and previously migrated objects. Users are not created; authors are matched by login/email. |
| aism_migration_copyA | Copy selected posts/pages (any type) from one site to another with their categories/tags, featured images, embedded media and reusable blocks, then remap IDs and URLs. Copying again updates the earlier copies. |
| aism_migration_statusA | Compare source content counts with what has been migrated into the target, and report finalize state. Read-only. |
| aism_migration_rollbackA | Undo a migration on the target: permanently delete posts, media files, terms and comments the migration created, restore site settings it changed, and forget its ID map. Objects matched to pre-existing target content are kept. Requires migration:delete on the target. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| ai-site-manager-guide | The default site’s authenticated AI Site Manager guide. |
TDQS
Scored across 31 tools
Most tools target clearly separate resources, but several boundaries are blurry: aism_plugin_update overlaps heavily with aism_plugin_action (which also performs updates), and the install/upload pairs (aism_plugin_install vs aism_plugin_upload, aism_theme_install vs aism_theme_upload) differ only by source in a way that requires careful reading. The migration cluster (run vs copy vs export vs transfer_package) is well described but still easy to misselect at a glance.
Nearly all names follow a `aism_<resource>_<action>` snake_case pattern, with a few bare-noun outliers (aism_sites, aism_revisions, aism_schema, aism_guide, aism_discover) that lack an action verb. Minor singular/plural drift (aism_plugins_list vs aism_plugin_install, aism_themes_list vs aism_theme_action) is readable but not perfectly uniform.
31 tools is well past the comfortable range for a single server, and the surface is inflated by near-duplicate pairs (plugin install/upload/update/action, theme install/upload/action). While the WordPress-management domain is genuinely broad, several of these could be collapsed into parameterized tools.
Coverage is strong: full content CRUD plus media upload, settings read/update, plugin and theme lifecycle, revisions, and an end-to-end migration lifecycle (plan, run, status, rollback, copy, export, package transfer). Gaps are modest and often explicitly documented as unsupported (revision mutation, self-update, multisite mutations, user creation, site connection management beyond listing).