Skip to main content
Glama
prasadpatil25

mindspark-mcp

Related Servers

Alternatives to mindspark-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets Claude Code manage GitHub issues, branches, and pull requests through natural language, automating the full development workflow from planning to closing.
      108
      2
      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
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that gives Claude access to your GitHub account — read files, browse repos, commit changes, and manage issues and pull requests, all from a conversation.
      256
      ISC
    • F
      license
      Not graded
      quality
      C
      maintenance
      A custom MCP server that lets AI assistants interact with GitHub accounts, offering tools for repository creation, file viewing, code search, and issue management.
      -

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action pair: maps vs nodes, listing vs rendering vs creating vs deleting. get_map and render_map could overlap, but the descriptions explicitly separate outline reading from visual rendering.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: list_maps, get_map, render_map, create_map, add_node, update_node, delete_node, delete_map. The verbs are clear and the object is always the affected resource.

    Tool Count5/5

    Eight tools is well-scoped for a mind map management server. Each tool covers a necessary core operation without redundancy or bloat.

    Completeness4/5

    The surface covers the main lifecycle: list, read, render, create, update nodes, add nodes, delete nodes, and delete maps. Minor gaps exist around reorganizing nodes (move/reorder) and updating map-level metadata, but agents can accomplish core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues