Chatpack MCP vs Netlogger MCP
A side-by-side look at the Chatpack MCP and Netlogger MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredN
Netlogger MCPDeveloper Tools · Local subprocess (stdio)NetLogger MCP server. Nets on the air, live check-ins and who's up, past nets.53GoodAuth: no auth requiredVerdict: choose Chatpack MCP for developer tools work as a local process; choose Netlogger MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
NChoose Netlogger MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
NETLOGGER_MCP_CALLSIGN, NETLOGGER_MCP_MOCK. - You want tools like
netlogger_active_nets, netlogger_checkins, netlogger_past_nets.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Chatpack MCP | N Netlogger MCP |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | NETLOGGER_MCP_CALLSIGNNETLOGGER_MCP_MOCK |
| Verified owner | Verified | Community listing |
| GitHub stars | 224 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 6 |
| Full listing | View Chatpack MCP | View Netlogger MCP |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
Netlogger MCP tools 6
netlogger_active_netsNets on the air now: frequency, band, mode, net control, logger, monitoring countnetlogger_checkinsA live net's check-in list, plus the pointer (the station being worked now)netlogger_past_netsClosed nets over the last N days, with the net IDs past check-ins neednetlogger_past_checkinsA closed net's check-in listnetlogger_set_callsignSave your callsign (asked once, on first use)get_version_infoService version + upstream spec version (fleet identity attestation)
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.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Netlogger MCP
{
"mcpServers": {
"netlogger-mcp": {
"command": "uvx",
"args": [
"netlogger-mcp"
],
"env": {
"NETLOGGER_MCP_CALLSIGN": "YOUR_NETLOGGER_MCP_CALLSIGN_HERE",
"NETLOGGER_MCP_MOCK": "YOUR_NETLOGGER_MCP_MOCK_HERE"
}
}
}
}
Frequently asked questions
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. Netlogger MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Chatpack MCP for developer tools work and Netlogger MCP 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.
Chatpack MCP is listed as free. Auth: no auth required. Netlogger 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 chatpack-mcp and netlogger-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars. Netlogger MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.