Skip to content

Add status filtering to Linear MCP list_issues function #2279

Closed
@afneyman

Description

@afneyman

Summary

The Linear MCP currently returns all issues including completed ones when using list_issues or list_my_issues, which can bloat context unnecessarily when working with AI assistants.

Problem

When calling the Linear MCP functions to list issues, all issues are returned regardless of their status (Todo, In Progress, Done, etc.). This means every API call includes completed issues, which:

  • Increases token usage in LLM contexts
  • Makes it harder to focus on active work
  • Provides no way to filter for only open/active issues

Proposed Solution

Add a status or statuses parameter to the list_issues and list_my_issues functions that accepts:

  • A single status ID or name
  • An array of status IDs or names
  • Status types (e.g., 'active', 'completed', 'canceled')

Example usage:

{
  "name": "list_issues",
  "arguments": {
    "assigneeId": "user-id",
    "statuses": ["Todo", "In Progress"]
  }
}

Additional Context

This would be particularly useful for AI assistants and automation tools that need to focus on actionable items without the overhead of filtering completed work client-side.

🤖 Generated with Claude Code

Co-Authored-By: Claude [email protected]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions