> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibely.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Linear

> Let your published app read and create Linear issues, or let Vibely build features straight from your Linear tickets.

Linear is an issue tracker for software teams. Vibely connects to it in two separate ways, and you can use either or both:

* **App connector.** Your published app reads and writes Linear while people use it: a public roadmap, or a bug report form that files issues.
* **Chat connector.** Vibely reads your issues and specs while you build, so you can say `Implement ENG-412` and it works from the real ticket.

<Frame>
  <img src="https://cdn.vibely.sh/doc/v1/integrations-linear.webp" alt="Connect your app to Linear" width="1200" height="675" />
</Frame>

Each is its own authorization. Connecting one doesn't connect the other.

## What you can build

| Use case | Example prompt | Connection |
| - | - | - |
| Public roadmap | `Build a public roadmap page from my Linear projects, grouped by status.` | App |
| Bug report form | `Add a support form that files a Linear issue in the Support team.` | App |
| Cycle report | `Add a page showing what shipped in the current cycle.` | App |
| Mobile triage | `Add a screen listing unassigned Support issues that I can assign to myself with one tap.` | App |
| Build from a ticket | `Read ENG-412 in Linear and implement it.` | Chat |
| Sprint prototype | `Prototype the features in our current cycle.` | Chat |

With the app connector, your app can read issues, projects, cycles, and teams, and create and update issues.

## Before you start

* A Linear workspace and an account that can authorize apps in it.
* Access to every team you want the connection to reach. The connection sees what the authorizing account sees.
* Permission to add connectors in your Vibely workspace. See [Admin controls](/integrations/admin-controls).

<Note>
  Linear API usage counts against your Linear plan and its rate limits.
</Note>

## Connect Linear

<Tabs>
  <Tab title="App connector">
    <Steps>
      <Step title="Open the connector">
        In the sidebar, go to **Customize → Connectors** and select **Linear**.
      </Step>

      <Step title="Add a connection">
        Click **Add connection**, then connect. Vibely asks Linear for `read` and `write` access.
      </Step>

      <Step title="Authorize in Linear">
        Approve access in the Linear window that opens.
      </Step>

      <Step title="Ask for the feature">
        In the project chat, describe what you want, for example `Build a public roadmap from my Linear projects.`
      </Step>
    </Steps>
  </Tab>

  <Tab title="Chat connector">
    <Steps>
      <Step title="Open MCP settings">
        Go to **Settings → Connectors**. Linear is listed with the other prebuilt chat connectors.
      </Step>

      <Step title="Connect">
        Click **Connect** next to Linear and approve access in the window that opens.
      </Step>

      <Step title="Use it in the chat">
        Reference a ticket in your prompt, for example `Read ENG-412 in Linear and implement it.` You can switch Linear on or off for your messages from the composer's **+** menu under **Connectors**.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## How each connection works

**App connector.** The connection runs on one shared Linear account. Every visitor to your published app acts as that account. For a company app, authorize with an account that's a member of every relevant team. Your app calls Linear through Vibely's connector gateway, which holds the token, so the token never ships in your app's code.

**Chat connector.** The connection is personal to you. Only you can use it, it runs through Linear's hosted MCP server, and it isn't part of the app you publish.

## Limitations

* **One shared account for the app connector.** Every user of your published app acts as the account that authorized it.
* **Issue-level access only.** `write` covers creating and updating issues and projects. It doesn't cover workspace administration, such as members or billing.
* **Linear's rate limits apply.** Vibely passes them through to your app.

## Manage or disconnect Linear

* The **app** connection is under **Customize → Connectors → Linear**. Disconnecting it stops your published app from reaching Linear; the generated code stays and starts failing until you reconnect or remove it.
* The **chat** connection is under **Settings → Connectors**. Removing it only stops Vibely from reading Linear while you build.

To revoke access from Linear's side, remove the app in your Linear settings.

## FAQ

<AccordionGroup>
  <Accordion title="Do I need both connections?">
    No. Use the app connector if your published app needs Linear. Use the chat connector if you only want Vibely to work from your tickets while it builds.
  </Accordion>

  <Accordion title="Can each user of my app connect their own Linear account?">
    No. The app connector uses one shared account for everyone who uses your app.
  </Accordion>

  <Accordion title="Can my teammates use my chat connection?">
    No. Chat connections are personal. Teammates connect their own Linear accounts.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Connectors" href="/integrations/connectors/overview">App and chat connectors explained.</Card>
  <Card title="Custom MCP servers" href="/integrations/connectors/custom-mcp">Connect a tool that isn't in the catalog.</Card>
  <Card title="Notion" href="/integrations/notion">Another app and chat connector.</Card>
  <Card title="Admin controls" href="/integrations/admin-controls">Who can add connectors.</Card>
</CardGroup>


## Related topics

- [Connect your app to Notion](/integrations/notion.md)
- [App and chat connectors](/integrations/connectors/catalog.md)
- [Connect tools, services, and APIs](/integrations/connectors/overview.md)
- [Connector authentication and credentials](/integrations/connectors/auth.md)
- [Manage connectors in your workspace](/integrations/admin-controls.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.