WordPress Trac MCP Server
OfficialServer 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.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchTicketsB | Search for WordPress Trac tickets by keyword or filter expression. Returns ticket summaries with basic info. |
| getTicketC | Get detailed information about a specific WordPress Trac ticket including description, comments, and metadata. |
| getChangesetC | Get information about a specific WordPress code changeset/commit including commit message, author, and diff. |
| getTimelineB | Get recent activity from WordPress Trac timeline including recent tickets, commits, and other events. |
| getTracInfoA | Get WordPress Trac metadata like components, milestones, priorities, and severities. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.