Netlogger MCP vs Appwrite MCP
A side-by-side look at the Netlogger MCP and Appwrite MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
N
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 Netlogger MCP for developer tools work as a local process; choose Appwrite MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Appwrite MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | N Netlogger MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 76/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | NETLOGGER_MCP_CALLSIGNNETLOGGER_MCP_MOCK | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 72 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 6 | Not listed |
| Full listing | View Netlogger MCP | View Appwrite MCP |
Tools & capabilities
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)
Appwrite 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.
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"
}
}
}
}
Appwrite MCP
{
"mcpServers": {
"appwrite-mcp": {
"url": "https://mcp.appwrite.io/"
}
}
}
Frequently asked questions
Netlogger MCP is categorized under Developer Tools and uses a local stdio subprocess. Appwrite MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Netlogger MCP for developer tools work and Appwrite 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.
Netlogger MCP is listed as free. Auth: no auth required. Appwrite MCP is listed as free. Auth: oauth 2.0. 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 netlogger-mcp and appwrite-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Netlogger MCP has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Appwrite MCP has 76/100 (Great) with 3 views, 0 installs and 72 GitHub stars.