Burnlore vs Filesystem
A side-by-side look at the Burnlore and Filesystem MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Burnlore for art & culture work; choose Filesystem for file systems as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Filesystem when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
path, head, tail.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Burnlore | |
|---|---|---|
| Category | Art & Culture | File Systems |
| Quality signal | 12/100 · Emerging | 85/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | — | 91,512 |
| Directory activity | 0 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | Not listed | 17 |
| Full listing | View Burnlore | View Filesystem |
Tools & capabilities
Burnlore tools
No tool names declared yet. Check the project README from the listing page.
Filesystem tools 17
pathheadtailpathscontenteditsoldTextnewTextdryRunsortBysourcedestination- +5 more on 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.
Burnlore
No confirmed install command for Burnlore yet — follow the setup steps linked from its listing page rather than a guessed package name.
Filesystem
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem"
]
}
}
}