otherapi_key

Userlist

Userlist is a full-stack email automation platform designed for SaaS companies, enabling targeted behavior-based campaigns through email and in-app messages.

Verdict

The Userlist MCP lets your team manage customer data in Userlist directly from Switchy. By @mentioning Userlist in a Space, you can create or update user-company relationships and remove companies when accounts close or data needs cleaning. This is most useful for customer success and ops teams who need to sync account changes without leaving their AI workspace. The MCP requires an API key with write permissions, so you'll want to limit access to team members who handle customer records. It doesn't support reading data or querying relationships — only writes and deletes.

Common use cases

  • Link new users to their company accounts
  • Remove churned companies from customer database
  • Update account ownership after sales handoffs
  • Clean up duplicate company records in bulk

Integration

Vendor
Userlist
Category
other
Auth
API_KEY
Tools
2
Composio slug
userlist

Tools

  • Delete Company from Userlist
    destructive

    Tool to delete a company from userlist. use when you need to remove a company by its unique identifier after verifying it.

  • Push User-Company Relationship

    Tool to create or update a relationship between a user and a company in userlist. use after confirming valid user and company identifiers.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Userlist from the list. 3. In a separate tab, log into your Userlist account and go to Settings > API Keys. 4. Generate a new API key with write permissions for companies and relationships. 5. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 6. Switchy will verify the key and confirm the connection. 7. Open any Space and type '@Userlist' to see available tools in the autocomplete menu. 8. Test the connection by asking '@Userlist to show me what tools you have' — you should see options to push relationships and delete companies. 9. Grant the integration to specific Spaces where your team manages customer data.

What teammates see: by default, memories from Userlist are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Spaces have used this MCP together with a given model.

How Switchy teams use it

Not enough Spaces yet to publish anonymised usage stats (we require ≥ 50 Spaces per week).

Starter prompts

Remove Closed Account

@Userlist delete company comp_xyz789 from our records. This account closed last week and we've confirmed no active users remain.
Open in a Space →

Bulk Relationship Updates

@Userlist I have five users who switched companies. Here are the user IDs and their new company IDs. Push each relationship with role set to member.
Open in a Space →

Cleanup Duplicate Companies

@Userlist we have duplicate entries for Acme Corp. Keep comp_abc123 and delete comp_def456 and comp_ghi789.
Open in a Space →

Onboarding Sync

@Userlist three new users just signed up for company comp_xyz789. Create relationships for usr_111, usr_222, and usr_333 with role set to member.
Open in a Space →

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@userlist show me all relationships for user ID usr_abc123 and explain which companies they're associated with

Output

Based on the available tools, I can help manage user-company relationships in Userlist, but I don't have a direct tool to retrieve existing relationships. However, I can create or update relationships using the Push User-Company Relationship tool if you provide both a user ID and company ID. To view existing relationships, you may need to access your Userlist dashboard directly or use their API's GET endpoints outside this integration.

Notes

This example reveals a key limitation: the MCP provides write operations (push relationships, delete companies) but lacks read/query tools. Users expecting to search or list relationships will need to rely on Userlist's web interface or separate API calls for discovery workflows.

Prompt

@userlist link user usr_def456 to company com_xyz789 with role 'admin' and set them as the billing contact

Output

I've pushed the relationship between user usr_def456 and company com_xyz789 to Userlist. The relationship has been created with the specified attributes (role: admin, billing contact designation). This operation either created a new relationship or updated an existing one if this user-company pair was already linked. You can verify the relationship details in your Userlist dashboard under the company's user list.

Notes

This write operation is idempotent—running it multiple times won't create duplicates. The tool requires valid user and company identifiers that already exist in Userlist; it won't create new users or companies. Ensure your API key has write permissions for relationship management.

Prompt

@userlist we're offboarding Acme Corp—delete company com_acme999 and confirm it's removed from all tracking

Output

I've deleted company com_acme999 from Userlist. This action permanently removes the company record and all associated relationships with users. Note that this is a destructive operation that cannot be undone through this integration. The company's historical event data may still exist in Userlist's analytics depending on your retention settings, but the company entity itself is no longer active for segmentation or messaging.

Notes

Deletion is immediate and irreversible via this MCP. The tool doesn't return confirmation of what was deleted (user count, relationship count), so verify the company ID carefully before executing. Consider exporting company data first if you need an audit trail of what existed before deletion.

Use-case deep-dives

SaaS onboarding cleanup after trial churn

When to automate Userlist company deletion for trial dropoffs

A 6-person SaaS team runs weekly trial cohorts and needs to keep their Userlist workspace clean without manual CSV exports. The Delete Company tool works if you're removing fewer than 50 companies per week and have a reliable source of truth (like a CRM webhook or Stripe event) that triggers the deletion. The Push User-Company Relationship tool lets you reassign accounts when a trial converts and a new admin takes over. This MCP is the right call if your team already uses Userlist for lifecycle emails and you want to close the loop on churn without logging into the dashboard. If you're deleting hundreds of companies daily or need bulk operations, you'll hit rate limits fast—at that scale, use Userlist's batch API directly instead of this MCP.

Customer success handoff tracking

Using this MCP to sync account ownership changes in real time

A 12-person B2B support team needs to update Userlist when a customer moves from sales to CS, or when an enterprise account adds a new subsidiary. The Push User-Company Relationship tool handles this if the handoff happens fewer than 20 times per day and you're working from a single source like HubSpot or Salesforce. The MCP requires you to already know the user and company identifiers—it won't search or validate them for you, so your workflow needs a lookup step first. This setup wins when your team is in Slack or a shared AI workspace and can trigger the sync without opening Userlist's UI. If your org structure changes constantly or you're managing thousands of relationships, the two-tool limit here becomes a bottleneck—you'll want a dedicated integration platform instead.

Post-acquisition account consolidation

When this MCP helps merge user-company data after M&A

A 4-person ops team just acquired a competitor and needs to consolidate 200 customer accounts into their Userlist instance over two weeks. The Push User-Company Relationship tool can create the new mappings one at a time, and the Delete Company tool can remove duplicates after verifying the merge. This MCP is practical if you're doing the consolidation in batches during standups and want to avoid context-switching between your project tracker and Userlist's dashboard. The API key auth means anyone on the team can run the tools without sharing credentials. The trade-off: with only two tools and no bulk operations, this approach works for mid-sized migrations but breaks down past 500 companies—at that volume, you'll spend more time waiting on API calls than you save by staying in one workspace.

Frequently asked

What does the Userlist MCP do in Switchy?

It lets your AI agents manage customer relationships in Userlist — creating or updating user-company links and deleting companies when needed. Useful for automating customer onboarding flows, cleaning up test accounts, or syncing CRM data without writing custom scripts. The MCP handles two core operations: pushing relationship records and removing company profiles.

Do I need admin access to connect Userlist?

You need a Userlist API key with write permissions. Userlist doesn't use OAuth — you generate the key in your workspace settings and paste it into Switchy. Anyone with access to that key can delete companies and modify relationships, so treat it like a database password. Don't share the connection with team members who shouldn't have delete rights.

Can the Userlist MCP read existing customer data?

No. This MCP only writes and deletes — it can't fetch lists of users, query company properties, or read relationship metadata. If you need to check whether a company exists before deleting it, you'll do that verification outside Switchy or use Userlist's main API separately. The MCP is for mutations, not queries.

Why use this instead of Userlist's API directly?

The MCP saves you from writing boilerplate HTTP requests and handling auth headers in every workflow. Your AI agent can say "delete company X" in natural language instead of you constructing a DELETE request with the right endpoint and token. Trade-off: you lose fine-grained control over error handling and response parsing that raw API calls give you.

Who on the team should connect Userlist to Switchy?

Whoever owns your customer data hygiene — usually a growth ops or customer success lead. Since the MCP can delete companies, don't hand the connection to junior team members running exploratory prompts. One shared connection works for the whole workspace; individual agents inherit access when they're granted permission to use the Userlist MCP.

Data last verified 607 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.