Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WPSSH_KEYNoThe secret key for the single WordPress site, copied from Tools -> WP SSH in WordPress admin.
WPSSH_URLNoThe URL of a single WordPress site, e.g. https://example.com. Used with WPSSH_KEY.
WPSSH_MODENoSafety mode: 'read' (default), 'write', or 'full'.read
WPSSH_NAMENoOptional name for the single site. Defaults to 'default'.default
WPSSH_SITESNoJSON array for configuring several sites, e.g. [{"name":"shop","url":"https://shop.com","key":"..."}].
WPSSH_MAX_CHARSNoMaximum characters returned per call. Large responses are truncated with a hint.60000
WPSSH_ALLOW_HTTPNoSet to '1' to allow plain http:// URLs on a trusted private network.
WPSSH_TIMEOUT_MSNoRequest timeout in milliseconds.30000

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
wpssh_sitesA

List the WordPress sites this server can reach and the current safety mode ("read"). Never shows keys.

wpssh_pingA

Check that the WP SSH plugin is installed and reachable (no key needed). Returns plugin, version, site, label.

site_infoA

Site name, label, URL, WordPress / theme / WooCommerce versions. Good first call.

diagnosticsB

PHP/memory config, autoload options size, DB size and largest tables, transients/revisions counts, active caching plugins.

health_check_statusA

Result of the last hourly self-check (if health checks are enabled).

health_check_runA

Run the health check now (DB connection, PHP fatals in debug.log, low disk space, bridge disabled).

cron_listB

All scheduled WP-Cron events, soonest first.

option_getB

Read a WordPress option by name.

post_listC

List posts/pages/custom post types.

post_getB

Get one post by ID.

term_listC

List taxonomy terms.

menu_listB

List navigation menus.

media_listC

List media library items.

plugin_listA

List installed plugins and their active state.

theme_listA

List installed themes.

file_listB

List a directory inside wp-content.

file_readB

Read a file inside wp-content.

db_queryA

Run a read-only SQL query (SELECT / SHOW / DESCRIBE / EXPLAIN, one statement). Use LIMIT.

search_replace_previewA

DRY RUN of a serialization-safe search/replace across the database. Shows what would change, changes nothing.

order_listB

List WooCommerce orders (WooCommerce must be active).

order_getB

Full order detail including line items and addresses.

elementor_data_getB

Raw _elementor_data JSON of a page. Can be very large.

template_exportA

Export a page's Elementor data + settings so it can be copied to another site with template_import.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 23 tools

Disambiguation4/5

Most tools target clearly distinct resources and actions, such as order_list vs order_get and file_list vs file_read. There is mild overlap among site-introspection tools (wpssh_sites, wpssh_ping, site_info), but descriptions make their purposes distinguishable.

Naming Consistency3/5

Many tools follow a resource_verb pattern (order_list, post_get, option_get), but the set also includes bare nouns (diagnostics), prefixed tools (wpssh_sites, wpssh_ping), and mixed orderings (health_check_run, search_replace_preview). It remains readable but is not a single predictable convention.

Tool Count3/5

At 23 tools the surface is heavy for a WordPress admin server, though the breadth of resources justifies some of it. Several list/get pairs could be consolidated or grouped, making it borderline rather than well-scoped.

Completeness4/5

The read-only surface covers posts, terms, menus, media, plugins, themes, options, cron, orders, files, Elementor data, diagnostics, and raw DB reads. Some common read operations are missing (users, comments, WooCommerce products beyond orders), but db_query provides a workaround and the absence of writes is consistent with the stated read safety mode.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues