---
title: "Did Google join the Agent Plugins standard?"
description: "**Yes. On 6 August 2026 Google said it is joining the Agent Plugins Technical Steering Committee as a Core Maintainer.** Kevin Hou represents Google on that group. The same post says Google is starting to build support i"
canonical: https://agentpluginsdirectory.com/blog/google-joins-agent-plugins-core-maintainer
last-updated: 2026-08-22
---

# Did Google join the Agent Plugins standard?

**Yes. On 6 August 2026 Google said it is joining the Agent Plugins Technical Steering Committee as a Core Maintainer.** Kevin Hou represents Google on that group. The same post says Google is starting to build support into its products. That is a seat on the spec, not a listing in this index.

agentpluginsdirectory.com is the verified directory of Agent Plugins, the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema.

## What did Google publish?

Kevin Hou, Haoyu Wang, and Alan Blount wrote on the [Google Developers Blog](https://developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more/) on 6 August 2026:

> Agent Plugins 1.0.0 is an open, vendor-neutral specification for packaging Agent Skills and MCP servers into portable plugins. It was published by a TSC of Core Maintainers from Amazon, Cursor, Microsoft, OpenAI, and Vercel. Google is joining that group as a Core Maintainer, represented by Kevin Hou, and we're starting to build support into our own products.

And:

> A plugin is a directory. That's the whole idea, and the restraint is the point.

Read the post in full at [developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more](https://developers.googleblog.com/agent-plugins-package-your-skills-tools-and-more/).

Source: Google Developers Blog, 6 August 2026, Hou, Wang, Blount.

## Does that mean Google already ships a listed plugin?

No. Joining the TSC is a maintainer announcement. This directory lists a plugin only when we can fetch a plugin.json that passes the official 1.0.0 schema and survives the usual exclusions. Check [publishers](/publishers) and [census.json](/census.json) for who actually publishes today. Do not treat a blog post as a listing.

The live verified count is 1,309 as of 2026-08-22.

Source: agentpluginsdirectory.com verified index, 2026-08-22.

## What should I read next?

- [What are Agent Plugins](/guides/what-are-agent-plugins) for the package idea
- The [specification](/spec) for the normative text
- [Build an Agent Plugin](/build) if you want to publish one
- The [plugin.json validator](/validator) if you have a draft manifest

## FAQ

**Did Google join the Agent Plugins standard?** Yes, as a Core Maintainer on the TSC, represented by Kevin Hou, per the 6 August 2026 Google Developers Blog post.

**Is Google already in the original publisher list on this site?** The brand line still names OpenAI, Amazon, Cursor, Microsoft, and Vercel as the publishers of the open standard. Google is joining that Core Maintainer group.

**Can I install a Google Agent Plugin from this directory?** Only if a verified listing exists. Look at [publishers](/publishers). We do not invent a listing from a product announcement.

**How many plugins are verified right now?** 1,309 as of 2026-08-22. See [census.json](/census.json).