Can my agent retrieve the summary of a specific meeting from Fathom?

Yes. Use the 'get_summary' tool. Provide the meeting ID, and the agent will return the AI-distilled context, including key discussion points and decisions made during the call natively.

How do I extract action items from a call via chat?

Use the 'get_action_items' tool. Your agent will parse the AI-identified tasks, returning assigned owners and descriptions, making it easy to automate your follow-up workflows.

Can I search for meetings where a specific keyword was mentioned through the agent?

Absolutely. Use the 'search_meetings' tool. Provide your query, and the agent will search through titles, transcripts, and summaries to find matching meetings across your entire Fathom history.

Fathom MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Fathom
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Fathom through Vinkius, pass the Edge URL in the `mcps` parameter and every Fathom tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Fathom Specialist",
    goal="Help users interact with Fathom effectively",
    backstory=(
        "You are an expert at leveraging Fathom tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Fathom "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fathom MCP Server

Connect your Fathom.video account to any AI agent and take full control of your meeting intelligence and automated note-taking through natural conversation.

When paired with CrewAI, Fathom becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Fathom tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Meeting Orchestration — List recent meetings and search across your entire recording history to retrieve titles, dates, and participant metadata natively
AI Transcription — Retrieve full speaker-attributed transcripts with timestamps to review exact discussions and verbal commitments limitlessly
Contextual Summarization — Get AI-generated summaries distilling key discussion points, decisions, and overall meeting context into a concise format
Action Item Tracking — Extract AI-identified tasks with assigned owners and due dates to automate post-meeting follow-up workflows
Recording Management — Access video and audio recording URLs for immediate streaming or download bypassing the web interface
Attendee Auditing — List all meeting participants including join/leave times and speaking duration to verify engagement levels synchronously
Team Intelligence — Access meetings shared with your Fathom team to monitor cross-functional discussions and organizational knowledge securely
Highlight Navigation — Retrieve specific moments flagged as important during calls to focus on critical insights without reviewing entire recordings

The Fathom MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fathom to CrewAI via MCP

Follow these steps to integrate the Fathom MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Fathom

Why Use CrewAI with the Fathom MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Fathom through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Fathom + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Fathom MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Fathom for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Fathom, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Fathom tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Fathom against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Fathom MCP Tools for CrewAI (12)

These 12 tools become available when you connect Fathom to CrewAI via MCP:

get_action_items

Get AI-identified action items for a meeting

get_attendees

Get the list of participants for a meeting

get_highlights

Get important moments flagged in a meeting

get_me

Get current API token user profile

get_meeting

Get details for a specific Fathom meeting

get_recording

Get the recording URLs for a meeting

get_summary

Get the AI-generated summary for a meeting

get_team_meetings

List meetings shared with your team

get_transcript

Get the full transcript for a meeting

get_webhooks

List configured webhooks

list_meetings

List all Fathom meetings

search_meetings

Search for meetings by keyword

Example Prompts for Fathom in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Fathom immediately.

"Show me the summary and action items for my last meeting"

"Search my meetings for mentions of 'pricing strategy'"

"Get the transcript for meeting 'abc-123'"

Troubleshooting Fathom MCP Server with CrewAI

Common issues when connecting Fathom to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Fathom + CrewAI FAQ

Common questions about integrating Fathom MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.