Case study

Keeping Linear in sync with Modiva

A look at how teams use Modiva to connect Linear — filing and updating issues from across their stack and giving AI agents safe, scoped access — without building and maintaining a custom integration.

This is a representative example of the Modiva + Linear workflow. Have a story to share? Tell us and we’ll feature it here.

The challenge

Teams that plan their work in Linear rarely create every issue by hand. Keeping Linear as the source of truth usually means:

• Issues that should be created from support tickets, alerts or AI agents never made it into Linear without manual copy-paste or brittle one-off scripts.
• Each new automation meant re-learning Linear's OAuth, 24-hour token refresh and GraphQL schema from scratch.
• AI assistants and internal agents had no safe, scoped way to file, update or comment on issues.

The approach with Modiva

1. 1

   One connection, not a custom integration

   The team connects Linear to Modiva once through Linear's own OAuth consent screen. Modiva stores the scoped token encrypted at rest and refreshes the 24-hour token automatically — no credentials in code, no cron job babysitting expiry.

2. 2

   Issues, projects & comments over a unified API

   Instead of writing against Linear's GraphQL API directly, the team calls Modiva's unified issue, project, team and comment tools. The same request shape works across every tool Modiva supports, so adding the next system is a connection, not a rewrite.

3. 3

   Issue tracking for AI agents via MCP

   An MCP key exposes the same typed tools to AI assistants and internal agents. The team's agents can file an issue, move it across states, or drop a comment — with scopes the team controls and can revoke at any time.

4. 4

   Real-time reactions via webhooks

   Modiva verifies Linear webhooks and forwards issue, comment and project changes to the team's own endpoints, so downstream automations react the moment something changes rather than polling on a timer.

The outcome

• Linear stays in sync without anyone maintaining bespoke integration code.
• New issue-tracking automations ship in hours, reusing the same tools rather than re-implementing OAuth and GraphQL.
• AI agents read and write issues through scoped, revocable access — never raw API keys.