Skip to main content
Glama
bindreams

space-mcp

by bindreams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to space-mcp

No user-submitted related servers found.

    Related Servers

    • gitlab-mcp

      vinihcrosa
      A
      license
      A
      quality
      A
      maintenance
      MCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.
      13
      8 npm
      MIT

    • fj-mcp

      jairov4
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.
      -

    • gitlab-mcp

      EllGree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.
      414 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: read/list/create/edit/close/reopen/delete MRs, timeline, comments vs inline discussions, and Patronus run queries/actions. Singular/plural and general/inline comment distinctions are clear.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using HTTP verbs (get, put, patch, post) with clear resource nouns. Even action-oriented names like post_close_merge_request and post_reply_to_code_discussion maintain a predictable structure.

    Tool Count4/5

    At 16 tools, the set is slightly above the typical well-scoped range (3-15) but is justified by covering both merge request lifecycle and Patronus dry run/safe merge operations. Each tool has a clear purpose, so the count feels appropriate for the domain.

    Completeness4/5

    The tool surface covers full MR lifecycle (create, read, list, edit, close, reopen, delete), commenting (general and inline), replies, attachments, and Patronus run inspection/start/cancel. A minor gap is the lack of a tool to initiate a 'safe merge', though this might be intentionally excluded.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources