Skip to content

feat(plugin): support agent plugin spec - #205

Merged
wangauone merged 3 commits into
mainfrom
feat/agent-plugins-spec
Aug 5, 2026
Merged

feat(plugin): support agent plugin spec#205
wangauone merged 3 commits into
mainfrom
feat/agent-plugins-spec

Conversation

@wangauone

Copy link
Copy Markdown
Collaborator

Make the plugin/ directory a valid Agent Plugins (v1) plugin:

  • add plugin/plugin.json (spec manifest)
  • add plugin/mcp.json declaring the db-context-engineering and toolbox MCP servers in spec format
  • track plugin/plugin.json version via release-please
  • document installation via compatible Agent Plugins clients

Skills already live under plugin/skills/ and conform to the Agent Skills spec, so no skill changes are needed.

@wangauone
wangauone requested review from g-lynnzee and helloeve August 4, 2026 22:42

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces support for installing the repository as an Agent Plugin by adding plugin metadata (plugin/plugin.json), an MCP server configuration (plugin/mcp.json), and updating the README and release-please configuration. The review feedback highlights that the version of google-cloud-db-context-engineering is hardcoded to @0.7.0 in plugin/mcp.json, which will cause it to become stale when the package version is bumped. To resolve this, the reviewer suggests adding regex updaters to release-please-config.json to automatically bump these hardcoded versions during releases.

Comment thread plugin/mcp.json
Comment thread release-please-config.json
@wangauone
wangauone force-pushed the feat/agent-plugins-spec branch from d68c403 to 20cfe52 Compare August 5, 2026 00:16
Make the plugin/ directory a valid Agent Plugins (v1) plugin:
- add plugin/plugin.json (spec manifest)
- add plugin/mcp.json declaring the db-context-engineering and toolbox
  MCP servers in spec format
- track plugin/plugin.json version via release-please
- extend sync-mcp-version.yml so the release-please bump also rewrites the
  google-cloud-db-context-engineering pin in plugin/mcp.json (sourced from
  plugin/plugin.json, which has no $.version of its own)
- extend presubmit.yml to validate plugin/mcp.json's db-context and toolbox
  pins, matching the checks already covering the other manifests
- document installation via compatible Agent Plugins clients

Skills already live under plugin/skills/ and conform to the Agent Skills
spec, so no skill changes are needed.
@wangauone
wangauone force-pushed the feat/agent-plugins-spec branch from 20cfe52 to 89cf959 Compare August 5, 2026 00:23
@wangauone

Copy link
Copy Markdown
Collaborator Author

/gcbrun

@wangauone

Copy link
Copy Markdown
Collaborator Author

/gcbrun

@wangauone
wangauone merged commit 27852b1 into main Aug 5, 2026
13 checks passed
@wangauone
wangauone deleted the feat/agent-plugins-spec branch August 5, 2026 02:03
wangauone pushed a commit that referenced this pull request Aug 5, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.7.1](v0.7.0...v0.7.1)
(2026-08-05)


### Features

* **evaluate:** Use REST transport to enable working for unreleased
proto fields
([#192](#192))
([c243711](c243711))
* **plugin:** support agent plugin spec
([#205](#205))
([27852b1](27852b1))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants