Linksee Memory vs Penfield MCP
A side-by-side look at the Linksee Memory and Penfield MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Linksee Memory for knowledge & memory work as a local process; choose Penfield MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Linksee Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Penfield MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 57/100 · Good | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 15 | 6 |
| Directory activity | 4 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Linksee Memory | View Penfield MCP |
Tools & capabilities
Linksee Memory tools
No tool names declared yet. Check the project README from the listing page.
Penfield 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.
Linksee Memory
{
"mcpServers": {
"michielinksee-linksee-memory": {
"command": "npx",
"args": [
"-y",
"linksee-memory"
]
}
}
}
Penfield MCP
{
"mcpServers": {
"penfieldlabs-penfield-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Frequently asked questions
Linksee Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. Penfield MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Linksee Memory for knowledge & memory work and Penfield MCP for knowledge & memory.
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.
Linksee Memory is listed as free. Auth: no auth required. Penfield 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 michielinksee-linksee-memory and penfieldlabs-penfield-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Linksee Memory has a quality signal of 57/100 (Good) with 4 views, 0 installs and 15 GitHub stars. Penfield MCP has 49/100 (Fair) with 4 views, 0 installs and 6 GitHub stars.