A side-by-side look at the 6DuckLearn MCP and Screenpipe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 6DuckLearn MCP for knowledge & memory work; choose Screenpipe for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
SCREENPIPE_LOCAL_API_KEY.Rows where the two servers differ are marked.
| Spec | 6 6DuckLearn MCP | S Screenpipe |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 27/100 · Emerging | 41/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | SCREENPIPE_LOCAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View 6DuckLearn MCP | View Screenpipe |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for 6DuckLearn MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"screenpipe": {
"command": "npx",
"args": [
"-y",
"screenpipe-mcp@latest"
],
"env": {
"SCREENPIPE_LOCAL_API_KEY": "YOUR_SCREENPIPE_LOCAL_API_KEY_HERE"
}
}
}
}
