By anthropics
Design, build, and deploy MCP servers for Claude by interrogating your use case to select deployment models like remote HTTP, MCPB, or local stdio, implementing tool patterns with auth, adding interactive UI widgets such as forms, pickers, and dashboards for inline chat rendering, and packaging into standalone Node or Python .mcpb bundles for local distribution without user toolchain.
npx claudepluginhub anthropics/claude-plugins-official --plugin mcp-server-devThis skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation dialog" inline in the conversation, or mentions "apps SDK" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets.
This skill should be used when the user asks to "build an MCP server", "create an MCP", "make an MCP integration", "wrap an API for Claude", "expose tools to Claude", "make an MCP app", or discusses building something with the Model Context Protocol. It is the entry point for MCP server development — it interrogates the user about their use case, determines the right deployment model (remote HTTP, MCPB, local stdio), picks a tool-design pattern, and hands off to specialized skills.
This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP", discusses ".mcpb files", mentions bundling a Node or Python runtime with their MCP server, or needs an MCP server that interacts with the local filesystem, desktop apps, or OS and must be installable without the user having Node/Python set up.
Share bugs, ideas, or general feedback.
A curated directory of high-quality plugins for Claude Code.
⚠️ Important: Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change. See each plugin's homepage for more information.
/plugins - Internal plugins developed and maintained by Anthropic/external_plugins - Third-party plugins from partners and the communityPlugins can be installed directly from this marketplace via Claude Code's plugin system.
To install, run /plugin install {plugin-name}@claude-plugins-official
or browse for the plugin in /plugin > Discover
Internal plugins are developed by Anthropic team members. See /plugins/example-plugin for a reference implementation.
Third-party partners can submit plugins for inclusion in the marketplace. External plugins must meet quality and security standards for approval. To submit a new plugin, use the plugin directory submission form.
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # Documentation
Please see each linked plugin for the relevant LICENSE file.
For more information on developing Claude Code plugins, see the official documentation.
Comprehensive toolkit with 8 expert skills for Claude Code plugin development covering hooks, MCP integration, commands, and agents with best practices.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools.
Complete framework for building MCP applications and servers for Claude, ChatGPT, and AI agents with integrated tooling.
MCP server development helper with tool and resource scaffolding
Plugin development toolkit with skills for creating agents, commands, hooks, MCP integrations, and comprehensive plugin structure guidance
Manage Claude Code settings and MCP server configurations with best practices