Cowboy MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
You are connected to the WordPress site "Cowboy MCP sandbox" at http://127.0.0.1:8765 (domain: 127.0.0.1). WordPress 7.1.4, theme "twentytwentyfive", table prefix "wp_".
IMPORTANT: Read the wordpress://tools/catalog resource first — it lists every available tool with a one-line description, grouped by category. Find the tool you need there, then call cowboy_run directly; use cowboy_discover only to search by keyword or to fetch a tool's full inputSchema.
Safety: Safe mode is ON. When ON, destructive tools require confirm: true. All non-read-only tools support dry_run: true to preview changes without executing. Never write into wp-content/mu-plugins/ (refused unless Power mode is on): must-use plugins cannot be paused by recovery mode, so a fatal there locks out wp-admin and this endpoint. Ship code as a regular plugin under plugins/ and activate it with wp_activate_plugin.
Beyond tools, use resources/list for read-only site data (site info, recent posts, plugin list, etc.), resources/templates/list for parameterized lookups like wordpress://posts/{id}, and prompts/list for guided workflows (site audit, SEO optimization, content migration, troubleshooting, security hardening, performance optimization).
Conventions: Use {prefix} as the table prefix in SQL (e.g. {prefix}posts). Plugin file paths use folder/file.php format (e.g. woocommerce/woocommerce.php). File operations are relative to wp-content/. Post statuses: publish, draft, pending, private, trash, future.
Always confirm destructive actions with the user before executing them.
This site exposes 89 tools via 2 gateway meta-tools. Categories:
options (1 tools): update WordPress options (with sensitive-option blocklist)
files (4 tools): read, write, list, delete files in wp-content
database (5 tools): raw SQL queries and writes (with safety blocklists)
system (4 tools): site info, WP-CLI, search-replace, site health
users (5 tools): list, read, create, update, and delete users, including role changes (with self-protection and privileged-role gating)
media (4 tools): list, upload, update, and delete media library attachments, including alt text
batch (2 tools): multi-tool sequencing, audit log retrieval
rollback (6 tools): undo changes from the journal, create/list/restore/delete database checkpoints
diagnostics (10 tools): error logs, HTTP requests, email testing, hooks, transients, REST routes, thumbnails, rewrite rules, site snapshots, connection self-test
content (8 tools): create, read, update, delete posts, pages, and custom post types
plugins (6 tools): list, activate, and deactivate plugins
themes (5 tools): list themes and switch the active theme
taxonomies (4 tools): list, create, update, and delete taxonomy terms
comments (4 tools): list, create, update, and delete comments and product reviews
menus (6 tools): list, create, update, and delete classic navigation menus and their items
gutenberg (8 tools): block editing, patterns, FSE templates, template parts, global styles, navigation
cache (4 tools): provider detect, flush, preload, settings
abilities (3 tools): abilities registered by other plugins through the WordPress Abilities API (WooCommerce, the AI plugin's core abilities, core...) - each runs its own permission check; not undoable
Workflow: read wordpress://tools/catalog to find a tool by name, then cowboy_run to execute it; use cowboy_discover to search by keyword or to get a tool's full inputSchema.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cowboy_discoverA | Search or browse available WordPress tools by keyword or category. Returns matching MCP tool definitions with name, description, inputSchema, and annotations. Examples:
|
| cowboy_runA | Execute a WordPress tool by name with arguments. Use cowboy_discover first to find the right tool and its inputSchema. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| wordpress-site-audit | Guided health, security, performance, and SEO audit of the WordPress site. |
| content-migration | Step-by-step content import with validation and rollback guidance. |
| seo-optimization | Analyze and optimize SEO across the WordPress site. |
| woocommerce-store-setup | Guided WooCommerce store configuration and optimization. |
| troubleshoot-issue | Diagnostic workflow for common WordPress problems. |
| bulk-content-update | Guided batch content operations with preview and safety controls. |
| security-hardening | Review and apply WordPress security best practices. |
| performance-optimization | Identify and fix WordPress performance bottlenecks. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Site Information | WordPress installation details, active theme/plugins, PHP version, etc. |
| Core Options | Key WordPress options (blogname, blogdescription, permalink_structure, etc.) |
| Current Theme Files | Directory listing of the active theme. |
| Theme functions.php | Contents of the active theme's functions.php file. |
| Theme style.css | Contents of the active theme's style.css file. |
| Database Schema | All database tables with column definitions. |
| Registered Post Types | All registered post types with their config. |
| Registered Taxonomies | All registered taxonomies. |
| .htaccess | Root .htaccess file (Apache sites only). |
| wp-config summary | Non-sensitive constants defined in wp-config.php. |
| Tool Catalog | Complete catalog of all available MCP tools organized by category with usage examples. Read this to discover what actions you can perform. |
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: cowboy_discover searches/browses tools, while cowboy_run executes a named tool. There is no overlap, and the descriptions explicitly guide the agent to discover before running.
Both tools follow the exact same cowboy_verb pattern (cowboy_run, cowboy_discover), with no deviations or mixed conventions.
Two tools is slightly below the typical 3-15 range, but it is appropriate for a discovery/execution gateway where the real surface is dynamic. Each tool earns its place and the minimal interface is intentional.
The pair covers the full gateway lifecycle: find a tool (with schema) and execute it. Category browsing and keyword search provide sufficient coverage for accessing the underlying WordPress toolset, with no obvious dead ends.