Magnetic

@Magnetic show me all my follow-ups due in the next 7 days and group them by contact priority

Retrieved 14 upcoming follow-ups from your Magnetic account. High-priority contacts (8 follow-ups): 3 scheduled calls with enterprise prospects, 2 proposal reviews, 3 check-ins on pending deals. Medium-priority (4 follow-ups): quarterly touchpoints with existing clients. Low-priority (2 follow-ups): introductory emails to cold leads. All tasks include contact names, due dates, and associated grouping IDs for context.

This example demonstrates read-heavy retrieval combining the Get Current Follow-ups tool with AI synthesis to organize results by priority. Requires valid API key authentication. The MCP returns raw follow-up data; the AI infers priority from contact tags or grouping metadata if available in your Magnetic setup.

@Magnetic find the grouping for Acme Corp's Q1 renewal and add a task to schedule their kickoff call by Friday

Located grouping 'Acme Corp Q1 Renewal' (ID: grp_8x3k9m). Created new task 'Schedule Acme kickoff call' with due date March 15, assigned to you. Task linked to the renewal grouping and tagged with 'client-onboarding'. Confirmation: task ID tsk_2p7n4q now visible in your Magnetic dashboard under this grouping.

Showcases write capability by creating a task within an existing grouping. The MCP uses Get Magnetic Groupings to search, then creates the task via an implied write tool. Side-effect: this task immediately appears in your Magnetic account and may trigger notifications to team members watching the grouping.

@Magnetic pull all groupings tagged 'enterprise-deal' that are still in 'proposal' status and draft a summary of common blockers mentioned in task notes

Found 6 enterprise groupings in 'proposal' status. Common blockers across task notes: budget approval delays (mentioned in 4 groupings), security review requirements (3 groupings), multi-stakeholder sign-off processes (5 groupings). Two groupings cite procurement timelines extending into Q2. One grouping flagged legal redlines on data residency clauses. This synthesis suggests focusing enablement efforts on procurement acceleration and security documentation.

Combines Get Grouping Tags, Get Magnetic Groupings, and Get Magnetic Task to aggregate data, then applies AI reasoning to surface patterns. Accuracy depends on how consistently your team documents blockers in task notes. The MCP provides raw text; the AI extracts themes but cannot verify completeness of the underlying data.

When Magnetic wins for client pipeline handoffs

A 6-person creative agency uses Magnetic to track client opportunities and follow-ups. The Get Current Follow-ups and Get Magnetic Groupings tools let the team pull upcoming tasks and active deals into a shared Switchy workspace during Monday pipeline reviews. The API key auth means anyone on the team can query the same data without credential juggling. This works when your follow-up volume stays under 50 active tasks per week—beyond that, the tool set gets noisy because Magnetic doesn't expose filtering by assignee or date range in these endpoints. If your agency runs 20-30 concurrent opportunities and you need a single view of who's chasing what, Magnetic in Switchy closes that gap without adding another dashboard.

When contact tag retrieval justifies the integration

A 3-person account management team at a consulting firm uses Magnetic's contact tagging to segment clients by vertical and engagement tier. The Get Contact Tags tool surfaces those tags in Switchy so the team can audit tagging consistency during quarterly reviews without opening Magnetic's UI. The catch: you need the contact ID first, which means this workflow only makes sense if you're already pulling contact lists from another source or using Magnetic's search elsewhere. If your tagging schema has fewer than 10 tags total, the manual lookup overhead outweighs the automation benefit. This integration pays off when you're managing 100-plus contacts with multi-dimensional tagging and you need spot-checks on tag hygiene without context-switching.

When grouping metadata tools support onboarding workflows

A 4-person operations team at a SaaS company uses Magnetic groupings to track implementation projects. The Get Grouping Custom Field Definitions and Get Grouping Statuses tools let them document available fields and status options in Switchy during new-hire onboarding or process audits. This is a narrow use case: these tools retrieve schema metadata, not actual project data, so they're only valuable if your team frequently references field definitions or status lists outside Magnetic's interface. If your custom field setup changes less than once a quarter, the integration overhead isn't worth it. This wins when you're scaling intake processes and need a shared reference for what fields exist and what statuses mean, especially if multiple people are configuring Magnetic workflows.