{"id":"dot-fun-fathom-mcp","name":"fathom-mcp","homepage":null,"repo_url":"https://github.com/Dot-Fun/fathom-mcp","category":"ai-ml","subcategories":[],"tags":["mcp","fastmcp","python","ai","meetings","transcripts","summaries","webhooks","fathom","integration"],"what_it_does":"An MCP (Model Context Protocol) server (built with FastMCP) that wraps the Fathom AI API to provide MCP tools for listing meetings, fetching summaries and transcripts, listing teams and team members, and managing meeting webhooks.","use_cases":["Let an AI agent query a user’s Fathom meetings (filtered by participants/date ranges/teams)","Retrieve meeting transcripts and summaries for downstream analysis","Automate workflows by creating/deleting Fathom webhooks for meeting notifications","Team-aware meeting discovery (list teams and team members, then list related meetings)"],"not_for":["High-volume production workloads without careful rate-limit handling","Use as a standalone HTTP API for external clients (it is primarily an MCP server)","Use without securing and rotating the Fathom API key"],"best_when":"You want an MCP-compatible agent (e.g., Claude Desktop/Codex) to retrieve meeting artifacts (transcripts/summaries) and react to webhook triggers using Fathom’s API.","avoid_when":"You need fine-grained OAuth-style scopes and short-lived credentials, or you need published idempotency guarantees for create/delete operations.","alternatives":["Fathom’s native API directly (per developers.fathom.ai)","A custom MCP server wrapping Fathom endpoints tailored to your exact tool set","Other MCP servers that expose meeting/transcript data from your calendar/meeting system"],"af_score":78.8,"security_score":65.5,"reliability_score":28.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T15:41:07.731116+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":true},"auth":{"methods":["FATHOM_API_KEY environment variable (API key)"],"oauth":false,"scopes":false,"notes":"Authentication is described as requiring a FATHOM_API_KEY environment variable. No OAuth flow or explicit scope granularity is described."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information for the MCP server itself is provided; Fathom API usage likely applies separately."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":78.8,"security_score":65.5,"reliability_score":28.8,"mcp_server_quality":78.0,"documentation_accuracy":80.0,"error_message_quality":null,"error_message_notes":"README lists common upstream HTTP errors (401/400/404/429) and mentions 429 includes reset time; it does not document MCP-layer error formats.","auth_complexity":95.0,"rate_limit_clarity":82.0,"tls_enforcement":95.0,"auth_strength":65.0,"scope_granularity":40.0,"dependency_hygiene":55.0,"secret_handling":70.0,"security_notes":"Uses an API key via environment variable (not OAuth). Scope granularity is not described. README does not show how secrets are logged/handled inside server code; it does mention returning a webhook secret for signature verification, which increases the importance of secure secret storage.","uptime_documented":0.0,"version_stability":40.0,"breaking_changes_history":30.0,"error_recovery":45.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Rate limits are global (60 calls/60s) and agents may easily exceed this when iterating over many meetings/transcripts; README advises checking specific rate-limit headers but does not provide retry/backoff guidance.","Async delivery is mentioned for get_summary/get_transcript; agents may need to handle eventual results rather than assuming immediate completion.","Webhook creation returns a secret for signature verification; agents must store/use it securely to validate webhook authenticity."]}}