codescene-mcp-server

Use when installing the CodeScene MCP Server binary or package, registering it in an AI assistant, or copying agent guidance files into a repository.

Write an end-to-end integration test for the CodeScene MCP Server, covering file structure, backend abstraction, MCPClient usage, test registration, and verification.

Run the end-to-end integration test suite for the CodeScene MCP Server. Use when you need to verify that all MCP tools work correctly against the real CLI and server infrastructure.

Update the embedded CodeScene CLI to a new version, including downloading new binaries, computing SHA-256 checksums, and updating all pinned hashes in cli-checksums.sha256 and Dockerfile.

Use when the user wants to view, set, or troubleshoot CodeScene MCP configuration such as access tokens, on-prem URLs, default projects, or SSL certificates.

Scaffold a new MCP tool for the CodeScene MCP Server following the project's established patterns for directory structure, dependency injection, decorators, testing, and registration.

Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.

Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.

Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file.

Use when users with a CodeScene instance ask what to improve first across a project, which hotspots matter most, or how to rank refactoring candidates.

Use when a user asks what to test first based on CodeScene findings, especially for high-risk hotspots or pull-request change sets.

Use when choosing reviewers, domain experts, or likely owners for a file or directory from CodeScene project data.

Use when AI-generated or AI-modified changes need a Code Health gate before commit, handoff, or pull request.