Attio Activity MCP Server

Attio Activity

Communication and meeting activity linked to CRM records. Three data types: email threads scoped to records, call recordings with timestamped transcripts, and calendar meetings with participant tracking.

Capability areas

Email threads

• List threads — retrieve conversation threads attached to a specific record. Requires object slug (e.g. "people", "companies") and record_id. Optionally filter to a specific list entry with entry_id + list slug. Paginate with limit (max 100) and offset.
• Get thread — fetch a single thread by ID with all its messages.

Call recordings

• List recordings — retrieve recordings for a specific meeting by meeting_id. Each recording has a status: processing, completed, or failed. Includes web URLs for playback.
• Get recording — fetch a single recording by meeting_id + call_recording_id.
• Get transcript — retrieve the timestamped transcript for a recording. Returns speech segments with speaker names, spoken text, and start/end times in seconds.

Meetings

• List meetings — browse meetings with rich filtering: by linked record (linked_object + linked_record_id), by participant email, or by date range (ends_from + starts_before). Sort by start_asc or start_desc.
• Get meeting — fetch full meeting details including title, description, participants, and linked CRM records.
• Find or create meeting — idempotent upsert. If a calendar_url matches an existing meeting, returns it; otherwise creates a new one. Requires title, start (datetime + timezone), and end.

Workflows

• Call review: list meetings for a record → list call recordings for a meeting → get the transcript to review what was discussed.
• Activity timeline: list threads + list meetings for a person or company record to build a full communication timeline.
• Meeting sync: use find-or-create with calendar_url to deduplicate calendar imports into Attio.

Gotchas

• Record scoping: threads require both object slug and record_id. Discover these from the CRM bundle first.
• Meeting → recording hierarchy: recordings are children of meetings. You need the meeting_id before you can access recordings or transcripts.
• Transcript availability: transcripts are only available when the recording status is "completed". Processing or failed recordings have no transcript.
• Date filters: meeting date filters use ISO 8601 datetime strings (e.g. "2026-03-01T00:00:00.000Z"), not YYYY-MM-DD dates.
• Read-heavy: most activity tools are read-only. The only write operation is find-or-create meeting.