Skip to main content
Glama
musictechlab

mcp-codemagic

by musictechlab

Related Servers

Alternatives to mcp-codemagic

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Codemagic CI/CD API, enabling app management, build operations, artifact handling, cache control, and team management through natural language.
      3 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local Python MCP server that exposes the Codemagic CI/CD REST API as Claude-callable tools. Trigger builds, manage apps, download artifacts, and clear caches — all from Claude Code or Claude Desktop without leaving the chat.
      25
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A server that enables interaction with Jenkins CI/CD pipelines from any compatible MCP client (like Claude Desktop), allowing users to manage jobs, builds, coverage reports, and other Jenkins functionality through natural language.
      11
      7 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An opinionated MCP server for App Store Connect that provides 13 curated tools, slash-command workflows, and a Claude Skill to manage apps, reviews, sales, and pre-submission audits via natural language.
      41
      72 npm
      MIT

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a unique, clearly defined purpose: listing apps, getting app details, listing builds, getting build details, starting a build, and canceling a build. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow a consistent 'codemagic_verb_noun' pattern using snake_case (e.g., codemagic_list_apps, codemagic_start_build). This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a CI/CD server. It covers essential operations without being overwhelming or too sparse.

    Completeness4/5

    Core build lifecycle (list, start, get, cancel) is covered. Minor gaps exist, such as no explicit tool for retrying a build or downloading artifacts, but the set is functional for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues