Linear
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
Scored across 36 tools
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 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.
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.
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 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious 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" + } +] - changed
Input schema / properties / market / descriptionPrevious 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."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious 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."
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious 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." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious 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."
1 tool update
- Changed
resolve_entity1 field changed- changed
Input schema / properties / value / descriptionPrevious 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
MCP server for Linear project management and issue tracking
Monday.com MCP — wraps the Monday.com GraphQL API (BYO API key)
Search, read and create Linear issues, projects, teams and cycles.
AniList MCP — wraps AniList GraphQL API (free, no auth)
Related MCP Servers
- AlicenseBqualityAmaintenanceMulti-workspace Linear MCP server using Personal API Keys instead of OAuth. Provides tools for managing issues, projects, teams, and more across multiple workspaces.5727 PyPI1MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Linear resources through an MCP interface, offering functionality for issue management and resource retrieval with rate limiting and error handling support.481 npm1MIT
- AlicenseBqualityCmaintenanceEnables 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.22MIT
- AlicenseNot gradedqualityCmaintenanceCustom MCP server for Linear that enables managing issues, projects, and workspaces through natural language, backed by raw GraphQL.210 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.