Managing Linear Issues and GitHub PRs with MCP

The “Meta-Work” of development (updating tickets, checking PRs) often takes more time than coding. MCP allows you to offload this to AI.

The GitHub MCP Server

Allows you to:

• search_repositories
• get_file_content
• create_issue

Workflow:

“I found a bug in auth.ts. Create a GitHub issue for it with the title ‘Auth Token Expiry Bug’ and paste the relevant code snippet.”

The Linear MCP Server

(Community maintained) Allows you to:

• get_issues
• update_issue

Workflow:

“Find the Linear ticket assigned to me regarding ‘Dark Mode’. Mark it as ‘In Progress’.”

The Unified Dashboard

By combining these in Vibe Manager, you can create a “Project Management” profile for your AI.

Prompt:

“Check my assigned Linear tickets. For the top priority one, find the corresponding GitHub branch, read the latest commit, and tell me if it passes tests.”

This level of orchestration—crossing the boundary between Project Management (Linear) and Code (GitHub)—is the holy grail of automated dev workflows.