Просмотр исходного кода

context7: tag the remote MCP URL with client=claude-code-plugin (+ validate path fix) (#5823)

* context7: tag the remote MCP URL with client=claude-code-plugin

* validate: also trigger on vendored plugins' .mcp.json and hooks changes
jordanecker-ant 4 часов назад
Родитель
Сommit
bc875e80be
2 измененных файлов с 9 добавлено и 1 удалено
  1. 8 0
      .github/workflows/validate-plugins.yml
  2. 1 1
      external_plugins/context7/.mcp.json

+ 8 - 0
.github/workflows/validate-plugins.yml

@@ -48,6 +48,14 @@ on:
       - 'plugins/*/assets/**'
       - 'external_plugins/*/README.md'
       - 'external_plugins/*/assets/**'
+      # And for a vendored plugin's MCP server config / hooks: a PR that only edits
+      # plugins/<name>/.mcp.json (e.g. repointing a partner's remote MCP URL, as
+      # #4985 and its follow-up did for context7) or a hooks file matches nothing
+      # above, so `validate` never reports and the PR sits "Expected" forever.
+      - 'plugins/*/.mcp.json'
+      - 'plugins/*/hooks/**'
+      - 'external_plugins/*/.mcp.json'
+      - 'external_plugins/*/hooks/**'
   push:
     branches: [main]
     paths:

+ 1 - 1
external_plugins/context7/.mcp.json

@@ -2,7 +2,7 @@
   "mcpServers": {
     "context7": {
       "type": "http",
-      "url": "https://mcp.context7.com/mcp",
+      "url": "https://mcp.context7.com/mcp?client=claude-code-plugin",
       "headers": {
         "Authorization": "${CONTEXT7_API_KEY:-}"
       }