Skip to content

docs: Claude Code v2.1.308 - archived API examples now match API 2026-10-21 (Bearer auth, new SDK majors) so copied code stops using the old version; Claude Duet launches #1401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
claude-yolo merged 1 commit into from
Oct 22, 2026
+715,218 −580,856
Merged

docs: Claude Code v2.1.308 - archived API examples now match API 2026-10-21 (Bearer auth, new SDK majors) so copied code stops using the old version; Claude Duet launches #1401

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
7,928 changes: 3,977 additions & 3,951 deletions content/.metadata.json
View file
Open in desktop

Large diffs are not rendered by default.

54 changes: 27 additions & 27 deletions content/claude/build/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,54 +6,54 @@

> 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.

To 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:
To 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:

* **[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
* **[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
* **[An MCP App](/docs/connectors/building/mcp-apps/getting-started)**: include one when you want the connector to show interactive UI in the conversation
* **Commands and agents**: include named actions, or specialists Claude can delegate to, which [Plugin structure and testing](/docs/plugins/build) covers
* **[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
* **[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
* **[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
* **Commands and agents**: include named actions, or specialists Claude can delegate to, which [Plugin structure and testing](/docs/plugins/build.md) covers

When 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.
When 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.

## Choose a starting page

> **[Build a plugin](/docs/plugins/build)**
> **[Build a plugin](/docs/plugins/build.md)**
>
> Lay out the plugin folder and manifest, write the skills, reference your MCP server, and test the plugin in Claude.

> **[Write skills](/docs/skills/how-to)**
> **[Write skills](/docs/skills/how-to.md)**
>
> Teach Claude your workflows: the SKILL.md frontmatter, the instructions, reference files, and scripts.

> **[Build an MCP server](/docs/connectors/building/index)**
> **[Build an MCP server](/docs/connectors/building/index.md)**
>
> Give the plugin access to your product or data: implement the server, set up authentication for Claude's clients, and test it.

> **[Add interactive UI](/docs/connectors/building/mcp-apps/getting-started)**
> **[Add interactive UI](/docs/connectors/building/mcp-apps/getting-started.md)**
>
> Have your MCP server show interactive components in the conversation with MCP Apps. Optional.

> **[Submit your plugin or MCP server](/docs/directory/publish)**
> **[Submit your plugin or MCP server](/docs/directory/publish.md)**
>
> 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.

> [!NOTE]
>
> * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview) tab
> * 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)
> * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout)
> * If you want to connect a tool or install a plugin for yourself, see the [Customize Claude](/docs/extend/overview.md) tab
> * 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)
> * If you're distributing only inside your organization, see [Roll out a plugin to your whole organization](/docs/plugins/org-rollout.md)
> * 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

## Steps to build and publish a plugin

Building and publishing a plugin follows these steps in order:

1. **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.
2. **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
3. **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).
4. **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.
5. **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
6. **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).
1. **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.
2. **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
3. **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).
4. **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.
5. **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
6. **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).
7. **Measure**: after people have it, [see whether they use it](#measure-usage-of-what-you-built).

### Tools that help you build and check a plugin
Expand All @@ -71,14 +71,14 @@ Most of the tooling for building and checking a plugin lives in [Claude Code](ht

Usage 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:

* **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
* **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
* **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
* **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
* **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
* **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**
* **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**

## Next steps

* [Build your first plugin](/docs/plugins/quickstart): build a small example plugin, test it, and push it to GitHub, ready to submit your own
* [Plugin structure and testing](/docs/plugins/build): the folder layout, manifest, skills, MCP server reference, and testing
* [Build an MCP server for Claude](/docs/connectors/building/index): implement the server, authentication, and testing against Claude
* [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
* [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
* [Plugin structure and testing](/docs/plugins/build.md): the folder layout, manifest, skills, MCP server reference, and testing
* [Build an MCP server for Claude](/docs/connectors/building/index.md): implement the server, authentication, and testing against Claude
* [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
Loading
Loading