WordPress Trac MCP Server
OfficialRelated Servers
Alternatives to WordPress Trac MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA 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.34 npm9MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to manage WordPress sites and create content with AI-generated featured images.13 npm2MIT
- 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.-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server for seamless WordPress.com integration, enabling AI assistants to connect to WordPress.com sites with OAuth authentication.12 npm5MIT

WordPress MCPofficial
AlicenseBqualityFmaintenanceA WordPress plugin that implements the Model Context Protocol to enable AI models and applications to interact with WordPress sites in a structured and secure way.570 npm941ISC- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to interact with GitHub repositories, issues, and pull requests.5 npmMIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: getChangeset retrieves commit details, getTicket fetches ticket information, getTimeline shows recent activity, getTracInfo provides metadata, and searchTickets searches for tickets. The descriptions clearly differentiate these functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using camelCase (e.g., getChangeset, getTicket, getTimeline, getTracInfo, searchTickets). The naming is predictable and readable throughout the set, with no deviations in style or convention.
With 5 tools, this server is well-scoped for its purpose of interacting with WordPress Trac. Each tool serves a specific, non-redundant function, and the count is appropriate for covering key operations like retrieving changesets, tickets, activity, metadata, and searching without being overwhelming.
The tool set provides strong coverage for querying and retrieving information from WordPress Trac, including tickets, changesets, activity, metadata, and search. A minor gap exists in the lack of tools for creating or updating tickets or changesets, but this is reasonable for a read-only or query-focused server, and agents can still perform core workflows effectively.