Autopm vs MCP Linear

A side-by-side look at the Autopm and MCP Linear MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Autopm logoAutopmProduct Management18 AI product-management robots for market research, financials, and execution specs. No API keys29EmergingAuth: not declaredMCP Linear logoMCP LinearProduct Management · Local subprocess (stdio)Integrates with Linear project management system51GoodAuth: api key required

Verdict: choose Autopm for product management work; choose MCP Linear for product management as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Autopm logoChoose Autopm when

  • You need dedicated capabilities in the Product Management domain.
Explore Autopm

MCP Linear logoChoose MCP Linear when

  • You need dedicated capabilities in the Product Management domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: LINEAR_API_TOKEN, LINEAR_OAUTH_ACCESS_TOKEN.
Explore MCP Linear

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAutopm logoAutopmMCP Linear logoMCP Linear
CategoryProduct ManagementProduct Management
Quality signal29/100 · Emerging51/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredFree
Required env varsNone listedLINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars1148
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Autopm tools

No tool names declared yet. Check the project README from the listing page.

MCP Linear tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Autopm

No confirmed install command for Autopm yet — follow the setup steps linked from its listing page rather than a guessed package name.

MCP Linear

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "tacticlaunch-mcp-linear": {
      "command": "npx",
      "args": [
        "-y",
        "@tacticlaunch/mcp-linear"
      ],
      "env": {
        "LINEAR_API_TOKEN": "YOUR_LINEAR_API_TOKEN_HERE",
        "LINEAR_OAUTH_ACCESS_TOKEN": "YOUR_LINEAR_OAUTH_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

Autopm is categorized under Product Management and uses an install path we have not confirmed yet. MCP Linear belongs to Product Management and uses a local stdio subprocess. Pick Autopm for product management work and MCP Linear for product management.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Autopm has no confirmed install command yet — follow its own setup instructions.

Autopm has no declared pricing — check the project's own site. MCP Linear is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add autopm and tacticlaunch-mcp-linear as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Autopm has a quality signal of 29/100 (Emerging) with 1 views, 0 installs and 1 GitHub stars. MCP Linear has 51/100 (Good) with 3 views, 0 installs and 148 GitHub stars.