DirForge vs File AI
A side-by-side look at the DirForge and File AI MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DirForge for file systems work over a hosted endpoint; choose File AI 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 DirForge when
- You need dedicated capabilities in the File Systems domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose File AI when
- You need dedicated capabilities in the File Systems domain.
- You prefer a local stdio subprocess transport.
- You want tools like
doc_analyze, doc_read, doc_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | File Systems | File Systems |
| Quality signal | 48/100 · Fair | 49/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 3 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View DirForge | View File AI |
Tools & capabilities
DirForge tools
No tool names declared yet. Check the project README from the listing page.
File AI tools 5
doc_analyzeparse a local file and cache a document index.doc_readread blocks, chunks, or anchors from an existing index or path.doc_searchsearch cached content with source anchors.doc_contextretrieve nearby blocks around an anchor or query.doc_list_formatslist File Viewer core registry formats, all supported extensions, renderer capabilities, and File AI extractor coverage.
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.
DirForge
{
"mcpServers": {
"dissimilis-dirforge": {
"url": "http://localhost:8091/mcp"
}
}
}
File AI
{
"mcpServers": {
"file-ai": {
"command": "npx",
"args": [
"-y",
"@flyfish-dev/file-ai"
]
}
}
}
Frequently asked questions
DirForge is categorized under File Systems and uses a remote HTTP/SSE transport. File AI belongs to File Systems and uses a local stdio subprocess. Pick DirForge for file systems work and File AI for file systems.
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.
DirForge is listed as free. Auth: no auth required. File AI has no declared pricing — check the project's own site. 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 dissimilis-dirforge and file-ai as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DirForge has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 5 GitHub stars. File AI has 49/100 (Fair) with 1 views, 0 installs and 3 GitHub stars.