Skip to main content
Book a demo

Connect Linear to VS Code

Give VS Code governed access to Linear’s 82 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Linear to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Linear in Runlayer

    Add Linear from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Linear’s 82 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Linear

    Sign in the way Linear requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Linear from VS Code

    Linear’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

82 Linear tools in VS Code

Runlayer policy decides which of these VS Code users can call. 17 read data only.

  • Create attachment

    Deprecated fallback for tiny files only.

  • Create attachment from upload

    Link an already-uploaded Linear assetUrl to an existing issue as an attachment.

  • Create initiative label

    Create a new Linear initiative label.

  • Create issue label

    Create a new Linear issue label.

  • Delete attachment

    Delete an attachment by ID

  • Delete comment

    Delete a Linear comment.

  • Delete customer

    Delete a customer in Linear

  • Delete customer need

    Archive a customer need in Linear

See all 82 Linear tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Linear call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination