Context7 vs Where Them Logs
A side-by-side look at the Context7 and Where Them Logs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
Where Them LogsDeveloper ToolsWhere apps write their log files on Windows, macOS and Linux, as exact copyable paths.33EmergingAuth: not declaredVerdict: choose Context7 for developer tools work as a local process; choose Where Them Logs for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Context7 when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
resolve-library-id, query-docs.
WChoose Where Them Logs when
- You need dedicated capabilities in the Developer Tools domain.
- You have the keys it needs:
LOCAL_ADMIN_BYPASS, COSMOS_ENDPOINT, COSMOS_DATABASE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Where Them Logs | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 65/100 · Great | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | LOCAL_ADMIN_BYPASSCOSMOS_ENDPOINTCOSMOS_DATABASE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 63,150 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Context7 | View Where Them Logs |
Tools & capabilities
Context7 tools 2
resolve-library-idResolves a general library name into a Context7-compatible library ID.query-docsRetrieves documentation for a library using a Context7-compatible library ID.
Where Them Logs 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.
Context7
{
"mcpServers": {
"upstash-context7": {
"command": "npx",
"args": [
"-y",
"ctx7"
]
}
}
}
Where Them Logs
No confirmed install command for Where Them Logs yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Context7 is categorized under Developer Tools and uses a local stdio subprocess. Where Them Logs belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Context7 for developer tools work and Where Them Logs for developer tools.
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. Where Them Logs has no confirmed install command yet — follow its own setup instructions.
Context7 is listed as free. Auth: api key required. Where Them Logs 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 upstash-context7 and where-them-logs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context7 has a quality signal of 65/100 (Great) with 9 views, 0 installs and 63,150 GitHub stars. Where Them Logs has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.