Dibs vs Faf MCP
A side-by-side look at the Dibs and Faf MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Dibs for developer tools work; choose Faf MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Faf MCP when
- You need dedicated capabilities in the Developer Tools 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 | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 57/100 · Good |
| 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 | Community listing |
| GitHub stars | 2 | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dibs | View Faf MCP |
Tools & capabilities
Dibs tools
No tool names declared yet. Check the project README from the listing page.
Faf 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.
Dibs
No confirmed install command for Dibs yet — follow the setup steps linked from its listing page rather than a guessed package name.
Faf MCP
{
"mcpServers": {
"wolfe-jam-faf-mcp": {
"command": "bunx",
"args": [
"faf"
]
}
}
}
Frequently asked questions
Dibs is categorized under Developer Tools and uses an install path we have not confirmed yet. Faf MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Dibs for developer tools work and Faf MCP for developer tools.
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. Dibs has no confirmed install command yet — follow its own setup instructions.
Dibs has no declared pricing — check the project's own site. Faf MCP 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 dibs and wolfe-jam-faf-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dibs has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. Faf MCP has 57/100 (Good) with 3 views, 0 installs and 7 GitHub stars.