Skip to main content
Glama

Server Details

Linear MCP — wraps the Linear GraphQL API (OAuth)

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
32.7% over 38 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-linear
GitHub Stars
0
Server Listing
linear

TDQS

B3.3/5.0

Scored across 36 tools

Disambiguation1/5

The server mixes two entirely different domains (Linear issue tracking and the Pipeworx data-routing platform) under one name, and within the Pipeworx half there are numerous near-duplicate tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are explicitly described as identical routers with only minor variations; deep_research overlaps heavily with ask_pipeworx; and three separate Polymarket edge tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker) are difficult to distinguish at a glance. An agent cannot reliably tell which tool to use for a given query.

Naming Consistency2/5

Naming is inconsistent across the set: the Linear tools use a consistent linear_ prefix, but the Pipeworx tools use ad-hoc names (ask_pipeworx, bet_research, compare_entities, deep_research, forget, recall, remember, subscribe) rather than a single verb_noun or domain-prefixed convention. The mix of snake_case is uniform but the semantic pattern is chaotic, with a few tools (forget, remember, subscribe, unsubscribe) forming a small consistent verb group while others do not.

Tool Count2/5

36 tools is excessive for a single server, especially when it appears to bundle two unrelated domains (Linear issues and the Pipeworx data platform). Several tools are redundant or variant duplicates (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded, three Polymarket edge scanners), suggesting the set has grown without pruning.

Completeness2/5

The Linear portion is notably incomplete: it offers linear_create_issue, linear_get_issue, linear_list_issues, linear_list_teams, and linear_search, but no update, delete, or comment operations, so agents cannot close, edit, or discuss issues—a major gap for an issue-tracking integration. The Pipeworx portion is broad but overlaps heavily and leaves lifecycle gaps such as no clear create/update path for some data resources, making the overall surface uneven.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "when-will-bitcoin-hit-150k"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
        -  }
        -]New value: +[
        +  {
        +    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "market": "will-bitcoin-reach-100k-in-july-2026"
        -  },
        -  {
        -    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
        -  }
        -]New value: +[
        +  {
        +    "market": "when-will-bitcoin-hit-150k"
        +  },
        +  {
        +    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
        +  }
        +]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
        -  {
        -    "topic": "fed"
        -  },
        -  {
        -    "topic": "btc"
        -  }
        -]New value: +[
        +  {
        +    "topic": "fed"
        +  },
        +  {
        +    "topic": "btc"
        +  },
        +  {
        +    "topic": "bitcoin"
        +  },
        +  {
        +    "topic": "fed rate decision"
        +  }
        +]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
  3. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
  4. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."

Related MCP Connectors

Related MCP Servers

  • A
    license
    B
    quality
    A
    maintenance
    Multi-workspace Linear MCP server using Personal API Keys instead of OAuth. Provides tools for managing issues, projects, teams, and more across multiple workspaces.
    57
    27 PyPI
    1
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Linear resources through an MCP interface, offering functionality for issue management and resource retrieval with rate limiting and error handling support.
    481 npm
    1
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Enables MCP clients to read and manage Linear issues, sub-issues, relations, comments, projects, cycles, teams, users, labels, and workflow states using a personal API key.
    22
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Custom MCP server for Linear that enables managing issues, projects, and workspaces through natural language, backed by raw GraphQL.
    210 npm
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.