WordPress.org Trac▌
by courtneyr-dev
Search and monitor WordPress.org Trac tickets across Core, Plugins, Themes, Meta, bbPress, BuddyPress & GlotPress — view
Integrates with WordPress.org Trac instances across Core, Meta, Plugins, Themes, bbPress, BuddyPress, and GlotPress to search tickets, retrieve detailed information with comments, access changeset diffs, monitor timeline activity, and query metadata.
github stars
★ 2
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / WordPress core contributors tracking bugs and features
- / Plugin/theme developers researching known issues
- / Community members monitoring project development
capabilities
- / Search tickets across WordPress Trac instances by keywords
- / Retrieve detailed ticket information with comments and metadata
- / Access changeset diffs and commit information
- / Monitor timeline activity for recent changes
- / Query Trac metadata like components and milestones
what it does
Searches and retrieves detailed information from WordPress.org Trac bug tracking systems across all WordPress projects (Core, Meta, Plugins, Themes, bbPress, BuddyPress, GlotPress).
about
WordPress.org Trac is a community-built MCP server published by courtneyr-dev that provides AI assistants with tools and capabilities via the Model Context Protocol. Search and monitor WordPress.org Trac tickets across Core, Plugins, Themes, Meta, bbPress, BuddyPress & GlotPress — view It is categorized under developer tools. This server exposes 5 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install WordPress.org Trac in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
WordPress.org Trac is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
WordPress Trac MCP Server
Search and explore all WordPress.org Trac issue trackers directly from Claude, ChatGPT, or any AI assistant that supports MCP (Model Context Protocol).
No coding required to use this - just add the server URLs to your AI assistant config.
Based on trac-mcp by James LePage.
Quick Start (No Coding Required)
For Claude Desktop Users
-
Open your Claude Desktop config file:
- Mac:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- Mac:
-
Add the WordPress Trac servers to the
mcpServerssection:
{
"mcpServers": {
"wordpress-core-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-meta-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-meta-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-plugins-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-plugins-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-themes-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-themes-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-bbpress-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-bbpress-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-buddypress-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-buddypress-trac.meta-trac-wordpress.workers.dev/mcp"]
},
"wordpress-glotpress-trac": {
"command": "npx",
"args": ["mcp-remote", "https://mcp-server-wporg-glotpress-trac.meta-trac-wordpress.workers.dev/mcp"]
}
}
}
-
Restart Claude Desktop
-
You can now ask Claude things like:
- "Search Core Trac for accessibility issues"
- "Find recent plugin directory tickets"
- "Show me ticket #12345 from Meta Trac"
- "What's the latest activity on BuddyPress Trac?"
For ChatGPT Users
- Open ChatGPT Settings → Connectors tab
- Add Server → Import remote MCP server
- Use any of these URLs:
- Core:
https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - Meta:
https://mcp-server-wporg-meta-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - Plugins:
https://mcp-server-wporg-plugins-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - Themes:
https://mcp-server-wporg-themes-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - bbPress:
https://mcp-server-wporg-bbpress-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - BuddyPress:
https://mcp-server-wporg-buddypress-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt - GlotPress:
https://mcp-server-wporg-glotpress-trac.meta-trac-wordpress.workers.dev/mcp/chatgpt
- Core:
- Enable in Composer → Deep Research tool
What You Can Search
| Trac Instance | What It Tracks | Live URL |
|---|---|---|
| Core | WordPress core bugs, features, enhancements | core.trac.wordpress.org |
| Meta | WordPress.org website and infrastructure | meta.trac.wordpress.org |
| Plugins | Plugin directory issues and reviews | plugins.trac.wordpress.org |
| Themes | Theme reviews and directory | themes.trac.wordpress.org |
| bbPress | bbPress forum software | bbpress.trac.wordpress.org |
| BuddyPress | BuddyPress social networking plugin | buddypress.trac.wordpress.org |
| GlotPress | Translation platform | glotpress.trac.wordpress.org |
Available Commands
Once connected, you can ask your AI assistant to:
- Search tickets: "Search for REST API issues" or "Find tickets about block editor"
- Get ticket details: "Show me ticket #58000" or "What's the status of ticket 12345?"
- View changesets: "Show changeset r58000" or "What changed in revision 55000?"
- Check timeline: "What happened on Core Trac this week?"
- Get project info: "List the milestones for WordPress 6.7"
For Developers
Deploy Your Own Instance
# Clone the repository
git clone https://github.com/courtneyr-dev/meta-trac.git
cd meta-trac
# Install dependencies
npm install
# Login to Cloudflare
npx wrangler login
# Deploy specific instances
npm run deploy:core # Core Trac
npm run deploy:meta # Meta Trac
npm run deploy:plugins # Plugins Trac
npm run deploy:themes # Themes Trac
npm run deploy:bbpress # bbPress Trac
npm run deploy:buddypress # BuddyPress Trac
npm run deploy:glotpress # GlotPress Trac
# Or deploy ALL at once
npm run deploy:all
Environment Variables
| Variable | Values | Default | Description |
|---|---|---|---|
TRAC_INSTANCE | core, meta, plugins, themes, bbpress, buddypress, glotpress | meta | Which Trac instance |
TRAC_BASE_URL | URL | (auto) | Override the base URL |
Local Development
# Start dev server
npm run dev
# Test with MCP Inspector
npx @modelcontextprotocol/inspector http://localhost:8787/mcp
# Run tests
npm run test:unit
# Type check
npm run type-check
API Testing
# Health check
curl https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev/health
# Search tickets
curl -X POST 'https://mcp-server-wporg-core-trac.meta-trac-wordpress.workers.dev/mcp' \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"searchTickets","arguments":{"query":"accessibility","limit":5}},"id":1}'
Architecture
- Runtime: Cloudflare Workers (global edge deployment)
- Language: TypeScript with Zod validation
- Protocol: Model Context Protocol (MCP)
- APIs: Public WordPress Trac CSV/RSS endpoints (no auth required)
Known Limitations
- Comment history not available via CSV API (visit ticket URL for full discussion)
- Components list requires sampling tickets to extract values
- Each Trac instance is a separate deployment
License
GNU General Public License v2 or later - see GPL License.
Contributing
Contributions welcome! This server demonstrates production-ready MCP servers with multi-instance support.
FAQ
- What is the WordPress.org Trac MCP server?
- WordPress.org Trac is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for WordPress.org Trac?
- This profile displays 35 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.4 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.4★★★★★35 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
Useful MCP listing: WordPress.org Trac is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Emma Martin· Dec 28, 2024
WordPress.org Trac has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Aarav Kim· Dec 8, 2024
According to our notes, WordPress.org Trac benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Aanya Sethi· Nov 27, 2024
Useful MCP listing: WordPress.org Trac is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Rahul Santra· Nov 19, 2024
According to our notes, WordPress.org Trac benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Aarav Garcia· Oct 18, 2024
Strong directory entry: WordPress.org Trac surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Layla Torres· Oct 14, 2024
WordPress.org Trac reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Pratham Ware· Oct 10, 2024
I recommend WordPress.org Trac for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Emma Jackson· Sep 25, 2024
WordPress.org Trac is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Tariq Jackson· Sep 21, 2024
According to our notes, WordPress.org Trac benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 35