Skip to main content
Glama
465,824 tools. Updated 2026-08-19 07:25

"Linear ticket integration tool for code context enhancement" matching MCP tools:

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    An MCP server that provides dynamic codebase context to Claude Code through tools like hybrid search, recent changes, and symbol definitions, enhancing AI-assisted coding with local RAG.
    8
    MIT
  • A
    license
    -
    quality
    D
    maintenance
    Enables AI coding assistants to automatically scan, store, and query API endpoints from codebases, providing instant lookup and semantic search to reduce context switching and token consumption.
    1
    MIT

Matching MCP Connectors

  • Search, read and create Linear issues, projects, teams and cycles.

  • Linear MCP — wraps the Linear GraphQL API (OAuth)

  • Retrieve a specific Linear ticket by ID to view its details and status. Fetches issue information directly from Linear.
    MIT
  • Retrieve the source code for a specific ABAP enhancement implementation by providing the enhancement spot and implementation name.
    MIT
  • Generate integration workflows and code snippets for implementing Chargebee functionality in your application. Specify your goal and programming language to get accurate implementation guidance.
    MIT
  • Retrieve source code of an enhancement implementation by providing its name and the enhancement spot. Access specific ABAP enhancement source via ADT.
    MIT
  • Export scan findings as SARIF 2.1.0 JSON for integration with GitHub Code Scanning, VS Code, and CI pipelines.
    Apache 2.0
  • Add a comment to a Linear ticket by specifying the ticket ID and comment text. Use this tool to provide updates, feedback, or additional details on existing tickets.
  • Retrieve detailed information about a Linear issue, including comments, using the issue ID. Designed to integrate with the Linear MCP Server for efficient issue tracking and management.
  • Cross-check extracted meeting note items (blockers, ticket references, feature/bug mentions) against the Linear dependency graph to identify unrecorded blockers, status mismatches, or overlaps with existing tickets.