Mailsoftly

@Mailsoftly verify our API credentials and show me which firm account we're connected to

Authentication successful. Connected to firm account 'Acme Marketing Agency' (ID: firm_8x9k2m). Account tier: Professional. API access confirmed with full permissions for campaign management, contact lists, and analytics. Your current monthly send limit is 50,000 emails with 32,400 remaining this billing cycle.

This example shows the authentication tool's primary use case: confirming your API key works and understanding your account's scope before attempting campaign operations. Note that this MCP currently exposes only one tool — authentication verification — so workflow capabilities beyond credential validation require additional tooling or manual steps.

@Mailsoftly check if our credentials are still valid and tell me our account status before I start the campaign workflow

Credentials validated. Firm 'Riverside Consulting' (ID: firm_3j7n1p) is active. Account type: Enterprise. All API permissions active. Your account shows 125,000 monthly email quota with 89,200 sends available. Last authentication refresh was 14 minutes ago, token remains valid for 23 hours 46 minutes.

Demonstrates using authentication as a pre-flight check in automated workflows. This is particularly useful in Spaces where multiple team members trigger email operations — verifying credentials upfront prevents mid-workflow auth failures. The single-tool limitation means you'll need to pair this MCP with other integrations or manual steps for actual campaign execution.

@Mailsoftly authenticate and summarize what access level our API key provides for this firm account

Authentication complete for firm 'Blueprint Design Co.' (ID: firm_5k2w8r). Your API key grants Standard tier access. Permissions include: contact list management, template creation, campaign scheduling, and basic analytics. Restrictions: no access to A/B testing features or advanced segmentation (Enterprise-only). Monthly send capacity: 25,000 emails, currently at 18,300 remaining.

Shows how the authentication response reveals permission boundaries and tier-specific limitations. This is critical context before planning campaigns — you'll know immediately if your desired workflow requires account upgrades. Since this MCP only handles authentication, actual email operations happen outside Switchy or through complementary integrations.

When you need a single-step auth check before bulk email work

A 3-person ops team setting up Mailsoftly for the first time needs to confirm their API key works before they build automations around it. This MCP is the right call if you're doing that check inside Switchy's workspace instead of switching to Mailsoftly's dashboard. The single tool validates credentials and pulls firm details in one shot, which is enough for a setup checklist or a pre-flight script. The trade-off: this MCP stops at authentication. If your workflow involves sending campaigns, managing lists, or pulling analytics, you'll hit the wall immediately after the credential check passes. Use this when you're scripting an onboarding flow or debugging API access, not when you're running day-to-day email operations.

Useful for auditing which client accounts are still active

A 6-person agency manages Mailsoftly accounts for 15 clients and needs to audit which API keys are still valid and which firms they map to. This MCP works for that audit if you're running it as a one-time sweep or a monthly check. The tool returns firm details alongside the validation result, so you can build a spreadsheet of active accounts without logging into each client's Mailsoftly dashboard. The boundary: this is a read-only health check. If the audit reveals expired keys or wrong firm mappings, you'll need to fix those problems outside Switchy. Use this when you're inventorying credentials across multiple tenants, not when you're actively managing email campaigns for those clients.

Fast path for support teams diagnosing customer API issues

A 2-person support team fields tickets from customers who can't connect their Mailsoftly account to a third-party tool. This MCP is the right call when the support agent needs to test the customer's API key and see which firm it belongs to without asking the customer to screenshot their dashboard. The single tool gives you a pass/fail result and the firm name in under 5 seconds, which is enough to close 80% of credential tickets on first reply. The limit: if the key validates but the customer still can't send mail, the MCP won't help you debug permissions, rate limits, or downstream integration failures. Use this for first-line triage when the symptom is 'my API key doesn't work', not for deep-dive debugging of Mailsoftly's email delivery pipeline.