Call Linear MCP tools via mcporter CLI — issues, projects, teams, comments, cycles, milestones, and more. Use for: 'create Linear issue', 'list my issues', 'update issue status', 'check sprint progress', 'add comment to ticket'. Replaces native Linear MCP plugin to save context window.
Install with Tessl CLI
npx tessl i github:HelloWorldSungin/ark-ai-mcp --skill mcp-linearOverall
score
18%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Two equivalent forms — use whichever is clearer:
# Colon-delimited (shell-friendly, best for simple args)
mcporter call linear.TOOL_NAME key:value key2:value2 --output json
# Function-call style (better for complex args)
mcporter call 'linear.TOOL_NAME(key: "value", key2: "value2")' --output jsonAlways use --output json for machine-readable results you'll parse.
# List issues (assignee "me" = current user)
mcporter call linear.list_issues assignee:me limit:10 --output json
# Search issues by text
mcporter call linear.list_issues query:"search terms" team:ENG --output json
# Get single issue by ID
mcporter call linear.get_issue id:ENG-123 --output json
# Get issue with relations (blocking/blocked-by/duplicates)
mcporter call linear.get_issue id:ENG-123 includeRelations:true --output json
# Create issue
mcporter call 'linear.create_issue(title: "Bug: login broken", team: "ENG", priority: 2, assignee: "me")' --output json
# Create issue with labels
mcporter call 'linear.create_issue(title: "Fix deploy", team: "ENG", labels: "[\"Bug\",\"Infra\"]")' --output json
# Update issue (state, priority, assignee, etc.)
mcporter call 'linear.update_issue(id: "ENG-123", state: "In Progress", priority: 1)' --output json
# Filter by state, label, project, priority, delegate
mcporter call linear.list_issues state:started label:bug project:infra priority:2 --output json
# Filter by date (ISO-8601 durations)
mcporter call 'linear.list_issues(team: "ENG", createdAt: "-P7D")' --output json
mcporter call 'linear.list_issues(team: "ENG", updatedAt: "-P1D")' --output json
# Include archived issues
mcporter call linear.list_issues team:ENG includeArchived:true --output json# List comments on an issue
mcporter call linear.list_comments issueId:ISSUE_UUID --output json
# Create comment (body is markdown)
mcporter call 'linear.create_comment(issueId: "ISSUE_UUID", body: "Comment text here")' --output jsonmcporter call linear.list_teams --output json
mcporter call linear.get_team query:ENG --output json# List/get projects
mcporter call linear.list_projects --output json
mcporter call linear.get_project query:infra --output json
mcporter call linear.get_project query:infra includeMilestones:true --output json
# Create project
mcporter call 'linear.create_project(name: "Q2 Platform", description: "Platform improvements for Q2", teams: "[\"ENG\"]")' --output json
# Update project
mcporter call 'linear.update_project(id: "PROJECT_UUID", state: "started", description: "Updated scope")' --output json
# List project labels
mcporter call linear.list_project_labels --output jsonmcporter call linear.list_users --output json
mcporter call linear.get_user query:me --output jsonMilestones, Documents, Attachments, Cycles, Labels, Statuses, and other tools are documented in references/tool-catalog.md. Or run mcporter list linear --all-parameters to see all tools.
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.