A Claude Code integration package that declares a GitHub MCP connection; review the bundle before adding a second GitHub server separately.
The checked package pairs a Claude plugin manifest with an MCP configuration file. Its manifest describes repository, issue and pull-request work through GitHub's server. The package is the client integration layer; the GitHub MCP Server is the underlying tool connection. They fill different roles and should not be counted as two independent permissions you automatically need.
A Claude Code user who wants a documented starting point for GitHub access and can inspect the client configuration, account and repository scopes before enabling it.
Repository visibility does not authorize writes. Issue creation, comments, pull-request edits and workflow operations can affect other people. Account access and organization policies may limit which tools are available, and service terms are separate from the repository's software license.
Inspect the pinned manifest and MCP configuration, then use a test repository with the smallest useful scope. Begin by reading a known issue or file and compare the returned result with GitHub. Add write capabilities only for a clearly authorized task.
Check the actual identity, reachable repositories, transport and permission boundary in your client. If the bundle already supplies the connection, avoid installing a duplicate MCP configuration. No authentication flow or remote tool was exercised in this catalog assessment.
claude-code
Publisher manifest for claude-code; runtime behavior not tested
Review the publisher setup, permissions, credentials and service costs before use.
Open the pinned package below and follow its publisher instructions for your agent. A Skills installer is not a universal plugin installer. Review hooks, bundled MCP connections, permissions and configuration before enabling the package.
external_plugins/github/.claude-plugin/plugin.jsonPresence is a static file/manifest observation. A missing declaration does not prove the component is absent at runtime.
Unknown; source software and connected services may have separate terms.
Unknown — no runtime security assessment.
Only sanitized manifest/registry metadata and bounded documentation are inspected. Package code, transitive dependencies, hooks and remote services have not been audited. Review access before use.
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
A structured investigation workflow for a failing build, unexpected application behavior or a regression that keeps returning.
Repository star change: +587 over 24.12 hours. 2026-11-02
A Python UI reference for Gradio interfaces, component layouts, event handlers and interactive model demonstrations.
Repository star change: +9 over 24.12 hours. 2026-11-02
A project scaffold and bundling workflow for complex React-based HTML artifacts.
Repository star change: +478 over 24.12 hours. 2026-11-02
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
A multi-format plugin bundle that organizes planning, testing and implementation through reusable development skills and startup guidance.
A Claude Code review workflow for pull-request changes, with source references and separate local feedback and optional publication steps.
A Claude Code package for connecting Context7's hosted documentation lookup, useful when library versions matter to a coding task.
Category-based discovery suggestions. Review functional overlap; these combinations have not been integration-tested.
Explore freellmpool as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore agents-party as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.
Explore Victauri as an MCP connection for development. Compare the declared transport, package requirements and source evidence before connecting an agent.
Choose a complementary capability only after checking for duplicated permissions and bundled connections. Agent Stacks explain the roles and validation steps; they are proposals, not tested integrations.
Build a stack for your task · Related AI guides · Report a correction