wordpress/trac-mcp

开发工具

本页由 AI 翻译，技术细节请以原文为准。查看原文

17 stars 6 forks 质量 77 趋势 41GPL-2.0

Repository Install

WordPress 跟踪器的 MCP

概览

WordPress.org 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 - 健康检查:[T2] - 标准MCP:[[T3] -- -- 搜索/匹配:[T4] -- -- 健康检查:[T5] 先前部署在[T6]]的部署已贬值,并使用旧代码。它的a8cai.workers.dev subdomain与主动中转部署的a8c-aiops.dev subdomain不同.

概述（AI 翻译）

WordPress.org 的只读模式背景协议服务器 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

前部署在[T6] 贬值并运行更旧的代码. 它的 [[T7] 子域与活动中程不同部署的 [[T8] 子域。

□ 特拉克实例

每个Trac实例都有自己的终点。 [[T9]和/mcp/chatgpt服务于核心。

QQ Trac 标准 MCP 搜索/匹配 QQ

本页由 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

新手？先看 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"
      ]
    }
  }
}