Briar vs Teamwork MCP
A side-by-side look at the Briar and Teamwork 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 Teamwork MCP for workplace & productivity over a hosted endpoint. 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 Teamwork MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TW_MCP_BEARER_TOKEN, TW_MCP_SERVER_ADDRESS, NODE_EXTRA_CA_CERTS.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Briar | |
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 43/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | TW_MCP_BEARER_TOKENTW_MCP_SERVER_ADDRESSNODE_EXTRA_CA_CERTS |
Tools & capabilities
Briar tools
No tool names declared yet. Check the project README from the listing page.
Teamwork 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"
]
}
}
}
Teamwork MCP
{
"mcpServers": {
"teamwork-mcp": {
"url": "https://mcp.example.com"
}
}
}
Frequently asked questions
Briar is categorized under Workplace & Productivity and uses a local stdio subprocess. Teamwork MCP belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Briar for workplace & productivity work and Teamwork MCP 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. Teamwork MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 briar and teamwork-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. Teamwork MCP has 48/100 (Fair) with 2 views, 0 installs and 27 GitHub stars.