Modem
Modem turns customer conversations into structured topics, people, and company insights for analysis and workflow automation.
Verdict
Common use cases
- Verify account VIP status before a sales call
- Pull customer message history during support triage
- Create contact records from inbound leads
- Check weekly activity trends for renewal planning
- Link external platform IDs to unified profiles
Integration
- Vendor
- Modem
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 30
- Composio slug
modem
Tools
- Add People to Company
Associate one or more existing people with an existing company. People already associated with the company are reported as skipped. This changes company membership, and the approved API surface has no inverse removal operation.
- Create Companies
Create one to 50 companies in one batch. Each item succeeds or fails independently; use a one-item array to create one company.
- Create People
Create one to 50 people in one batch. Each item succeeds or fails independently; use a one-item array to create one person.
- Get Channel
Get one channel's source details, connection state, context, timestamps, and message count by UUID.
- Get Company
Get one company's core details, connection values, domain, logo, and VIP status by decimal ID.
- Get Company Activity
Get one company's message count, weekly activity series, and source-level message breakdown.
- Get Company History
Get up to 50 company audit records plus merge history. The API reports the total audit count but exposes no cursor or page parameter, so this tool cannot retrieve records beyond the requested limit.
- Get Company Identities
Get external platform identities linked to one company by Modem's identify operation.
- Get Current Organization
Return the organization selected by the connected API key. Use this as an authentication smoke test and to confirm the active tenant; it returns no member, credential, or plan details.
- Get Person
Get one person's complete profile, including company, connections, tags, sources, timestamps, identities, and message activity aggregates.
- Get Person History
Get up to 50 person audit records plus merge history. The API reports the total audit count but exposes no cursor or page parameter, so this tool cannot retrieve records beyond the requested limit.
- Get Person Identities
Get all external platform identities linked to one person.
- Get Person Source Stats
Get one person's message counts broken down by source platform.
- Get Topic
Get one topic's complete details, including its summary, classification, lifecycle, priority, keywords, time range, archive state, and event count.
- Get Topic Groups
Get every message group assigned to one topic in ascending or descending group-time order. Modem does not paginate or limit this endpoint, so topics with many deeply nested messages can return a large response.
- Get Topic History
Get up to 50 topic audit records plus action and merge history. The API reports the total audit count but exposes no cursor or page parameter, so this tool cannot retrieve audit records beyond the requested limit.
- Get Topic People
Get every unique person who participated in one topic, including source identities, company, profile, VIP state, and contribution count.
- Identify External Records
Upsert links from external platform records to Modem people and companies in batches of 50. Modem matches platform identities before natural keys, can create records only from the documented creation fields, links resolved memberships, and
- List and Search Topics
List or search topics by keywords or semantic meaning with organization, participant, source, status, date, and classification filters, one page at a time. Semantic search takes precedence when both search modes are supplied.
- List Channels
List organization channels with connection state and message counts, optionally filtered by source, name, or channel IDs.
- List Companies
List companies with person and message aggregates, optionally searching and sorting the result. Returns one page and an opaque continuation cursor.
- List Groups
List message groups for exactly one company or one person, returning compact message content and topic context one page at a time.
- List People
List people with aggregated message statistics, optionally filtering by search text, ecosystem tags, or company and sorting the result. Returns one page and an opaque continuation cursor.
- Merge Companies Irreversibly
Irreversibly merge one or more source companies into one surviving target. All domains, person associations, and Slack workspaces move to the target, and source records cannot be restored by this API. Requires explicit confirm_irreversible=
- Merge People Irreversibly
Irreversibly merge one or more source people into one surviving target. All identities, emails, and company associations move to the target, and source records cannot be restored by this API. Requires explicit confirm_irreversible=true. Sup
- Merge Topics Irreversibly
Irreversibly merge 1 to 50 source topics into one surviving target. Modem archives and marks every source as merged, then copies their group and event associations to the target; this API cannot undo the merge. Requires explicit confirm_irr
- Update Companies
Update one to 50 companies in one batch. Omitted fields remain unchanged, explicit null values clear nullable fields, and each item reports success independently.
- Update People
Update one to 50 people in one batch. Omitted fields remain unchanged, explicit null values clear nullable fields, and each item reports success independently.
- Update Topic
Update one topic's priority, lifecycle, issue type, complete keyword list, or archive state. Omitted fields remain unchanged; issue_type=null clears the classification.
- Update Topics
Set priority or archive state for one to 100 topics at once. Provide at least one change, use archived=false to unarchive, and provide an archive reason only with archived=true.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Modem from the developer tools category. 3. Log in to your Modem dashboard, navigate to Settings > API Keys, and generate a new key with read and write permissions. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Switchy will validate the key and confirm the connection within a few seconds. 6. Open any Project, type '@Modem get company' followed by a company ID, and send the message to test retrieval. 7. If the MCP returns company details, the integration is live and ready for your team to use across all Projects.
What teammates see: by default, memories from Modem are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Lookup Customer Profile
@Modem get company details for ID 12345. Show me the domain, logo URL, VIP status, and any linked connection values.
Review Recent Activity
@Modem get company activity for ID 67890. Break down message volume by source and show the last four weeks of activity.
Create Contact Batch
@Modem create people from this list: Alice (alice@example.com), Bob (bob@example.com), Carol (carol@example.com). Return success or failure for each.
Associate People to Account
@Modem add people IDs 101, 102, and 103 to company ID 12345. Report which associations succeeded and which were skipped.
Audit Company Changes
@Modem get company history for ID 12345. Show me the most recent audit events and any merge operations in the log.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@modem show me the activity breakdown for Acme Corp over the last 4 weeks, including which channels they're most active in
Acme Corp (ID 4521) has sent 347 messages in the last 28 days. Weekly breakdown: Week 1: 82 messages, Week 2: 91 messages, Week 3: 89 messages, Week 4: 85 messages. Source-level activity: Slack (201 messages, 58%), Email (89 messages, 26%), In-app chat (57 messages, 16%). The company is marked as VIP and has 12 associated people in Modem's directory.
This example uses Get Company Activity to surface engagement trends. The MCP returns message counts and source breakdowns but does not expose individual message content or timestamps. Useful for account health checks, but you'll need separate calls to drill into specific people or threads.
@modem create a new company record for "Globex Industries" with domain globex.io and mark them as VIP, then associate the three people we just imported
Created company "Globex Industries" (ID 8834) with domain globex.io and VIP status enabled. Successfully associated 3 people: Sarah Chen (ID 1205), Marcus Liu (ID 1206), and Priya Kapoor (ID 1207). All three people were already in Modem's directory and are now linked to this company. No people were skipped.
This example chains Create Companies with Add People to Company. Both operations are batch-capable (up to 50 items), and each item succeeds or fails independently. If a person is already associated with the company, Modem reports them as skipped rather than erroring. Requires write scope on your API key.
@modem pull the audit history for company ID 3401 and summarize any recent merges or major changes in the last 30 days
Retrieved 50 audit records for company ID 3401 (Modem's API limit). Recent activity: On March 10, company "Initech LLC" (ID 2987) was merged into this record, consolidating 8 people and 142 messages. On March 15, the company domain was updated from initech.com to initech.io. On March 18, VIP status was enabled. No other structural changes detected in the visible history. Note: Modem reports 127 total audit records exist, but the API does not support pagination beyond the first 50.
This example uses Get Company History to surface merge events and field changes. The 50-record limit is a hard API constraint — if a company has extensive history, older records are invisible to this MCP. Best for recent activity checks, not exhaustive compliance audits.
Use-case deep-dives
When Modem wins for AE-to-CSM account transitions
A 6-person sales team closing 15-20 deals a month needs CSMs to inherit full context without Slack archaeology. Modem's Get Company Activity and Get Company History tools surface message volume, weekly engagement trends, and audit trails in one call—so the CSM sees which channels lit up during the trial and who the champion was. This works when your CRM already tracks deal stage but can't pull conversational signal from support or product channels. If your team closes fewer than 10 deals a month, the manual handoff doc is faster. If you're over 50 deals, you need a dedicated rev-ops automation, not an MCP. Use Modem when the handoff happens often enough to hurt but not so often you've built custom tooling.
When message-count trends predict churn risk
A 4-person support team managing 80 accounts wants early warning when a customer goes quiet. Modem's Get Company Activity returns weekly message series and source-level breakdowns, so you spot the drop from 12 messages a week to zero before the renewal conversation. The Create People and Add People to Company tools let you tag new stakeholders as they appear in channels, keeping the contact graph current. This scenario breaks down if your product has low touch-point frequency—SaaS tools with monthly check-ins don't generate enough signal. It also fails if you need sentiment analysis; Modem gives you volume and recency, not tone. Use this when message cadence is your leading churn indicator and you have under 200 accounts.
When Get Company Identities connects your integration partners
A 10-person partnerships team onboarding 30 integration vendors needs to see which Slack channels, GitHub orgs, and Zendesk tickets link to each partner company. Modem's Get Company Identities and Get Channel tools surface external platform IDs and connection states, so you know if the partner's eng team is active in your shared channel or went dark three weeks ago. The 30-tool surface handles batch company creation when you're importing a new cohort from a partnership tier. This works when your partner count is under 100 and you're managing relationships in multiple tools. Over 100 partners, you need a PRM with native integrations. Under 20, a shared spreadsheet is honest enough. Use Modem when you're in the middle zone and relationship health lives in message patterns.
Frequently asked
What does the Modem MCP let me do in Switchy?
The Modem MCP connects Switchy to your Modem customer data platform. You can create and update people and companies, retrieve channel details, pull activity metrics, and query company history — all without leaving your AI workspace. It's useful for teams that manage customer context in Modem and want to surface that data during conversations or workflows in Switchy.
Do I need admin access to connect Modem?
You need a Modem API key with sufficient permissions to call the endpoints you plan to use. Modem uses API_KEY authentication, so whoever generates the key controls which operations are allowed. Check with your Modem admin to confirm the key has access to companies, people, channels, and activity endpoints if you want full functionality in Switchy.
Can the Modem MCP retrieve more than 50 audit records for a company?
No. The Get Company History tool returns up to 50 audit records and has no pagination or cursor parameter, so you cannot fetch older records beyond that limit. If you need a complete audit trail, you'll have to query Modem's API directly or export the data from Modem's dashboard.
How is this different from calling Modem's API myself?
The MCP wraps Modem's REST API so you can query and update customer data in natural language inside Switchy, without writing code or switching tabs. If you already have scripts that call Modem, keep using them for scheduled jobs. Use the MCP when you want ad-hoc lookups or updates during a conversation with your team.
Who on my team should connect the Modem integration?
Whoever manages your Modem workspace and can generate an API key with the right scopes. Typically that's a customer success ops lead or a product manager who owns your CRM setup. Once connected, anyone in your Switchy workspace can invoke the Modem tools, so make sure your team understands what data they're querying.