Fathom MCP vs Nx Console
A side-by-side look at the Fathom MCP and Nx Console MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
Fathom MCPDeveloper Tools · Remote HTTP/SSEGive your AI assistant real meeting context via Fathom so every output grounded in your work42FairAuth: not declaredVerdict: choose Fathom MCP for developer tools work over a hosted endpoint; choose Nx Console 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?
FChoose Fathom MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
Choose Nx Console when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Fathom MCP | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 42/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1,413 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fathom MCP | View Nx Console |
Tools & capabilities
Fathom MCP tools
No tool names declared yet. Check the project README from the listing page.
Nx Console 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.
Fathom MCP
{
"mcpServers": {
"mcp-13": {
"url": "https://api.fathom.ai/mcp"
}
}
}
Nx Console
{
"mcpServers": {
"nx-console": {
"command": "npx",
"args": [
"-y",
"create-nx-workspace@latest"
]
}
}
}
Frequently asked questions
Fathom MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Nx Console belongs to Developer Tools and uses a local stdio subprocess. Pick Fathom MCP for developer tools work and Nx Console 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.
Fathom MCP has no declared pricing — check the project's own site. Nx Console 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 mcp-13 and nx-console as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fathom MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Nx Console has 51/100 (Good) with 2 views, 0 installs and 1,413 GitHub stars.