WordPress Trac
This MCP server provides AI assistants with access to WordPress.org Trac data through public CSV and RSS endpoints, built by James LePage using TypeScript and deployed on Cloudflare Workers for global edge performance. The implementation offers five core tools for searching through 60,000+ WordPress tickets with intelligent filtering, retrieving detailed ticket information including metadata and comments, accessing changeset information with full diff content, monitoring recent development activity through timeline feeds, and extracting project metadata like components and milestones. Built with custom XML-RPC client implementation, robust CSV parsing with fallback mechanisms, HTML scraping for changeset data, and WordPress-branded UI styling, it serves WordPress core contributors needing conversational access to development history, plugin developers researching similar issues and solutions, and AI assistants requiring comprehensive WordPress ecosystem knowledge for development guidance and issue tracking.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately.
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- cloud-infra
- Source
- PulseMCP
- Repository
- github.com/jameswlepage/trac-mcp
- Author type
- human
- Updated
- 2026-04-25
Use via MCP
Resolve WordPress Trac from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.