Soul MCP Server vs Entroly
A side-by-side look at the Soul MCP Server and Entroly MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Soul MCP Server for knowledge & memory work as a local process; choose Entroly 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 Soul MCP Server 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.
- You want tools like
validate_soul_file, generate_soul_template, score_soul_file.
Choose Entroly 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 56/100 · Good | 64/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 475 |
| Directory activity | 11 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Soul MCP Server | View Entroly |
Tools & capabilities
Soul MCP Server tools 3
validate_soul_fileValidates a `.soul.md` file against the SOUL.md schema.generate_soul_templateGenerates a starter `.soul.md` for a given agent name and keywords.score_soul_fileReturns a completeness score (0–100) based on how many optional fields are filled.
Entroly 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.
Soul MCP Server
{
"mcpServers": {
"antoniotf5-soul-mcp-server": {
"command": "npx",
"args": [
"soul-mcp-server"
]
}
}
}
Entroly
{
"mcpServers": {
"juyterman1000-entroly": {
"command": "npx",
"args": [
"-y",
"entroly"
]
}
}
}
Frequently asked questions
Soul MCP Server is categorized under Knowledge & Memory and uses a local stdio subprocess. Entroly belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Soul MCP Server for knowledge & memory work and Entroly 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.
Soul MCP Server is listed as free. Auth: no auth required. Entroly 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 antoniotf5-soul-mcp-server and juyterman1000-entroly as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Soul MCP Server has a quality signal of 56/100 (Good) with 11 views, 0 installs and 2 GitHub stars. Entroly has 64/100 (Good) with 3 views, 0 installs and 475 GitHub stars.
