Draft
Report WordPress Trac MCP tool capabilities and upstream 403 errors#2398
Conversation
Copilot
AI
changed the title
[WIP] Test WordPress Trac MCP for closed tickets
Report WordPress Trac MCP tool capabilities and upstream 403 errors
Jul 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Investigation of the
wordpress-tracMCP server against WordPress Core Trac, coveringsearchTicketsschema inspection, a filtered query for closed 7.1 milestone tickets, andgetTicketfor ticket 65127.Findings
searchTicketsschemaquery(required),component,status,limit(max 50)milestone,type, orfocusesfiltersUpstream HTTP 403
All calls —
searchTickets(4 attempts with varying query forms),getTicket(65127), andgetTracInfo(milestones)— returnedHTTP 403: Forbiddenfromcore.trac.wordpress.org. Zero data was retrieved.Ticket 65127
All fields (properties, description, comments, changesets, references, GitHub links) inaccessible due to 403.
Full findings posted as a comment on issue #2397. No repository files modified.