Before you start
Check 3 things.
Access to Supertake and its current integration documentation.
Confirmation that Supertake accepts remote Streamable HTTP MCP servers with OAuth.
Access to the intended Mermail workspace.
← All integrationsSupertake and Mermail
SUPERTAKE
This connection requires custom remote MCP with Streamable HTTP and OAuth in your Supertake account.
Supertake and Mermail
connection requirements.
Use these MCP details when your Supertake account offers custom remote connectors.
Why Supertake
An inbox for your agent’s workflow.
Mermail provides a dedicated inbox for agent workflows. A connection from Supertake requires custom remote MCP support with Streamable HTTP and OAuth.
Mermail’s hosted MCP endpoint is available
OAuth sign-in is required for this endpoint
Streamable HTTP for remote MCP connections
A read-only mailbox check to test the connection
Visit Supertake
Success contract
Done when all 3 pass.
Supertake documents custom remote MCP and OAuth support.
Mermail OAuth finishes in the intended workspace, if supported.
list_mailboxes succeeds, if a connection is available.
Connection requirements.
1
Check your account’s connector options
Check whether your Supertake account offers custom remote MCP connectors with OAuth.
Visit Supertake2
Keep the Mermail endpoint ready
If supported, use this endpoint and Supertake’s documented OAuth flow. No API-key header is needed.
MCP URL · OAuth required
https://console.mermail.app/mcp3
Test the connection
Once connected, ask Supertake to list your Mermail mailboxes before running other inbox tasks.
Verify
List my Mermail mailboxes using list_mailboxes.What does Supertake need to connect?
Your account needs custom remote MCP connectors with Streamable HTTP and OAuth. Check Supertake’s available options.
What if I cannot add a custom connector?
Ask Supertake about custom remote MCP access for your account before adding the Mermail endpoint.