Skip to main content
Glama
MikeyBeez

mcp-registry-interface

by MikeyBeez

Related Servers

Alternatives to mcp-registry-interface

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that connects Claude AI directly to the GitHub API, enabling natural language queries for live repository data, issues, PRs, and contributions.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      MCP (Model Context Protocol) server for GitHub API integration. This server provides comprehensive tools for interacting with GitHub repositories, issues, pull requests, branches, and code search through a unified interface.
      15
      2 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that enables Claude to directly interact with GitHub, including repos, files, branches, issues, pull requests, Actions, and code search using a personal access token.
      26
      85 npm
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that allows Claude and other MCP-compatible LLMs to interact with the GitHub API, supporting features like creating issues, getting repository information, listing issues, and searching repositories.
      4
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that provides comprehensive GitHub integration for Claude Desktop, allowing users to manage repositories, issues, and pull requests. It supports file operations, branch management, and repository searches through natural language commands.
      245 npm
      -
    • F
      license
      B
      quality
      D
      maintenance
      An MCP server that enables Claude and other compatible LLMs to interact with the GitHub API, supporting features like creating issues, retrieving repository information, listing issues, and searching repositories.
      4
      -

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: searching, retrieving details, listing categories, refreshing data, and getting help. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., registry_search_servers, registry_get_server_details). 'help' is a minor deviation but is a conventional verb-like exception in many toolkits.

    Tool Count5/5

    With exactly 5 tools, the set is well-scoped for a registry interface. Each tool covers a needed function without redundancy or bloat.

    Completeness4/5

    The core read and maintenance operations (search, get details, list categories, refresh) are all present. A list-all servers function could be considered missing, but search likely covers that use case adequately.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues