Fathom MCP vs Pipeshub AI

A side-by-side look at the Fathom MCP and Pipeshub AI 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/SSE
Give your AI assistant real meeting context via Fathom so every output grounded in your work42FairAuth: not declared
Pipeshub AI logoPipeshub AIDeveloper Tools · Remote HTTP/SSEThe open-source context layer for AI agents. PipesHub turns your company's knowledge (Slack, Drive, Jira, GitHub, Microsoft 365 and 40+ connectors) into a permission-aware workspace that agents can search, grep, navigate and cite. MCP, SDKs and built-in agents. Self-hosted.57GoodAuth: not declared

Verdict: choose Fathom MCP for developer tools work over a hosted endpoint; choose Pipeshub AI for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

F
Choose Fathom MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
Explore Fathom MCP

Pipeshub AI logoChoose Pipeshub AI when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
Explore Pipeshub AI

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
F
Fathom MCP
Pipeshub AI logoPipeshub AI
CategoryDeveloper ToolsDeveloper Tools
Quality signal42/100 · Fair57/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—3,844
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Fathom MCP tools

No tool names declared yet. Check the project README from the listing page.

Pipeshub AI 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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-13": {
      "url": "https://api.fathom.ai/mcp"
    }
  }
}

Pipeshub AI

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "pipeshub-ai": {
      "url": "https://img.shields.io/npm/v/@pipeshub-ai/mcp?logo=npm&logoColor=white&label=mcp"
    }
  }
}

Frequently asked questions

Fathom MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Pipeshub AI belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Fathom MCP for developer tools work and Pipeshub AI 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. Pipeshub AI is listed as free. 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 pipeshub-ai 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. Pipeshub AI has 57/100 (Good) with 1 views, 0 installs and 3,844 GitHub stars.