Briar vs Scrivener MCP
A side-by-side look at the Briar and Scrivener MCP 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 Scrivener MCP for knowledge & memory 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 Scrivener MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Briar | |
|---|---|---|
| Category | Workplace & Productivity | Knowledge & Memory |
| Quality signal | 43/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
Tools & capabilities
Briar tools
No tool names declared yet. Check the project README from the listing page.
Scrivener MCP 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"
]
}
}
}
Scrivener MCP
{
"mcpServers": {
"writerslogic-scrivener-mcp": {
"command": "npx",
"args": [
"-y",
"scrivener-setup"
]
}
}
}
Frequently asked questions
Briar is categorized under Workplace & Productivity and uses a local stdio subprocess. Scrivener MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Briar for workplace & productivity work and Scrivener MCP for knowledge & memory.
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. Scrivener MCP is listed as free. Auth: no auth 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 briar and writerslogic-scrivener-mcp 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. Scrivener MCP has 61/100 (Good) with 18 views, 12 installs and 67 GitHub stars.
