WordPress Trac MCP Server
OfficialThis server provides read-only access to WordPress Core Trac data via the Model Context Protocol. Here's what you can do:
Search Tickets (
searchTickets): Search for WordPress Trac tickets using keywords, ticket numbers, or structured filter expressions (e.g.,milestone=6.9&status=closed&resolution=fixed), with pagination support.Get Ticket Details (
getTicket): Retrieve full details of a specific ticket by ID, including its description, metadata, and recent comments.Get Changeset/Commit Info (
getChangeset): Fetch details about a specific SVN revision/commit, including the commit message, author, and an optional truncated diff.Get Timeline (
getTimeline): View recent Trac activity (tickets, commits, and other events) over a configurable number of past days.Get Trac Metadata (
getTracInfo): Retrieve reference data such as available components, milestones, priorities, and severities.Compatibility Endpoint (
/mcp/chatgpt): A simplified endpoint for search and fetch operations, supporting direct ticket numbers orr-prefixed changeset numbers.
Enables deployment of the MCP server on Cloudflare Workers for global edge distribution of the WordPress Trac data service.
Supports ChatGPT's Deep Research feature with a simplified interface for searching WordPress Trac data and fetching detailed information about tickets and changesets.
Transforms WordPress.org Trac into an AI-accessible knowledge base, providing comprehensive access to WordPress tickets, code changes, and development activity.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WordPress Trac MCP Serversearch for recent open tickets about the block editor"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WordPress Trac MCP server
A read-only Model Context Protocol server for WordPress Core Trac. It runs as a Cloudflare Worker and uses Trac's public HTML, CSV, RSS, and diff endpoints.
Live server:
Standard MCP:
https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcpSearch/fetch compatibility:
https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcp/chatgptHealth check:
https://mcp-server-wporg-trac-staging.a8cai.workers.dev/health
Tools
The standard /mcp endpoint provides:
Tool | Purpose |
| Search by keywords, ticket number, or structured filters |
| Read a ticket, its metadata, and recent comments |
| Read a changeset and an optional truncated diff |
| Read recent Trac activity |
| List components, milestones, priorities, severities, types, or statuses |
The /mcp/chatgpt compatibility endpoint provides search and fetch. Use a bare number for a
ticket and an r prefix for a changeset: 65739 and r58504.
Search filters
searchTickets accepts plain keywords, ticket numbers, or filter expressions joined with &:
{
"query": "milestone=6.9&status=closed&resolution=fixed",
"limit": 50,
"page": 2
}It also accepts status, component, milestone, and resolution as separate arguments. A
separate argument overrides the same field in query. Results include pagination metadata.
Related MCP server: WordPress MCP
Connect
Remote-capable MCP clients can connect directly to the standard endpoint. Clients that need a local
bridge can use mcp-remote:
{
"mcpServers": {
"wordpress-trac": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp-server-wporg-trac-staging.a8cai.workers.dev/mcp"
]
}
}
}For ChatGPT, add the compatibility endpoint as a custom app. See OpenAI's current MCP help because product labels and setup steps change.
Develop
Requirements: Node.js 22 or later and pnpm 10.
pnpm install
pnpm devRun the complete local quality gate:
pnpm checkThis runs TypeScript, Biome, Vitest, and a Cloudflare Worker dry-run build. See docs/testing.md for manual protocol and live-data checks.
Deployment requires a configured Cloudflare account:
pnpm deploy
pnpm deploy:productionDesign and safety
The server is read-only and has no Trac credentials.
Tool inputs receive runtime validation before any upstream request.
Upstream requests use the fixed
core.trac.wordpress.orghost.Responses are parsed from public Trac pages and machine-readable formats.
The Worker keeps no ticket cache or durable state.
Contribute
Keep tool schemas, runtime validation, tests, and documentation aligned. Run pnpm check before
opening a pull request.
License
GPL-2.0-or-later.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/WordPress/trac-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server