coderocket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEROCKET_API_KEY | Yes | Your crk_ API key | |
| CODEROCKET_API_URL | No | Override the API endpoint | https://deploy.coderocket.com/api/v1 |
| CODEROCKET_ALLOW_CUSTOM_API_URL | No | Set to 1 to permit a non-default host |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reposA | List connected repositories with their analysis status, language, and framework. |
| deploy_repoA | Analyze a repository and generate a CI/CD workflow. Handles the full async flow internally (analyze → poll → generate → poll) and returns the complete YAML + explanation. |
| create_prA | Create a GitHub pull request with the generated CI/CD workflow. |
| generation_feedbackA | Submit feedback on a generated workflow (worked, partial, or failed). |
| list_reviewsB | List AI code reviews, optionally filtered by repository. |
| get_reviewA | Get detailed code review with all inline comments organized by severity. |
| account_statusA | Get account information including subscription tier, usage, and limits. |
| repo_detailsA | Get comprehensive repository details: analysis results, readiness score, optimizations, and generation history. |
| health_checkA | Check connectivity to the CodeRocket API. Useful for debugging setup issues. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: repo listing vs. repo details, deployment generation, PR creation, review listing vs. details, account status, health check, and feedback submission. There is no overlap, and the boundaries between list_repos and repo_details are clear (summary vs. comprehensive).
The tool names mix verb-first patterns (list_repos, create_pr, deploy_repo, list_reviews, get_review) with noun-first patterns (account_status, health_check, generation_feedback, repo_details). This inconsistency, while not causing confusion, prevents a predictable naming convention.
With 9 tools, the server is well-scoped for its purpose—CI/CD workflow generation, PR creation, code reviews, and account management. Each tool serves a clear function, and the count is within the ideal range.
The core lifecycle is covered: analyze repo, generate workflow, create PR, submit feedback, and access reviews. Minor gaps exist, such as no direct listing/updating of individual workflows and no way to comment on or resolve review comments, but these are non-critical and the surface is largely complete.