Linear MCP Server vs Stripe Agent Toolkit

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Linear MCP Server MCP Servers	Stripe Agent Toolkit MCP Servers
Tagline	Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)	Stripe's official SDK and MCP server for wiring AI agents into payments, billing, and customer operations.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.	Free· Toolkit and MCP server are free (MIT). Underlying Stripe usage is billed at standard Stripe rates (typically 2.9% + 30 cents per successful card charge; billing/subscriptions and other products priced separately). LLM/model calls billed by your model provider.
Model	—	—
Editorial score	—	—
Use cases	Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server	MCP server for Claude Desktop and CursorAI support agent that issues refundsE-commerce copilot generating payment linksAutonomous invoicing and dunning workflowsInternal ops assistant reading MRR and disputesMetering and billing LLM token usage to end usersSubscription management via chat interfaceCustomer lookup and enrichment inside agents
Pros	Open source (MIT) and small enough to read end-to-end in an afternoon One-line install via Smithery or straight npx in Claude Desktop config Covers the create / update / search / comment loop that 90% of ticket workflows need Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents) Clear tool schemas make it a good reference implementation for building your own MCP servers Uses Linear's official GraphQL API, so permissions and audit trails stay intact	Official Stripe project, MIT-licensed, maintained in the stripe/ GitHub org rather than a community fork. Covers three integration styles: hosted MCP server, Vercel AI SDK plugin, and framework-free SDK for OpenAI/Anthropic/Gemini. One-command installers for Claude Code, Codex, Cursor, and Grok Build make it trivial to add Stripe tools to popular agent clients. Uses Stripe restricted API keys, so tool permissions map cleanly onto real Stripe scopes rather than a bespoke auth layer. Includes a token-meter helper so agents can bill their own LLM usage back to end customers through Stripe billing. Both TypeScript and Python bindings, keeping parity for teams standardized on either stack.
Cons	Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits	Only useful if you already use Stripe; there is no abstraction for Adyen, Braintree, or other processors. Tool coverage tracks the Stripe API surface but is not exhaustive — advanced Connect, Radar, or Terminal workflows may still need direct API calls. Giving an autonomous agent a live Stripe key carries real financial blast radius; safe use requires careful restricted-key scoping and human approval steps. The remote MCP server centralizes auth on Stripe's endpoint, which means outages or rate limits there hit every connected agent. Documentation is spread across GitHub, docs.stripe.com/agents, and per-package READMEs, which slows first-time setup.
Website	github.com	github.com

Pick Linear MCP Server if

✅ Open source (MIT) and small enough to read end-to-end in an afternoon
✅ One-line install via Smithery or straight npx in Claude Desktop config
✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)

Pick Stripe Agent Toolkit if

✅ Official Stripe project, MIT-licensed, maintained in the stripe/ GitHub org rather than a community fork.
✅ Covers three integration styles: hosted MCP server, Vercel AI SDK plugin, and framework-free SDK for OpenAI/Anthropic/Gemini.
✅ One-command installers for Claude Code, Codex, Cursor, and Grok Build make it trivial to add Stripe tools to popular agent clients.
✅ Uses Stripe restricted API keys, so tool permissions map cleanly onto real Stripe scopes rather than a bespoke auth layer.

Compare a different pair →