BeTheme MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BETHEME_MCP_SITES | No | JSON array of site configurations for multi-site mode. Overrides single-site settings. | |
| BETHEME_MCP_API_KEY | No | API key for the WordPress bridge plugin. | |
| BETHEME_MCP_BASE_URL | No | Base URL of the WordPress site (e.g., https://your-site.test). | |
| BETHEME_MCP_TIMEOUT_MS | No | Timeout for HTTP requests to WordPress (in milliseconds). | 10000 |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Verify that the MCP bridge and WordPress site are reachable. |
| authenticateA | Verify bridge credentials and return site capabilities. |
| list_sitesA | List the WordPress sites configured for this MCP server. |
| get_site_contextB | Return a safe summary of the WordPress site and theme context for an agent. |
| get_capabilitiesC | Return the capabilities exposed by the bridge and the current authentication context. |
| list_pagesB | List pages available in WordPress. |
| get_pageC | Retrieve a specific WordPress page. |
| create_pageC | Create a new page in WordPress. |
| update_pageC | Update an existing WordPress page. |
| publish_pageC | Publish a draft page. |
| delete_pageC | Delete a WordPress page. |
| get_page_builder_payloadC | Retrieve the stored BeBuilder payload for a page. |
| save_page_builder_payloadC | Persist a BeBuilder payload for a page. |
| list_templatesC | List available BeTheme templates. |
| get_templateB | Retrieve a specific BeTheme template. |
| create_templateC | Create a new BeTheme template. |
| update_templateC | Update an existing BeTheme template. |
| list_pluginsB | List installed or available plugins. |
| install_pluginC | Install and activate a plugin from the WordPress ecosystem. |
| activate_pluginC | Activate an installed plugin. |
| deactivate_pluginC | Deactivate an installed plugin. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_homepage_from_brief | Build a homepage from an agent brief |
| create_full_site_from_template | Create a full site from a template |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| site-context | |
| pages | |
| templates |
TDQS
Scored across 21 tools
Most tools are clearly scoped by resource and action, but install_plugin (which installs and activates) overlaps with activate_plugin, and update_page overlaps with publish_page and save_page_builder_payload. These fuzzy boundaries could cause an agent to pick the wrong tool.
The naming follows a consistent verb_noun snake_case pattern for most tools (list_pages, get_page, create_page, update_page, delete_page). Minor exceptions like health_check, authenticate, and save_page_builder_payload slightly break the pattern but do not make it unpredictable.
With 21 tools, the server sits in the heavy range. It covers sites, plugins, pages, templates, and builder payloads, but some utilities like health_check, authenticate, get_site_context, and get_capabilities overlap in purpose and could be consolidated.
Pages have full CRUD plus publish, but templates lack delete, plugins lack uninstall/update, and there is no apply-template-to-page operation. These are notable gaps for a BeTheme-focused WordPress server, though the core page workflow is covered.