Decide what to include in your plugin changedconnectors/building/what-to-build
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+10added
Lines−10removed
From line
11
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 11, old and new numbered
/
from line 11
1111
1212A plugin with only a connector or only skills is complete.
1313
14This page is for developers deciding which of those pieces their plugin needs. Once you've decided, [Plugin structure and testing](/docs/plugins/build), [Build an MCP server for Claude](/docs/connectors/building/index), and [Publish to the directory](/docs/directory/publish) cover the work.
14This page is for developers deciding which of those pieces their plugin needs. Once you've decided, [Plugin structure and testing](/docs/plugins/build.md), [Build an MCP server for Claude](/docs/connectors/building/index.md), and [Publish to the directory](/docs/directory/publish.md) cover the work.
1515
1616> [!NOTE]
1717>
18> * If you're choosing what to add to your own Claude rather than what to build, see [Connectors, skills, and plugins](/docs/extend/overview), which compares the three from the user's side
19> * If you're building for your own organization and not listing publicly, the same decisions apply, and you distribute the result as a [custom connector](/docs/connectors/custom/add-unlisted#add-a-connector-by-url) and an [organization plugin](/docs/plugins/admin) instead of through the directory
18> * If you're choosing what to add to your own Claude rather than what to build, see [Connectors, skills, and plugins](/docs/extend/overview.md), which compares the three from the user's side
19> * If you're building for your own organization and not listing publicly, the same decisions apply, and you distribute the result as a [custom connector](/docs/connectors/custom/add-unlisted.md#add-a-connector-by-url) and an [organization plugin](/docs/plugins/admin.md) instead of through the directory
2020
2121## Reach your product with an MCP connector
2222
23Include an MCP connector when Claude needs to read from or act in your product or data. The connector points at a remote MCP server that you build and host, with [OAuth sign-in](/docs/connectors/building/authentication) if your tools act on the user's own account. [Build an MCP server for Claude](/docs/connectors/building/index) covers the server, and [Build your first MCP server for Claude](/docs/connectors/building/quickstart) is the place to start if you haven't written one.
23Include an MCP connector when Claude needs to read from or act in your product or data. The connector points at a remote MCP server that you build and host, with [OAuth sign-in](/docs/connectors/building/authentication.md) if your tools act on the user's own account. [Build an MCP server for Claude](/docs/connectors/building/index.md) covers the server, and [Build your first MCP server for Claude](/docs/connectors/building/quickstart.md) is the place to start if you haven't written one.
2424
2525Once the server is live, people can use your product in chat on web, desktop, and mobile, in Cowork, and in Claude Code. Tools you add to the server later reach every plugin that references it without a new plugin release.
2626
from line 39
3939Commands, agents, and UI are optional pieces, and each fits a particular need:
4040
4141* **Commands**: named actions people run themselves, such as `/your-plugin:weekly-report`, for tasks they start deliberately rather than describe
42* **Agents**: specialists Claude can delegate part of a task to. Cowork and Claude Code run them; chat doesn't, as [Plugin feature support across platforms](/docs/plugins/platform-support) lists
43* **An MCP App**: interactive UI that your connector shows in the conversation, such as a form or a chart. [Add interactive UI with MCP Apps](/docs/connectors/building/mcp-apps/getting-started) covers building one
42* **Agents**: specialists Claude can delegate part of a task to. Cowork and Claude Code run them; chat doesn't, as [Plugin feature support across platforms](/docs/plugins/platform-support.md) lists
43* **An MCP App**: interactive UI that your connector shows in the conversation, such as a form or a chart. [Add interactive UI with MCP Apps](/docs/connectors/building/mcp-apps/getting-started.md) covers building one
4444
4545## Package and list the plugin
4646
4747Most plugins for a product include both an MCP connector and skills: the connector so Claude can reach the product, and the skills so Claude uses it the way you intend. Everything in the plugin is packaged together, so one listing gives people all of it.
4848
49When you list the plugin, submit the server too: the plugin as a plugin bundle and the server as an MCP connector. Submitting the server as a connector gives your organization the connector's listing and its dashboard, and lets you pair the two listings. [Submit your plugin, and your MCP server as a connector](/docs/directory/publish#submit-your-plugin-and-your-mcp-server-as-a-connector) explains the pairing.
49When you list the plugin, submit the server too: the plugin as a plugin bundle and the server as an MCP connector. Submitting the server as a connector gives your organization the connector's listing and its dashboard, and lets you pair the two listings. [Submit your plugin, and your MCP server as a connector](/docs/directory/publish.md#submit-your-plugin-and-your-mcp-server-as-a-connector) explains the pairing.
5050
5151The diagram shows what the server and the plugin each give people. The server gives them your connector. The plugin adds your skills and points to that same server.
5252
from line 58
5858
5959## Next steps
6060
61* [Plugin structure and testing](/docs/plugins/build): write the folder that packages your connector, skills, and the rest, and installs on every surface
62* [Build an MCP server for Claude](/docs/connectors/building/index): implement the server and its authentication, and test it against Claude
63* [Publish to the directory](/docs/directory/publish): submit the plugin, and its MCP server as a connector, from the [developer portal](https://claude.ai/directory/manage). Anyone on a paid Claude plan can submit, and on Team and Enterprise an Owner submits
61* [Plugin structure and testing](/docs/plugins/build.md): write the folder that packages your connector, skills, and the rest, and installs on every surface
62* [Build an MCP server for Claude](/docs/connectors/building/index.md): implement the server and its authentication, and test it against Claude
63* [Publish to the directory](/docs/directory/publish.md): submit the plugin, and its MCP server as a connector, from the [developer portal](https://claude.ai/directory/manage). Anyone on a paid Claude plan can submit, and on Team and Enterprise an Owner submits
6464
No line in this hunk matches that.