Skip to main content

LinearB MCP Server Connectivity Architecture

See how MCP-compatible AI clients connect securely to LinearB, authenticate with OAuth or an API key, and access engineering data through MCP tools

Steven Silverstone
Updated by Steven Silverstone

The LinearB MCP server provides a secure path between supported AI clients and your LinearB engineering data. This architecture shows the connection methods, authentication options, MCP tools, and data domains involved.

Endpoint: https://mcp.linearb.io/mcp
Recommended authentication: OAuth
Required access: Company Admin rights for the correct LinearB workspace

Connectivity Architecture

1 2 3 4 Client layer Authentication MCP server LinearB data domains Native streamable HTTP No bridge needed Claude Desktop · Claude Code · Cursor VS Code · Codex · Windsurf mcp-remote bridge Local stdio proxy For clients without native HTTP MCP Cline · Zed · others HTTPS request + credentials RECOMMENDED OAuth User-based · no keys to store or rotate Redirects to LinearB for approval ALTERNATIVE API key Header-based · Settings → API Tokens For clients that can't use OAuth Authenticated request https://mcp.linearb.io/mcp 16 tools discovered when the client connects get_metrics · search_pull_requests · get_issues · calculate_lead_time · +12 more Scoped read of your workspace Scoped, read-only access to: Delivery & throughput · Quality · DORA · DevEx Pull requests & branches · Repositories & contributors · Releases Incidents & services · Teams & users · Issues & PM entities · AI dev tools
The four-stage connectivity path: client → authentication → MCP server → scoped data access.

1 — Client layer

Native streamable HTTP

No bridge is needed for clients that support HTTP MCP.

  • Claude Desktop
  • Claude Code
  • Cursor
  • VS Code
  • Codex
  • Windsurf
{ "url": "https://mcp.linearb.io/mcp" }

Via mcp-remote bridge

Use a local stdio proxy for Cline, Zed, or any client without HTTP MCP support.

npx @modelcontextprotocol/mcp-remote <url>

HTTPS request + credentials ↓

2 — Authentication

Secure, user-based authentication. There are no keys to store or rotate, and every flow redirects to LinearB for approval.

API key (Alternative)

For clients that cannot use OAuth, generate a key in Settings → API Tokens and send it as a header.

{ "headers": { "x-api-key": "LINEARB_ADMIN_API_KEY" } }

3 — MCP server https://mcp.linearb.io/mcp

16 tools discovered when the client connects:

  • get_metrics
  • get_metrics_benchmarks
  • get_ai_dev_tools
  • get_repository_id_by_name
  • search_contributors
  • get_releases
  • search_incidents
  • get_services
  • search_users
  • search_teams_or_groups
  • get_teams
  • search_branches
  • search_pull_requests
  • get_issues
  • calculate_lead_time
  • get_pm_entities

Scoped read of your workspace ↓

4 — LinearB data domains

  • Delivery & throughput
  • Quality
  • DORA
  • DevEx
  • Pull requests & branches
  • Repositories & contributors
  • Releases
  • Incidents & services
  • Teams & users
  • Issues & PM entities
  • AI dev tools

The OAuth Handshake

  1. Add the endpoint in your client and use LinearB for the first time.
  2. The client prompts you to connect, or a CLI command starts the flow.
  3. Your browser opens and redirects to LinearB.
  4. Sign in and approve access for your workspace.
  5. Return to the client. It shows as connected and discovers the tools.

Setup typically takes two to five minutes. Verify important numbers in the LinearB dashboard before publishing a report.

Next Step

Follow Connect to LinearB MCP Server for client-specific setup instructions.

How did we do?

Connect to LinearB MCP Server

MCP Server

Contact