Skill v1.0.3
currentAutomated scan100/100~1 modified
version: "1.0.3" name: installing-and-activating-codescene-mcp description: Use when installing the CodeScene MCP Server binary or package, registering it in an AI assistant, or copying agent guidance files into a repository.
Installing and Activating CodeScene MCP
Overview
Use this skill when the task is to get the CodeScene MCP Server installed and registered with an AI assistant. The workflow has three parts: install the server, register it in the assistant, and copy the agent guidance files into the repository.
For configuring the server after installation (OAuth login, account ID, PAT, on-prem URLs, default project, SSL), use the configuring-codescene-mcp skill instead.
When to Use
- The user wants to install CodeScene MCP for the first time.
- The user has the binary or package installed but has not registered it in an AI assistant.
- The user wants a quick setup path for VS Code, GitHub Copilot, Claude Code, Docker, Homebrew, or Windows.
Do not use this skill for configuring tokens, URLs, or other server options. Use configuring-codescene-mcp for that. Do not use this skill for refactoring, safeguards, or technical debt prioritization.
Quick Reference
- Install using the method that matches the environment:
npxornpm, Homebrew, Windows installer script, manual download, or Docker. - Register the server in the AI assistant so it launches
cs-mcp. - Copy the appropriate agent guidance file into the repository:
docs/AGENTS-full.mdfor CodeScene Core users, ordocs/AGENTS-standalone.mdfor standalone license users. For Amazon Q, copy.amazonq/rulesinstead. - Copy any relevant skills from the CodeScene MCP skills catalogue at
https://github.com/codescene-oss/codescene-mcp-server/tree/main/skills. - After installation, authenticate with OAuth via the
loginMCP prompt (slash command), by asking the assistant to log in (logintool), or with CodeScene: Sign In in the VS Code extension. Use a PAT only for CI/headless environments.
Implementation
- Choose the installation method that fits the user environment:
npx @codescene/codehealth-mcpornpm install -g @codescene/codehealth-mcpbrew tap codescene-oss/codescene-mcp-server https://github.com/codescene-oss/codescene-mcp-server && brew trust codescene-oss/codescene-mcp-server && brew install cs-mcp- Windows PowerShell installer
- Manual binary download
- Docker image
- Verify that the
cs-mcpcommand or container entrypoint is available. - Register the server in the AI assistant:
- For VS Code or GitHub Copilot, install the CodeScene CodeHealth MCP extension, or add a
codesceneserver entry insettings.json/.vscode/mcp.json. - For Claude Code, install the plugin (
/plugin install codescene@codescene) or add the MCP withclaude mcp add.
- Authenticate:
- Interactive (recommended): Use the
loginMCP prompt (slash command), ask the assistant to log in (callsloginand opens a browser), or run CodeScene: Sign In in the VS Code extension. For multi-account Cloud users, setaccount_idfirst. For on-prem, setonprem_urlfirst. - CI / headless: Set a Personal Access Token via
set_configorCS_ACCESS_TOKEN. See theconfiguring-codescene-mcpskill.
- Copy the appropriate agent guidance file to the repository:
docs/AGENTS-full.mdfor CodeScene Core users, ordocs/AGENTS-standalone.mdfor standalone license users. Rename it toAGENTS.mdin the target repository so the agent picks it up automatically. - If the user is on Amazon Q, copy
.amazonq/rulesinstead of the AGENTS file. - Copy any relevant skills from
https://github.com/codescene-oss/codescene-mcp-server/tree/main/skillsfor safeguarding, refactoring, prioritization, or business-case workflows.
Common Mistakes
- Installing the server but never registering it with the assistant.
- Copying the setup files into the wrong repository.
- Skipping authentication after installation. For interactive use, call
login; for CI, set a PAT. - Pasting a PAT into client env when OAuth would work — a set
CS_ACCESS_TOKENblockslogin. - Manually editing environment variables when
login/set_configis simpler and persistent.