codemagic-mcp
Related Servers
Alternatives to codemagic-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with the Crewmeister API over local stdio, covering operations for members, teams, time tracking, salary exports, and related platform resources.Apache 2.0
- AlicenseCqualityBmaintenanceEnables MCP clients to interact with the current xMatters REST API over stdio, covering people, devices, groups, on-call schedules, events, incidents, workflows, services, integrations, and subscriptions. It is read-only by default and requires explicit operator opt-in plus per-call confirmation for mutations.179Apache 2.0
- AlicenseCqualityCmaintenanceEnables any MCP client to triage cloud agents, projects, conversations, transcripts, pull requests, and files, including listing agents, reading transcripts, following runs, and sending follow-ups, using an API key or browser sign-in.29MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.1873 npm5MIT
- AlicenseNot gradedqualityAmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.14 npm54MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to connect to a running MAGDA instance over stdio and access its native composition tools, resources, and resource templates, while providing instance discovery, fixed-instance connection, credential recovery, diagnostics, and compatibility checks.MIT
TDQS
Scored across 1 tool
With only a single tool exposed, there is no possibility of confusion or misselection between tools. The lone tool's purpose (reporting setup status) is unambiguous.
The single name 'cm_setup_status' uses a clean snake_case convention with a consistent 'cm_' namespace prefix. No pattern can be fully verified from one tool, but nothing is inconsistent or unreadable.
A Codemagic CI/CD integration would be expected to expose many build, app, and workflow operations, but only a single placeholder/setup tool exists. This is far too few for the apparent scope.
The server exposes no actual Codemagic API functionality; it only reports that no token is configured. The entire operational surface is missing, leaving agents with nothing to work with.