Integration

LinearB integration

LinearB is a software engineering intelligence platform that measures delivery (cycle time, deployment frequency, DORA metrics) from Git, project management and incident data. Report deployments and incidents, query and export team metrics, manage teams and their members, contributors (users), services, Git repositories and their configuration, project-management scope, custom reported metrics and metrics-builder dashboards, and export the audit log. The API token routes and the deprecated cycle-time-stage route are not exposed. Authentication is a LinearB API token sent in the x-api-key header; rate limits are 60 calls per minute per endpoint.

Connect LinearB How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with LinearB

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.

Scope, 10 operations

clear_team_git_scopeClear team git scopeDELETEClears a team's whole Git scope, repositories and services.
clear_team_git_scope_keyClear team git scope keyDELETEClears one key (repositories or services) of a team's Git scope.
clear_team_pm_scopeClear team pm scopeDELETEClears every scope key of a team on one integration; on Jira this also switches the team to Kanban.
clear_team_pm_scope_keyClear team pm scope keyDELETEClears one scope key of a team on one integration.
get_team_git_scopeGet team git scopeGETReturns the repositories and services assigned to one team (not to its descendant teams).
get_team_pm_scopeGet team pm scopeGETReturns a team's project-management scope (boards, projects and other keys), one item per integration.
replace_team_git_scopeReplace team git scopePUTReplaces a team's whole Git scope: each key sent becomes exactly that list and a key not sent is cleared. At least one key is required.
replace_team_pm_scopesReplace team pm scopesPOSTFor each item, replaces that team's whole scope document on that integration: a key the item omits is cleared. Each item must name at least one key.
update_team_git_scopeUpdate team git scopePATCHChanges the keys sent of a team's Git scope (repositories, services): mode merge replaces each key's list, mode add adds ids and removes none. Keys not sent are kept.
update_team_pm_scope_keysUpdate team pm scope keysPATCHFor each item, replaces the named scope keys of that team on that integration (mode add adds to them instead); keys not named are kept.

Config, 7 operations

get_git_configGet git configGETReturns the organization-wide default of every repository setting section and the organization-only sections.
get_repository_configGet repository configGETReturns a repository's settings; each section says whether the repository overrides it, with the organization default alongside.
replace_repository_configReplace repository configPUTReplaces a repository's overrides: each section sent overrides the default and every section not sent returns to the organization default.
reset_repository_configReset repository configDELETERemoves every override of a repository so it follows the organization default again.
reset_repository_config_sectionReset repository config sectionDELETERemoves a repository's override of one section so it follows the organization default; nothing changes if it was not overridden.
update_git_configUpdate git configPATCHChanges the organization-wide default of each section sent; other sections and repositories that override a section are unaffected. Some changes recalculate history.
update_repository_configUpdate repository configPATCHOverrides the organization default of each section sent for one repository; other sections are kept. Never changes the organization default.

Service, 5 operations

create_servicesCreate servicesPOSTCreates several services at once, each mapped to repositories and directory paths.
delete_serviceDelete serviceDELETEDeletes a service.
get_serviceGet serviceGETReturns one service with its repository paths.
list_servicesList servicesGETLists the services configured in LinearB with their repositories and paths.
update_serviceUpdate servicePUTChanges a service's name or its repository paths.

Incident, 4 operations

create_incidentCreate incidentPOSTReports an incident (provider_id, http_url, title, issued_at) so LinearB computes change failure rate and MTTR; link it to teams, services, repositories and the Git ref that caused it.
delete_incidentDelete incidentDELETEDeletes an incident reported through the API, by its provider_id.
get_incidentGet incidentGETReturns one incident reported through the API, by its provider_id.
update_incidentUpdate incidentPATCHChanges an incident reported earlier, by its provider_id; send only the fields to change (for example ended_at when it is resolved).

Member, 4 operations

add_team_membersAdd team membersPATCHAdds users to a team (by user id or email, with optional joined_at), keeping current members.
list_team_membersList team membersGETLists the members of a team with their join date.
remove_team_memberRemove team memberDELETERemoves one member from a team, by user id or email.
set_team_membersSet team membersPOSTReplaces a team's whole membership with the users sent, by user id or email, each with an optional joined_at date.

Team, 4 operations

create_teamsCreate teamsPOSTCreates teams in bulk as a background job and returns its job_id; follow it with get_job_status. To create one team at once use create_team.
delete_teamDelete teamDELETEDeletes a team.
list_teamsList teamsGETSearches teams by name (search_term) and type, page with offset and page_size (at most 50).
update_teamUpdate teamPATCHChanges a team's properties (name, color, parent and so on); only the fields sent change.

User, 4 operations

create_usersCreate usersPOSTCreates users in bulk as a background job and returns its job_id; follow it with get_job_status.
delete_userDelete userDELETEDeletes a LinearB user.
list_usersList usersGETSearches LinearB users (contributors): search_term matched on the field named by search_by_field (id, name or email), filter by role, sort by name or email, page with offset.
update_userUpdate userPATCHChanges a user's fields; custom_info is kept when not sent.

Entity, 3 operations

list_pm_entities_by_typeList pm entities by typeGETLists project-management entities of one type per integration: what exists, what is selected for collection and what uses it.
search_pm_entitiesSearch pm entitiesGETFinds project-management entities of one type (projects, boards, labels, sprints and so on) by keyword. For selection state and usage, use list_pm_entities_by_type.
select_pm_entitiesSelect pm entitiesPATCHSelects or deselects entities of one type on one integration for data collection.

Deployment, 2 operations

create_deploymentCreate deploymentPOSTReports a deployment (or a custom pre-deploy stage) of a Git ref in a repository so LinearB measures deploy time; returns a request_id. The stage field is a paid-plan feature.
list_deploymentsList deploymentsGETLists reported deployments and pre-deploy stages, newest first; filter by repository_id, commit_sha, stage or a time window (after, before) and page with limit and offset.

Export, 2 operations

export_audit_logExport audit logGETExports the organization audit log for a date range as CSV or JSON and returns a download URL valid for 1 hour.
export_metricsExport metricsPOSTVariant of query_metrics that writes the report to a CSV or JSON file and returns its report_url instead of the rows. Business and Enterprise plans.

Repository, 2 operations

list_git_repositoriesList git repositoriesGETLists the organization's Git repositories with their monitoring state; filter by name, provider_id, integration, monitoring state or visibility.
set_repositories_monitoringSet repositories monitoringPATCHSets up to 100 repositories to monitored or not_monitored. Monitoring loads the repository's history and counts against the repository quota.

Search, 2 operations

search_incidentsSearch incidentsPOSTSearches incidents reported through the API by date range, team, service, repository or status; sort and page with limit and offset.
search_incidents_unifiedSearch incidents unifiedPOSTVariant of search_incidents that also returns incidents derived from Jira or Azure Boards issues, the same data as the LinearB Incidents activity page.

Classification, 1 operation

classify_usersClassify usersPATCHSets bot and metrics-exclusion flags on up to 25 users; flags are set to the value sent, so a retry is safe. Users in the skipped map were not changed.

Dashboard, 1 operation

list_dashboardsList dashboardsGETBeta. Lists Metrics Builder dashboards: every public dashboard plus the account's private ones, with their metric ids for execute_dashboard_metric.

Execute, 1 operation

execute_dashboard_metricExecute dashboard metricPOSTBeta. Runs a saved Metrics Builder metric of a dashboard and returns its data rows; start_date and end_date are required in the body.

Health, 1 operation

get_healthGet healthGETChecks that the LinearB API is up and the key is accepted; answers message OK.

Integration, 1 operation

list_integrationsList integrationsGETLists the organization's project-management and Git integrations, live ones by default (include_invalid also lists deleted ones).

Measurement, 1 operation

query_metricsQuery metricsPOSTReturns metrics (cycle time, PR and commit metrics, AI tool metrics) for time ranges, grouped by organization, team, user, repository or label. Business and Enterprise plans.

Metric, 1 operation

report_custom_metricReport custom metricPOSTReports one value of an external custom metric (code coverage, vulnerabilities, build stability) at a timestamp, optionally tied to a PR, team, repo, commit or contributor.

Organization, 1 operation

get_organizationGet organizationGETReturns the caller's LinearB organization (id, name, settings).

Primary user, 1 operation

set_primary_userSet primary userPOSTMakes a user already merged under a unified user the primary of that merge group.

Reported metric, 1 operation

list_reported_metricsList reported metricsGETLists the external custom metrics configured for the organization (empty when none).

Single, 1 operation

create_teamCreate teamPOSTCreates one team at once and returns it (unlike create_teams, which runs in the background).

Status, 1 operation

get_job_statusGet job statusGETReturns the status of a background job, by the job_id that create_users or create_teams returned.

Unmerge, 1 operation

unmerge_usersUnmerge usersPOSTSplits users out of a unified user, each becoming a standalone user again. The primary user cannot be unmerged: set another primary first.

Use LinearB from Claude Code, Cursor or Codex

Connect LinearB in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its LinearB 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 LinearB

Create your workspace
Sign up free. Nothing to install.
Connect LinearB once
Add your LinearB 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.