# Your recorded meetings. The follow-up, drafted.

Source: https://corespeed.io/integrations/fathom

Connect Fathom, the AI meeting recorder, to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists your recorded meetings and reads their summaries, transcripts and action items, then drafts a follow-up or a weekly digest. It sees the meetings you recorded and those shared with your team, and it edits no recording.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Fathom after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Skip the replay. Send the follow-up

Ask your agent for a meeting's summary and action items, then a follow-up draft you can review before it goes anywhere.

You ask your agent: "Find yesterday's Lakeside kickoff in Fathom. Read the summary and action items, and draft a follow-up email that lists each item with its owner. Do not send it."

It calls CoreSpeed:

- `fathom__list_meetings`: ok, 447 ms
- `fathom__get_recording_summary`: ok, 362 ms

It reads from: Fathom.

### Follow-up draft: Lakeside kickoff, next steps.

We start with the data plan. Three action items came out of the call; one still needs an owner.

**Action items**

- Reid shares the access list.
- Mira drafts the data plan.
- The revised timeline needs an owner before Friday.

_Illustrative example · Fictional meeting · Draft only, nothing sent_

All connectors: https://corespeed.io/docs/connectors

## From the call to what happens next

Requests you can make once Fathom is connected. The data is fictional.

### Find this week's meetings

This week · recordings · Recorded meetings

- Recorded: 4 meetings
- Shared: 2 from your team
- From the meetings your key can see

### Collect the action items

Lakeside kickoff · Action items

- Items: 3, two with an owner
- Needs an owner: Send the revised timeline
- From the meeting summary

### Keep the decision for every agent

Shared memory · Fathom + memory

- Decision: Lakeside starts with the data plan
- Saved by: Your agent, shared with the team
- With CoreSpeed memory

Full example: https://corespeed.io/solutions/agent-memory (Markdown: https://corespeed.io/solutions/agent-memory.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Fathom**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Is this Fathom the meeting recorder or Fathom Analytics?

The meeting recorder at fathom.ai. Fathom Analytics, the website analytics tool, is a different product.

### Which meetings can the agent read?

The meetings recorded by the Fathom user who created the API key, plus meetings shared with that user's team.

### Does the agent change or delete recordings?

No. The Fathom tools read meetings, summaries and transcripts. They can also manage new-meeting webhooks, which is a separate call.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/fathom

## Related pages

- [Agent memory across chats and clients](https://corespeed.io/solutions/agent-memory): Keep preferences, project decisions, and shared team context in persistent memory across Claude Code, Codex, and Cursor.
- [Cal.com for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/cal): See your Cal.com bookings and availability inside your agent. Booking or cancelling a slot stays a separate, visible step.
- [Calendly for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/calendly): See your Calendly events and invitees inside your agent, and prepare for the day's calls. Cancelling stays a separate step.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Fathom API documentation: https://developers.fathom.ai/

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)