Zerno Lite vs MCP Linear
A side-by-side look at the Zerno Lite and MCP Linear MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Zerno Lite for product management work over a hosted endpoint; 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?
Choose Zerno Lite when
- You need dedicated capabilities in the Product Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
zerno_get_project_brief, zerno_get_agent_context, zerno_list_tasks.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 48/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | LINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 148 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Zerno Lite | View MCP Linear |
Tools & capabilities
Zerno Lite tools 8
zerno_get_project_briefnozerno_get_agent_contextnozerno_list_tasksnozerno_get_tasknozerno_update_taskmutateszerno_submit_task_triagecreates proposalszerno_create_agent_intake_taskcreates a taskzerno_capture_session_eventcreates memory event
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.
Zerno Lite
{
"mcpServers": {
"zerno-lite": {
"url": "https://zerno.one/mcp"
}
}
}
MCP Linear
{
"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
Zerno Lite is categorized under Product Management and uses a remote HTTP/SSE transport. MCP Linear belongs to Product Management and uses a local stdio subprocess. Pick Zerno Lite 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.
Zerno Lite 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 zerno-lite and tacticlaunch-mcp-linear as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Zerno Lite has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Linear has 52/100 (Good) with 4 views, 0 installs and 148 GitHub stars.