wordpress/trac-mcp

Developer tools

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기

17 stars 6 forks 품질 77 트렌드 41GPL-2.0

Repository Install

워드 프레스 Trac에 대한 MCP

개요

WordPress.org Trac 인스턴스에 대한 read-only Model Context Protocol 서버, WordPress Core Trac 시작하기. 그것은 Cloudflare 노동자로 실행하고 Trac의 공개 HTML, CSV, RSS 및 diff 엔드 포인트를 사용합니다. - 표준 MCP: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp - 검색/그림 호환성: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp/chatgpt - 건강 검사: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/health - 표준 MCP : https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp - Search/fetch 호환성 : https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp/chatgpt] - 건강 검사 : https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/health] https://mcp-server-wporg-trac-staging.a8cai.workers.dev]에서 이전의 노후화 배포가 진행되고 이전 코드를 실행합니다. 그것의 a8cai.workers.dev subdomain는 활성 staging 배포의 a8c-aiops.workers.dev subdomain과 다릅니다.

개요(AI 번역)

WordPress.org에 대한 read-only Model Context Protocol 서버 Trac 인스턴스, WordPress Core Trac 시작. 그것은 Cloudflare Worker는 Trac의 공개 HTML, CSV, RSS 및 diff 엔드 포인트를 사용합니다.

라이브 서버:

생산:

표준 MCP: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp
검색/그림 호환성: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp/chatgpt
건강 검사: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/health

안정성:

표준 MCP: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp
검색/그림 호환성: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp/chatgpt
건강 검사: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/health

https://mcp-server-wporg-trac-staging.a8cai.workers.dev에서 이전의 노후화 deprecated 및 이전 코드를 실행합니다. 그것의 a8cai.workers.dev subdomain은 활성 시술과 다릅니다. 배포 a8c-aiops.workers.dev subdomain.

Trac 인스턴스

각 Trac 인스턴스에는 자체 엔드포인트가 있습니다. /mcp와 /mcp/chatgpt]는 코어를 제공합니다.

| Trac | 표준 MCP | 검색/피트 호환성 |

이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요.

README

원문 README의 일부입니다. 원문 보기.

WordPress Trac MCP server

A read-only Model Context Protocol server for the WordPress.org Trac instances, starting with WordPress Core Trac. It runs as a Cloudflare Worker and uses Trac’s public HTML, CSV, RSS, and diff endpoints.

Live servers:

Production:

Standard MCP: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp
Search/fetch compatibility: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp/chatgpt
Health check: https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/health

Staging:

Standard MCP: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp
Search/fetch compatibility: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/mcp/chatgpt
Health check: https://mcp-server-wporg-trac-staging.a8c-aiops.workers.dev/health

The former staging deployment at https://mcp-server-wporg-trac-staging.a8cai.workers.dev is deprecated and runs older code. Its a8cai.workers.dev subdomain differs from the active staging deployment’s a8c-aiops.workers.dev subdomain.

Trac instances

Each Trac instance has its own endpoint. /mcp and /mcp/chatgpt serve Core.

Trac	Standard MCP	Search/fetch compatibility
WordPress Core	`/mcp`	`/mcp/chatgpt`
Making WordPress.org	`/mcp/meta`	`/mcp/meta/chatgpt`
Themes	`/mcp/themes`	`/mcp/themes/chatgpt`
Plugins	`/mcp/plugins`	`/mcp/plugins/chatgpt`
bbPress	`/mcp/bbpress`	`/mcp/bbpress/chatgpt`
BuddyPress	`/mcp/buddypress`	`/mcp/buddypress/chatgpt`
GlotPress	`/mcp/glotpress`	`/mcp/glotpress/chatgpt`
Google Summer of Code	`/mcp/gsoc`	`/mcp/gsoc/chatgpt`

The table is a discovery aid rather than an allowlist. Any .trac.wordpress.org resolves at /mcp/, so a Trac added later needs no change here. An instance is bound to the connection rather than chosen per tool call, so a client cannot read the wrong Trac by mistake.

Instances configure different fields. Themes has no components, and only some instances have severities. getTracInfo reports a field the instance does not configure as unavailable instead of failing. Ticket fields behave the same way: focuses exists only on Core and comes back empty elsewhere.

Filtering is stricter, because Trac answers a filter on a field it does not configure with the unfiltered result set rather than an error, and that reads as a real match count. searchTickets rejects such a filter and names the fields the instance does have. This covers both the separate arguments and the expressions inside query.

GitHub에서 전체 README 보기

설치

npx mcp-remote https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp

MCP 초보자라면? mcpskill.org 가이드부터 시작하세요 →

설정

{
  "mcpServers": {
    "wordpress-trac": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp"
      ]
    },
    "wordpress-meta-trac": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://wordpress-trac-mcp-server-prod.a8c-aiops.workers.dev/mcp/meta"
      ]
    }
  }
}