WordPress Trac

You can query WordPress.org Trac data with an MCP server that exposes tickets, changesets, and project metadata in a way that AI assistants can understand. It’s fast, searchable, and optimized for large data, enabling rich, contextual responses about WordPress development and project history.

How to use

Connect your MCP client to the WordPress Trac MCP Server to start asking questions about tickets, changesets, and project metadata. Use natural language queries and rely on the server’s intelligent routing to interpret ticket numbers, revisions, and keywords. You can search for tickets by keywords, fetch full ticket details, inspect changesets with diffs, and monitor recent activity.

How to install

Prerequisites: you need Node.js and npm installed on your machine. You will also need the Cloudflare Wrangler tool to deploy the server if you plan to publish to Cloudflare Workers.

Step 1: Clone the project repository and enter the directory.

Step 2: Install dependencies.

Step 3: Log in to Cloudflare to authorize deployment.

Step 4: Deploy the MCP server to the edge.

Step 5: Run a local development server for testing (optional). You can test with the MCP Inspector using the local endpoint.

Configuration and usage notes

There are two ways to connect to the server: a public HTTP MCP endpoint for standard clients and a local development workflow for testing.

Public MCP endpoint (HTTP): use this endpoint to connect your MCP client in standard workflows. The server is hosted at the public edge URL and requires no client-side authentication for browsing data.

Local development (stdio): run a local dev server to test commands directly. The development workflow uses a command like npm run dev to start the server locally, which typically exposes a testing interface at http://localhost:8787/mcp for inspection.

Available tools (standard MCP) allow you to search tickets, fetch ticket details, retrieve change sets, monitor timelines, and get trac metadata. ChatGPT Deep Research tools provide a simplified interface focused on search and fetch for streamlined research workflows.

Live demo

Live demonstration URL you can use to explore the MCP server functionality: https://mcp-server-wporg-trac-staging.a8cai.workers.dev.

Troubleshooting and notes

If you encounter connectivity issues, verify that your client is configured to the correct MCP endpoint and that the server is reachable from your network. For local testing, ensure Node.js and npm are installed and that you can access http://localhost:8787/mcp from your browser or inspector tool.

Security and access notes

Public endpoints do not require authentication for read access to Trac data. If you plan to compose or relay sensitive queries, consider implementing access controls on your client layer and apply best practices for API usage to avoid excessive querying.

Available tools

searchTickets

Search through WordPress Trac tickets with intelligent filtering by keywords, status, and other criteria.

getTicket

Retrieve comprehensive information about a specific ticket by ID, including descriptions, status, and metadata, with optional comments.

getChangeset

Access detailed information about code changes for a specific revision, including full diff content when requested.

getTimeline

Monitor recent WordPress development activity, returning a list of recent tickets and changes.

getTracInfo

Fetch organizational data such as components, milestones, and priorities.

search

ChatGPT Deep Research intelligent search that routes queries to tickets, changesets, or timeline data based on query type.

fetch

Retrieve detailed information about a specific item by ID, such as a ticket or a changeset, for in-depth research.