Integrations
Linear issues, resolved in the thread.
Mention an issue like ENG-12 and the Linear connector replies in the thread with its title and workflow state, plus the state of any GitHub pull requests attached to it.
Status Coming soon: the Linear connector is built but not yet hosted on app.hasarak.com, so it can't be installed there yet.
Linear in Hasarak
Issue keys become context
Write ENG-12 in any message and the connector replies with the issue's identifier, title and current state, like In Progress.
Linked PRs included
Grant it access to the GitHub connector and each reply adds the state of the pull requests attached to the issue.
Up to three issues per message
Standup notes that mention several issues get one reply with a line for each.
An MCP tool: issues.get
MCP programs can call tools.linear.issues.get({ id: "ENG-12" }) for an issue's title, state, URL and attachments.
How the Linear integration works
The Linear connector watches new messages for issue identifiers (a team key, a
dash and a number, like ENG-12 or OPS-7). For each issue it finds, it queries
the Linear API and posts a reply in the message’s thread:
ENG-12 · Rate-limit the sign-in form · In Progress · acme/web#42 open
There’s no need to paste full URLs or switch to the Linear app to check where an issue stands; the answer sits under the message that mentioned it.
Linear and GitHub together
Connectors in Hasarak can call each other, with permission. After you install
both, press refresh on Linear in Settings › Connectors: it asks for the
connector:github permission, and once it’s approved there, Linear replies
include the state of every GitHub PR attached to the issue. You see “ENG-12 is
In Progress and its PR is merged” in one line.
Install it
Install Linear from the built-in marketplace in Settings › Connectors. It reads messages and writes thread replies as its own member, and it never sees DMs.
Related
- Enable LinearInstall the Linear connector so issue keys like ENG-12 get a reply with the issue's title and state, plus attached GitHub PRs.→
- MCPAdd your workspace's /mcp URL to any MCP client. It signs in with OAuth as you and gets one typed API for channels, threads, the inbox, pages and every installed connector.→
- Custom connector (HTTP)Anything that answers HTTP can be a Hasarak connector. The protocol is written in OpenAPI, with a small TypeScript SDK for Cloudflare Workers or Bun; both are being prepared for publishing.→
- CursorEach member signs in to Cursor in the browser. Mention @ai in a message and a Cursor cloud agent answers in the thread, from that member's Cursor plan.→