Skip to main content
Glama
agenticbits

@agenticbits/claude-plugin

by agenticbits

Related Servers

Alternatives to @agenticbits/claude-plugin

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to interact with git repositories by providing real-time access to repository status, branch information, commit history, and file changes. Allows users to query their git workspace through natural language commands.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables natural language code search across multiple local Git repositories, allowing users to register projects, search for code, and explore file structures through Claude.
      6
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Git and GitHub pull request operations through Claude AI, including repository management, branch operations, commits, and PR creation/commenting. Streamlines development workflows by providing Git commands and GitHub API integration through natural language interactions.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with GitHub repositories directly from Claude, supporting actions like viewing repos, checking status, committing and pushing changes, and managing pull requests.
      -
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects Claude Desktop directly to GitHub repositories and git commands, enabling users to clone repos, check status, commit changes, push code, create repositories, and manage GitHub resources through natural conversation.
      245 npm
      -

    TDQS

    A3.8/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. For example, add_repo and remove_repo handle opposite operations, while get_branch_status and check_repo_branch provide different scopes of branch information. The descriptions make it easy to distinguish between configuration management tools (get_config_info, toggle_statusbar) and repository-specific operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with clear, descriptive names. The verbs are appropriate and consistent (add, check, get, list, remove, set, toggle, validate), and all use snake_case throughout. There are no deviations or mixed conventions in the naming scheme.

    Tool Count5/5

    With 10 tools, this server is well-scoped for managing git repository status in a status bar. Each tool serves a specific purpose in the workflow, from adding/removing repos to checking status and toggling visibility. The count is neither too sparse nor bloated, fitting the domain perfectly.

    Completeness5/5

    The toolset provides complete coverage for the domain of managing git repositories in a status bar. It includes all necessary CRUD operations (add, list, remove), status checks (branch, validation), configuration management (get config, toggle features), and visibility controls. There are no obvious gaps, and agents can perform full lifecycle management without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues