A side-by-side look at the Context and Mjucius Cozi MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Context for workplace & productivity work as a local process; choose Mjucius Cozi MCP 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?
Choose Context when
You need dedicated capabilities in the Workplace & Productivity domain.
No tool names declared yet. Check the project README from the listing page.
Mjucius Cozi 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.
Context is categorized under Workplace & Productivity and uses a local stdio subprocess. Mjucius Cozi MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Context for workplace & productivity work and Mjucius Cozi 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.
Context has no declared pricing — check the project's own site. Mjucius Cozi MCP 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 context and mjucius-cozi-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Mjucius Cozi MCP has 45/100 (Fair) with 1 views, 0 installs and 4 GitHub stars.