Connecting to LinearB MCP (OAuth)

The LinearB MCP server allows supported AI tools and IDE assistants to securely access your LinearB data using OAuth — no static API keys required.

Before You Begin

• LinearB role: Company Admin
• An active LinearB account in your company/workspace
• An MCP-compatible client that supports remote MCP servers and OAuth

Connect Using OAuth

MCP client setup varies by tool. Configure the remote MCP server using your client’s instructions, using the endpoint below. After saving, restart your client if required by that tool.

MCP endpoint: https://mcp.linearb.io/mcp

Once your client is configured, the OAuth flow is generally the same:

1. Initiate Connect or Authenticate from your MCP client.
2. Your browser opens automatically.
3. Ensure you are signed into the correct LinearB workspace before approving access.
4. Approve the access request.
5. Return to your client and confirm the server shows as Connected.

Session Behavior

• After authentication, the session is cached by the client.
• Sessions currently expire after 7 days. You will be prompted to reauthenticate when needed.
• Access can be revoked from the LinearB side if required.

Security Model (High-Level)

• No static API keys are shared with end users.
• Authentication is per-user via OAuth.
• Access is delegated securely through the Authorization Code flow.
• Only Company Admin users can authorize MCP connections.

For full technical reference, see the API documentation.

Supported Clients

LinearB MCP works with MCP-compatible clients that support remote MCP servers and OAuth. Below are common setup examples (choose the one that matches your client).

Option 1: Claude Desktop (UI)

Claude Desktop supports OAuth through the Connectors UI (not the config file).

1. Open Claude Desktop.
2. Go to Settings → Connectors → Manage Connectors → Add custom connector.
3. Enter the server URL: https://mcp.linearb.io/mcp
4. Save. On first use, your browser opens for login.

Note: Custom connectors may require a paid Claude plan, depending on your Anthropic subscription.

Option 2: Claude Code (CLI)

Add the MCP server via CLI:

claude mcp add --transport http linearb https://mcp.linearb.io/mcp

To make it available across all projects (user scope):

claude mcp add --transport http linearb https://mcp.linearb.io/mcp --scope user

To share it with your team (project scope, committed to .mcp.json):

claude mcp add --transport http linearb https://mcp.linearb.io/mcp --scope project

Then authenticate:

After adding, run /mcp inside Claude Code, select linearb, then choose Authenticate. Your browser will open for login.

Option 3: Windsurf (native OAuth)

Windsurf supports OAuth natively.

Edit ~/.codeium/windsurf/mcp_config.json:

{
            "mcpServers": {
              "linearb": {
                "serverUrl": "https://mcp.linearb.io/mcp"
              }
            }
          }

Note: Windsurf uses serverUrl (not url).

Restart Windsurf. On first use, your browser will open for login.

Option 4: VS Code (native MCP)

Create or edit .vscode/mcp.json in your workspace:

{
            "servers": {
              "linearb": {
                "type": "http",
                "url": "https://mcp.linearb.io/mcp"
              }
            }
          }

Notes:

• VS Code uses servers (not mcpServers) as the root key.
• For user-level config, open the Command Palette → MCP: Open User Configuration.
• On first use, VS Code will prompt you to authenticate via browser.

Option 5: Zed (uses mcp-remote)

Zed does not yet support native HTTP MCP URLs — use mcp-remote.

Edit ~/.config/zed/settings.json:

{
            "context_servers": {
              "linearb": {
                "settings": {},
                "enabled": true,
                "command": "npx",
                "args": [
                  "-y",
                  "mcp-remote",
                  "https://mcp.linearb.io/mcp"
                ]
              }
            }
          }

Restart Zed. On first use, your browser will open for login.

Other supported clients follow a similar pattern (for example: Cursor, Continue.dev, OpenAI Codex CLI, and VS Code MCP extensions). Use the same MCP endpoint: https://mcp.linearb.io/mcp.

Troubleshooting

Authentication window does not open

• Ensure your client supports OAuth-based remote MCP servers.
• Restart the client and try again.

Connected but no data appears

• Confirm you are signed in as a Company Admin.
• Confirm you are signed in to the correct LinearB workspace.
• Confirm the data exists in LinearB.

Related Articles

• Configuring the MCP Server
• MCP Server – Overview & Use Cases
• AI FAQs