Integration

CodeScene integration

CodeScene analyses Git repositories for code health, hotspots, technical debt, knowledge distribution and delivery. With this API an agent can list and import projects, trigger an analysis, read analysis results (files with code health scores, components, commits, issues, author and branch statistics, delta analyses for pull requests), read the KPI trends behind the 4-factors dashboards, read Code Health safeguard insights for pull requests and the CodeScene MCP server, read code coverage gate results, technical debt and the estimated engineering outcomes of a Code Health change, toggle project badges, and manage developer settings, teams, developers, repositories and architectural components. Replacing the shared password of a project's PM integration is not exposed, nor is the unversioned email route. Authentication is a CodeScene Cloud API token (created in CodeScene under the API tokens page) sent as a Bearer token in the Authorization header.

Connect CodeScene How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in CodeScene.Built from the 77 CodeScene tools below, on the connection you add once.

What you can do with CodeScene

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Mcp safeguard, 7 operations

get_my_mcp_safeguard_insightsGet my mcp safeguard insightsGETReturns aggregated CodeScene MCP server safeguard activity of the token's user: most-used tools, safeguard checks, code health uplifts and degradations prevented.
get_org_mcp_safeguard_insightsGet org mcp safeguard insightsGETReturns organization-wide CodeScene MCP server safeguard insights (organization taken from the token). Requires admin access.
get_project_mcp_safeguard_insightsGet project mcp safeguard insightsGETReturns aggregated CodeScene MCP server safeguard insights for one project, per weekly or monthly period.
list_my_mcp_safeguard_outcomesList my mcp safeguard outcomesGETLists the individual CodeScene MCP server safeguard events of the token's user, a page at a time.
list_org_mcp_safeguard_outcomesList org mcp safeguard outcomesGETLists organization-wide CodeScene MCP server safeguard events, a page at a time, with the user identity when available. Requires admin access.
list_org_mcp_safeguard_usersList org mcp safeguard usersGETLists the organization's users with per-user CodeScene MCP server safeguard activity (checks, uplifts, degradations prevented, most-used tools). Requires admin access.
list_project_mcp_safeguard_outcomesList project mcp safeguard outcomesGETLists the individual CodeScene MCP server safeguard events of one project, a page at a time.

Analysis, 5 operations

get_analysisGet analysisGETReturns one analysis by id: summary counts, high-level metrics (code health now, a month and a year ago, hotspots, worst performer), file summary per language and code coverage.
get_latest_analysisGet latest analysisGETReturns the latest analysis of a project: summary counts, high-level metrics (code health now, a month and a year ago, hotspots, worst performer), file summary per language and code coverage.
list_analysesList analysesGETLists the analyses of a project, a page at a time, each with id, name and an API ref.
list_analyses_by_dateList analyses by dateGETLists the analyses of a project that ran on a given date, a page at a time.
run_project_analysisRun project analysisPOSTStarts a new analysis of the project. CodeScene recommends turning off scheduled analyses if this is used as a continuous trigger.

Component, 4 operations

get_analysis_componentGet analysis componentGETReturns one architectural component of an analysis by name: owner, change frequency, authors, teams, knowledge loss, defects, cost and system mastery.
get_latest_componentGet latest componentGETReturns one architectural component of the latest analysis by name: owner, change frequency, authors, teams, knowledge loss, defects, cost and system mastery.
list_analysis_componentsList analysis componentsGETLists the architectural components of an analysis, a page at a time, each with name and API ref.
list_latest_componentsList latest componentsGETLists the architectural components of the latest analysis, a page at a time, each with name and API ref.

Developer, 4 operations

delete_developerDelete developerDELETEDeletes a developer from a developer settings set.
list_developersList developersGETLists the developers of a developer settings set, a page at a time, with emails, team, former-contributor and excluded flags.
remove_developer_from_teamRemove developer from teamDELETERemoves a developer from its team without deleting the developer.
update_developerUpdate developerPUTUpdates a developer: assign a team, mark as former contributor, or exclude from all analyses. Send only the fields to change; leave the others out to keep them.

File, 4 operations

list_analysis_component_filesList analysis component filesGETLists the files of one component of an analysis in descending order of order_by, with the same file metrics as the files list.
list_analysis_filesList analysis filesGETLists the files of an analysis in descending order of order_by, with code health scores, change frequency, defects, cost, ownership and recommendations. Use fields to limit the answer.
list_latest_analysis_filesList latest analysis filesGETLists the files of the latest analysis in descending order of order_by, with code health scores, change frequency, defects, cost, ownership and recommendations. Use fields to limit the answer.
list_latest_component_filesList latest component filesGETLists the files of one component of the latest analysis in descending order of order_by, with the same file metrics as the files list.

Project, 4 operations

create_projectCreate projectPOSTImports a new project from one or more Git repositories and returns the created project configuration. The repository URLs must be reachable by the user who created the token.
delete_projectDelete projectDELETEDeletes a project, all its analysis results and its developer settings when no other project shares them. Set developer-settings to false to keep the developer settings.
get_projectGet projectGETReturns one project by id: name, owner, analysis status and errors, configured Git remote URLs and description.
list_projectsList projectsGETLists the CodeScene projects the token can access, a page at a time, with id, name and analysis status. Sort with order_by, narrow with filter, and limit returned fields with fields.

Repository, 4 operations

add_project_repositoriesAdd project repositoriesPOSTAdds one or more Git repositories to a project. By default an architectural component is generated for each repository; set generate-architectural-component to false to skip that.
list_project_repositoriesList project repositoriesGETLists the Git repositories of a project with their URL, branch and external id.
remove_project_repositoriesRemove project repositoriesDELETERemoves one or more Git repository URLs from a project.
update_project_repository_branchesUpdate project repository branchesPUTChanges the analysed branch of repositories already registered on the project. Each URL must already belong to the project.

Team, 4 operations

create_teamCreate teamPOSTCreates a team in a developer settings set and returns the team data.
delete_teamDelete teamDELETEDeletes a team from a developer settings set.
list_teamsList teamsGETLists the teams of a developer settings set, a page at a time.
update_teamUpdate teamPUTRenames a team and returns the team data.

Code health trend, 3 operations

list_code_health_trendList code health trendGETTrend of average code health: the lines-of-code weighted average health of all files in the codebase. Score from 10 (healthy code) down to 1 (severe technical debt). Returns one value per date.
list_hotspot_code_health_trendList hotspot code health trendGETTrend of hotspot code health: the lines-of-code weighted average code health of the system-wide hotspots. Score from 10 (healthy code) down to 1 (severe technical debt). Returns one value per date.
list_worst_performer_trendList worst performer trendGETTrend of the worst performer: the code health of the file or files with the lowest code health in the codebase. Score from 10 (healthy code) down to 1 (severe technical debt). Returns one value per date.

Delivery trend, 3 operations

list_delivery_trendList delivery trendGETTrend describing the delivery efficiency of the project (4-factors Delivery dashboard). Returns one value per date.
list_development_time_trendList development time trendGETTrend of development time for the project (4-factors Delivery dashboard); a short development time is a prerequisite for speed to market. One value per date.
list_unplanned_work_trendList unplanned work trendGETTrend of unplanned work (bug fixes and unexpected rework) for the project (4-factors Delivery dashboard). Returns one value per date.

Knowledge trend, 3 operations

list_code_familiarity_trendList code familiarity trendGETTrend of code familiarity; a low value means much of the code was written by former contributors who have left. Returns one value per date.
list_knowledge_islands_trendList knowledge islands trendGETTrend of knowledge islands; a high value means key-person risk, where losing one or two developers loses significant knowledge. One value per date.
list_knowledge_trendList knowledge trendGETTrend describing the knowledge distribution of the project (4-factors Knowledge dashboard). Returns one value per date.

Team alignment trend, 3 operations

list_team_code_alignment_trendList team code alignment trendGETTrend describing the team code alignment of the project (4-factors Team-Code Alignment dashboard). Returns one value per date.
list_team_cohesion_trendList team cohesion trendGETTrend of team cohesion; strong cohesion means each team maps to a meaningful part of the architecture. Returns one value per date.
list_team_coupling_trendList team coupling trendGETTrend of team coupling; loosely coupled teams need less coordination and risk fewer conflicting changes. Returns one value per date.

Author statistic, 2 operations

list_analysis_author_statisticsList analysis author statisticsGETReturns per-author statistics of an analysis: commits, lines added, removed and net, first and last contribution, months contributing, primary file and component ownership.
list_latest_author_statisticsList latest author statisticsGETReturns per-author statistics of the latest analysis: commits, lines added, removed and net, first and last contribution, months contributing, primary file and component ownership.

Badge, 2 operations

get_project_badgesGet project badgesGETReturns which status badges are enabled for the project: average code health, hotspot code health, missed goals and system mastery.
update_project_badgesUpdate project badgesPUTEnables or disables the project's status badges. All four flags are required: read get_project_badges first and send the current values back with your change.

Branch statistic, 2 operations

list_analysis_branch_statisticsList analysis branch statisticsGETReturns per-branch statistics of an analysis: commits, authors, duration, lead times to merge, merged flag and delivery risk.
list_latest_branch_statisticsList latest branch statisticsGETReturns per-branch statistics of the latest analysis: commits, authors, duration, lead times to merge, merged flag and delivery risk.

Code coverage, 2 operations

delete_code_coverageDelete code coverageDELETEDeletes all uploaded code coverage data of a repository.
list_code_coverageList code coverageGETLists the metadata of the code coverage data uploaded for a repository: format, metric, commit, repository path and upload time.

Commit, 2 operations

list_analysis_commitsList analysis commitsGETLists the commits of an analysis, a page at a time: revision, author, date, repository, ticket id, files and lines added or deleted.
list_latest_commitsList latest commitsGETLists the commits of the latest analysis, a page at a time: revision, author, date, repository, ticket id, files and lines added or deleted.

Commit activity, 2 operations

list_analysis_commit_activityList analysis commit activityGETReturns the weekly commit activity trend of an analysis: number of revisions and authors per date.
list_latest_commit_activityList latest commit activityGETReturns the weekly commit activity trend of the latest analysis: number of revisions and authors per date.

Component config, 2 operations

get_project_componentsGet project componentsGETReturns the project's architectural components configuration: each component's name and the file patterns it covers.
replace_project_componentsReplace project componentsPOSTReplaces the whole architectural components configuration of the project with the list sent. Read get_project_components first and send back every component to keep.

Coverage gate, 2 operations

get_project_coverage_gate_insightsGet project coverage gate insightsGETReturns aggregated code coverage gate results of a project over a period: gates evaluated, passed, failed, pass rate, and each gate's metric and threshold distribution.
list_project_coverage_gate_outcomesList project coverage gate outcomesGETLists individual code coverage gate results of a project over a period, a page at a time: whether all gates passed, measured coverage vs threshold per gate, and the files to test.

Delta analysis, 2 operations

get_delta_analysisGet delta analysisGETReturns one delta (pull request) analysis: code health change per file, enabled and failed quality gates, commits, authors, base ref and branch head.
list_delta_analysesList delta analysesGETLists the delta analyses (pull request reviews) of a project, a page at a time, with id, repository and analysis time.

Developer settings, 2 operations

delete_developer_settingDelete developer settingDELETEDeletes a developer settings set by id, with its teams and developers.
list_developer_settingsList developer settingsGETLists the developer settings sets (author and team configurations shared by projects), a page at a time.

Issue, 2 operations

list_analysis_issuesList analysis issuesGETLists the issues (tickets) of an analysis, a page at a time, with status, cycle time, first and last commit, files changed and lines added or deleted.
list_latest_issuesList latest issuesGETLists the issues (tickets) of the latest analysis, a page at a time, with status, cycle time, first and last commit, files changed and lines added or deleted.

Pr safeguard, 2 operations

get_project_pr_safeguard_insightsGet project pr safeguard insightsGETReturns aggregated Code Health safeguard activity on a project's pull requests over a date range: totals, a verdict (no-issues, stable or degrading) and monthly trends.
list_project_pr_safeguard_outcomesList project pr safeguard outcomesGETLists per pull request Code Health safeguard outcomes of a project over a date range, a page at a time: PR id, date, repository, authors, findings and verdict.

Technical debt, 2 operations

get_analysis_technical_debtGet analysis technical debtGETReturns the technical debt friction of an analysis, or with refactoring_targets=true its technical debt hotspots. The vendor does not document the response shape.
get_latest_technical_debtGet latest technical debtGETReturns the technical debt friction of the latest analysis, or with refactoring_targets=true its technical debt hotspots. The vendor does not document the response shape.

Active author, 1 operation

list_active_authorsList active authorsGETLists the active authors (anyone who committed in the last three months) across the projects the token can access, with the projects each contributed to.

Engineering outcome, 1 operation

get_engineering_outcomesGet engineering outcomesGETEstimates the engineering impact of moving code from one Code Health score to another: 90% intervals for defects, development time and combined productivity, plus a plain-language summary.

Repository project, 1 operation

list_repository_projectsList repository projectsGETLists the projects the token can access, grouped by repository, with each repository's id and project ids.

Use CodeScene from Claude Code, Cursor or Codex

Connect CodeScene in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its CodeScene operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect CodeScene

Create your workspace
Sign up free. Nothing to install.
Connect CodeScene once
Add your CodeScene connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.