Mailosaur MCP integration for AI agents.
Connect AI agents to Mailosaur through 12 structured actions, including get message, create server, and delete all messages. Review authentication, inputs, w…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Mailosaur integration exposes
The Mailosaur Agent App exposes 12 provider-backed actions for communication and developer tools work. Its current contract lets an authorized agent retrieve one mailosaur message by id, including parsed body content, create a new mailosaur inbox server, and delete all mailosaur messages stored in one server. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Mailosaur account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Mailosaur capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_messageREADRetrieve one Mailosaur message by ID, including parsed body content.
INPUTS: id
create_serverWRITECreate a new Mailosaur inbox server.
INPUTS: name
delete_all_messagesHIGH IMPACTDelete all Mailosaur messages stored in one server.
INPUTS: server
delete_messageHIGH IMPACTDelete one Mailosaur message and its attachments.
INPUTS: id
delete_serverHIGH IMPACTDelete one Mailosaur inbox server and its stored messages.
INPUTS: id
get_serverREADRetrieve one Mailosaur inbox server by ID.
INPUTS: id
get_usage_limitsREADRetrieve Mailosaur account usage limits.
list_messagesREADList Mailosaur message summaries from one server.
INPUTS: server / receivedAfter / page / itemsPerPage / dir
list_serversREADList Mailosaur inbox servers in the current account.
list_usage_transactionsREADList the last 31 days of Mailosaur usage transactions.
search_messagesREADSearch Mailosaur message summaries in one server.
INPUTS: server / receivedAfter / page / itemsPerPage / dir
update_serverWRITEUpdate the name of one Mailosaur inbox server.
INPUTS: id / name
INPUT CONTRACTS
Know what the action needs before it runs.
get_message
idOPTIONAL- The identifier of the Mailosaur message.
create_server
nameOPTIONAL- The name of the server.
delete_all_messages
serverOPTIONAL- The identifier of the Mailosaur server.
delete_message
idOPTIONAL- The identifier of the Mailosaur message.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Message
Retrieve one Mailosaur message by ID, including parsed body content. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_messageControl Create Server
Create a new Mailosaur inbox server. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_serverVerify with Get Server
Retrieve one Mailosaur inbox server by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_serverSAFETY BOUNDARY
Operate Mailosaur with explicit limits
- Authorize Mailosaur with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_all_messages`, `delete_message`, and `delete_server` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Mailosaur rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Mailosaur task completed successfully.
CONNECTION MODEL
API key
Mailosaur API key used as the HTTP Basic auth password with username api. Create or manage API keys in the Mailosaur Dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Mailosaur.