WordPress.org 用のモデルコンテキストプロトコルサーバー Tracインスタンス、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]
• 検索/取得互換性: [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 サブドメインは、アクティブステージとは異なる デプロイメントの a8c-aiops.workers.dev サブドメイン。

Tracインスタンス

各 Trac インスタンスには、独自のエンドポイントがあります。 [/mcp] と [/mcp/chatgpt は、コアに役立ちます。

| Trac | スタンダードMCP | 検索・修正 |

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.

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.