Briar vs Abscissa
A side-by-side look at the Briar and Abscissa MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BriarWorkplace & Productivity · Local subprocess (stdio)Local knowledge store built from GitHub, Jira, Linear and cloud history, served over MCP.43FairAuth: not declaredVerdict: choose Briar for workplace & productivity work as a local process; choose Abscissa for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose Briar when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Choose Abscissa when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LINEAR_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Briar | |
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 43/100 · Fair | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | LINEAR_API_KEY |
| Verified owner | Community listing |
Tools & capabilities
Briar tools
No tool names declared yet. Check the project README from the listing page.
Abscissa 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.
Briar
{
"mcpServers": {
"briar": {
"command": "uvx",
"args": [
"briar-cli"
]
}
}
}
Abscissa
{
"mcpServers": {
"abscissa": {
"command": "uvx",
"args": [
"abscissa"
],
"env": {
"LINEAR_API_KEY": "YOUR_LINEAR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Briar is categorized under Workplace & Productivity and uses a local stdio subprocess. Abscissa belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Briar for workplace & productivity work and Abscissa for workplace & productivity.
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.
Briar has no declared pricing — check the project's own site. Abscissa has no declared pricing — check the project's own site. 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 briar and abscissa as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Briar has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Abscissa has 35/100 (Fair) with 1 views, 0 installs and 1 GitHub stars.
