Cowboy MCP
Related Servers
Alternatives to Cowboy MCP
- -
- AlicenseAqualityDmaintenanceEnables direct interaction with WordPress sites via Claude using the REST API, allowing reading, creating, updating, and deleting content securely with application passwords.20MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.9 npmMIT
- AlicenseNot gradedqualityAmaintenanceA free WordPress plugin that turns your site into a governed MCP server, exposing 153 curated WordPress abilities (posts, media, users, WooCommerce, ACF, SEO) as tools for AI agents like Claude and Cursor. Every ability is off by default, scoped to a least-privilege user, capability-gated, and logged.8GPL 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients like Claude Code and Cursor to control a WordPress site via 58 abilities over stdio (WP-CLI) or HTTP, self-contained and cloud-free.44GPL 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that turns WordPress sites into AI-operable surfaces by exposing CRUD primitives for posts, users, comments, and settings. It supports both local STDIO and remote HTTP transports, allowing AI assistants to manage content and site configuration directly.69 npm10MIT
- AlicenseNot gradedqualityCmaintenanceTurns any WordPress site into an MCP server, allowing AI clients to directly control files, database, WP-CLI, PHP, content, and more through declarative abilities without writing code.3GPL 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that bridges AI assistants to WordPress, enabling natural-language management of posts, pages, media, comments, users, plugins, and settings across multiple sites simultaneously.1-
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.