Build for Claude changedbuild/overview
Nearest release: v2.1.283, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 18:00 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+27added
Lines−27removed
From line
2
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 2, old and new numbered
/
from line 2
22
33> Build a plugin people use inside Claude: an MCP connector to your product, skills for your workflows, optional MCP Apps UI, and a listing in the directory.
44
5To bring your product or workflow into Claude, you build a [plugin](/docs/plugins/build): a package people add once and then use on claude.ai, in the desktop and mobile apps, in Cowork, and in Claude Code. A plugin packages whatever your integration needs, in any combination, and a plugin with only one of these pieces is complete:
5To bring your product or workflow into Claude, you build a [plugin](/docs/plugins/build.md): a package people add once and then use on claude.ai, in the desktop and mobile apps, in Cowork, and in Claude Code. A plugin packages whatever your integration needs, in any combination, and a plugin with only one of these pieces is complete:
66
7* **[An MCP connector](/docs/connectors/building/index)**: include one when Claude needs to reach your product or data. It points at an MCP server that you build and host
8* **[Skills](/docs/skills/how-to)**: include them to teach Claude your workflows, such as the sequence of steps, the defaults, and what good output looks like
9* **[An MCP App](/docs/connectors/building/mcp-apps/getting-started)**: include one when you want the connector to show interactive UI in the conversation
10* **Commands and agents**: include named actions, or specialists Claude can delegate to, which [Plugin structure and testing](/docs/plugins/build) covers
7* **[An MCP connector](/docs/connectors/building/index.md)**: include one when Claude needs to reach your product or data. It points at an MCP server that you build and host
8* **[Skills](/docs/skills/how-to.md)**: include them to teach Claude your workflows, such as the sequence of steps, the defaults, and what good output looks like
9* **[An MCP App](/docs/connectors/building/mcp-apps/getting-started.md)**: include one when you want the connector to show interactive UI in the conversation
10* **Commands and agents**: include named actions, or specialists Claude can delegate to, which [Plugin structure and testing](/docs/plugins/build.md) covers
1111
12When the plugin is ready, you can [submit it](/docs/directory/publish) to Anthropic's directory at [claude.ai/directory](https://claude.ai/directory), the catalog inside Claude where people find and add plugins and connectors, so that anyone on a paid plan can add it. Anthropic checks each submission before it's listed, and there's no partner program to apply to first.
12When the plugin is ready, you can [submit it](/docs/directory/publish.md) to Anthropic's directory at [claude.ai/directory](https://claude.ai/directory), the catalog inside Claude where people find and add plugins and connectors, so that anyone on a paid plan can add it. Anthropic checks each submission before it's listed, and there's no partner program to apply to first.
1313
1414## Choose a starting page
1515
16> **[Build a plugin](/docs/plugins/build)**
16> **[Build a plugin](/docs/plugins/build.md)**
1717>
1818> Lay out the plugin folder and manifest, write the skills, reference your MCP server, and test the plugin in Claude.
1919
20> **[Write skills](/docs/skills/how-to)**
20> **[Write skills](/docs/skills/how-to.md)**
2121>
2222> Teach Claude your workflows: the SKILL.md frontmatter, the instructions, reference files, and scripts.
2323
24> **[Build an MCP server](/docs/connectors/building/index)**
24> **[Build an MCP server](/docs/connectors/building/index.md)**
2525>
2626> Give the plugin access to your product or data: implement the server, set up authentication for Claude's clients, and test it.
2727
28> **[Add interactive UI](/docs/connectors/building/mcp-apps/getting-started)**
28> **[Add interactive UI](/docs/connectors/building/mcp-apps/getting-started.md)**
2929>
3030> Have your MCP server show interactive components in the conversation with MCP Apps. Optional.
3131
32> **[Submit your plugin or MCP server](/docs/directory/publish)**
32> **[Submit your plugin or MCP server](/docs/directory/publish.md)**
3333>
3434> List it in Anthropic's directory so anyone can add it: who can submit, what review involves, and the developer portal steps. Submit your MCP server as a connector too, even when your plugin references it.
3535
3636> [!NOTE]
3737>
38> * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview) tab
39> * If you're not sure whether your plugin needs an MCP server at all, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build)
40> * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
38> * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview.md) tab
39> * If you're not sure whether your plugin needs an MCP server at all, see [Decide what to include in your plugin](/docs/connectors/building/what-to-build.md)
40> * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
4141> * If you're building only for Claude Code's terminal and IDE users, see the [Claude Code plugin docs](https://code.claude.com/docs/en/plugins/create), which cover what that surface alone supports
4242
4343## Steps to build and publish a plugin
from line 44
4444
4545Building and publishing a plugin follows these steps in order:
4646
471. **Lay out the plugin**: create the folder and manifest and reference any MCP server it uses. Start with [Build your first plugin](/docs/plugins/quickstart) if you haven't made one before, or [Plugin structure and testing](/docs/plugins/build) for the full layout. Chat, Cowork, and Claude Code each load different parts of a plugin, so check [Plugin feature support across platforms](/docs/plugins/platform-support) before you commit to a design.
482. **Write the skills**: teach Claude your workflows in `SKILL.md` files inside the plugin. [Create a skill](/docs/skills/how-to) covers the frontmatter, the instructions, reference files, and scripts
493. **Build the MCP server**: if the plugin needs to reach your product or data, implement the server, get authentication right for Claude's clients, and test it against Claude. Start with [Build an MCP server for Claude](/docs/connectors/building/index), or with [Build your first MCP server for Claude](/docs/connectors/building/quickstart) if you haven't written one before. A local server can also be packaged as a [desktop extension](/docs/connectors/building/mcpb).
504. **Add interactive UI**: if you want your server to show interactive components in the conversation, build them with [MCP Apps](/docs/connectors/building/mcp-apps/getting-started). This step is optional.
515. **Test it**: try the plugin in Claude before you publish it. [Test the plugin on each surface](/docs/plugins/build#test-the-plugin-on-each-surface) covers claude.ai, Cowork, and Claude Code, and [Test your MCP server](/docs/connectors/building/testing) covers adding your server as a custom connector
526. **Publish**: submit the plugin to the directory, submit its MCP server as a connector, and maintain the listing. Start with [Publish to the directory](/docs/directory/publish).
471. **Lay out the plugin**: create the folder and manifest and reference any MCP server it uses. Start with [Build your first plugin](/docs/plugins/quickstart.md) if you haven't made one before, or [Plugin structure and testing](/docs/plugins/build.md) for the full layout. Chat, Cowork, and Claude Code each load different parts of a plugin, so check [Plugin feature support across platforms](/docs/plugins/platform-support.md) before you commit to a design.
482. **Write the skills**: teach Claude your workflows in `SKILL.md` files inside the plugin. [Create a skill](/docs/skills/how-to.md) covers the frontmatter, the instructions, reference files, and scripts
493. **Build the MCP server**: if the plugin needs to reach your product or data, implement the server, get authentication right for Claude's clients, and test it against Claude. Start with [Build an MCP server for Claude](/docs/connectors/building/index.md), or with [Build your first MCP server for Claude](/docs/connectors/building/quickstart.md) if you haven't written one before. A local server can also be packaged as a [desktop extension](/docs/connectors/building/mcpb.md).
504. **Add interactive UI**: if you want your server to show interactive components in the conversation, build them with [MCP Apps](/docs/connectors/building/mcp-apps/getting-started.md). This step is optional.
515. **Test it**: try the plugin in Claude before you publish it. [Test the plugin on each surface](/docs/plugins/build.md#test-the-plugin-on-each-surface) covers claude.ai, Cowork, and Claude Code, and [Test your MCP server](/docs/connectors/building/testing.md) covers adding your server as a custom connector
526. **Publish**: submit the plugin to the directory, submit its MCP server as a connector, and maintain the listing. Start with [Publish to the directory](/docs/directory/publish.md).
53537. **Measure**: after people have it, [see whether they use it](#measure-usage-of-what-you-built).
5454
5555### Tools that help you build and check a plugin
from line 67
6767
6868Usage figures for a directory listing are in the developer portal, and figures for a plugin you distribute yourself or inside your organization are in Claude Code or in **Customize**. Each of these pages covers one case:
6969
70* **A plugin listed in the directory**: [How a published plugin is used](/docs/connectors/building/after-publishing#track-published-plugin-usage) covers installs, versions, how often each skill and MCP server runs, and error rates
71* **A connector listed in the directory**: [Manage your directory listing](/docs/connectors/building/managing-your-listing#server-health-and-usage-metrics) covers the dashboard's server health, usage by product and by tool, and error breakdown
70* **A plugin listed in the directory**: [How a published plugin is used](/docs/connectors/building/after-publishing.md#track-published-plugin-usage) covers installs, versions, how often each skill and MCP server runs, and error rates
71* **A connector listed in the directory**: [Manage your directory listing](/docs/connectors/building/managing-your-listing.md#server-health-and-usage-metrics) covers the dashboard's server health, usage by product and by tool, and error breakdown
7272* **A plugin you rolled out to your organization's Claude Code users**: [Measure and evaluate plugins](https://code.claude.com/docs/en/plugins/measure) covers what a plugin costs in context, whether it's used, and the OpenTelemetry events that answer organization-wide questions
73* **A plugin or skill used inside your organization on claude.ai**: [How a plugin is used in your organization](/docs/plugins/overview#track-plugin-usage-in-your-organization) covers the adoption and activity figures on its page in **Customize**
73* **A plugin or skill used inside your organization on claude.ai**: [How a plugin is used in your organization](/docs/plugins/overview.md#track-plugin-usage-in-your-organization) covers the adoption and activity figures on its page in **Customize**
7474
7575## Next steps
7676
77* [Build your first plugin](/docs/plugins/quickstart): build a small example plugin, test it, and push it to GitHub, ready to submit your own
78* [Plugin structure and testing](/docs/plugins/build): the folder layout, manifest, skills, MCP server reference, and testing
79* [Build an MCP server for Claude](/docs/connectors/building/index): implement the server, authentication, and testing against Claude
80* [Decide what to include in your plugin](/docs/connectors/building/what-to-build): decide whether your plugin needs an MCP server, commands, agents, or UI
77* [Build your first plugin](/docs/plugins/quickstart.md): build a small example plugin, test it, and push it to GitHub, ready to submit your own
78* [Plugin structure and testing](/docs/plugins/build.md): the folder layout, manifest, skills, MCP server reference, and testing
79* [Build an MCP server for Claude](/docs/connectors/building/index.md): implement the server, authentication, and testing against Claude
80* [Decide what to include in your plugin](/docs/connectors/building/what-to-build.md): decide whether your plugin needs an MCP server, commands, agents, or UI
8181
No line in this hunk matches that.