---
name: mailslurp-connect
description: Connect MailSlurp or diagnose its MCP account, workspace, grant and entitlement before an infrastructure workflow.
---

Use the installed MailSlurp connection and its current advertised tools. Start with the advertised tool corresponding to `mailslurp.get_connection_diagnostics`; hosts may namespace its name. If this deployed server does not advertise it, use `mailslurp.get_agent_capabilities` for legacy messaging grants and explain that it does not establish infrastructure access. If authentication is required, use the host's Connect/sign-in flow. Keep credentials in that flow, never chat or ordinary tool arguments.

Confirm the intended workspace and choose only the permissions needed for the task on the MailSlurp consent screen. General infrastructure offers start unchecked; an explicitly scoped messaging request can retain its messaging defaults. A rendering-only connection needs no inbox selection, and SMS access stays tied to the explicitly selected phone numbers. Resource scope alone does not establish permission to read email. Do not create an Agent API worker merely to connect an AI client.

The diagnostic can select rendering, placement, warmup, sending or all. Its approved resources describe the grant, not current inventory. Read permission, write permission, account observations, API availability and execution flags are separate. Missing/failed observations are not zero balance. Included-credit units can mean complete renders or client targets; preserve the returned unit. Zero included credits or ineligibility for a new automatic add-on does not by itself prove an upgrade is required; an add-on may already exist. Provider/sender readiness, execution eligibility and monetary estimates remain unverified until the relevant authorized workflow checks them.

Explain observed missing access, unavailable features and entitlement separately; a subscription cannot expand an authorization grant. A source catalog or product page does not establish that a deployed connection exposes a tool. Use only advertised tools and supported arguments.

Connection diagnosis is observational: do not allocate resources or retrieve message bodies, codes or attachments merely to test setup. For separately authorized product work, respect the operation's usage bounds and host policy; normal MailSlurp billing, plan activation and add-on rules remain in force. Do not replace a missing tool with undocumented HTTP calls.

Successful diagnosis identifies the intended account, available actions and any remaining prerequisite. Save existing job and operation IDs before continuing a workflow after reconnecting.