AgentMail (QQ) MCP integration for AI agents.
Connect AI agents to AgentMail (QQ) through 5 structured actions, including list aliases, send message, and delete message. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 5
- 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 AgentMail (QQ) integration exposes
The AgentMail (QQ) Agent App exposes 5 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent list the current user's agentmail aliases and account limits, send a new message. when confirmation_token is omitted, the first phase returns a confirmation token; the action automatically completes the second phase, and move a message to trash (soft delete), automatically completing the provider confirmation flow. 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 AgentMail (QQ) account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AgentMail (QQ) capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_aliasesREADList the current user's AgentMail aliases and account limits.
send_messageWRITESend a new message. When confirmation_token is omitted, the first phase returns a confirmation token; the action automatically completes the second phase.
INPUTS: alias_id / to / cc / bcc / subject
delete_messageHIGH IMPACTMove a message to trash (soft delete), automatically completing the provider confirmation flow.
INPUTS: alias_id / message_id
list_messagesREADList or search messages in an alias mailbox.
INPUTS: alias_id / q / dir / limit / cursor
read_messageREADRead a single message including body and attachments.
INPUTS: alias_id / message_id
INPUT CONTRACTS
Know what the action needs before it runs.
send_message
alias_idREQUIRED- The alias identifier to send from.
toREQUIRED- Recipient email addresses.
ccOPTIONAL- CC recipient email addresses.
bccOPTIONAL- BCC recipient email addresses.
subjectREQUIRED- The message subject.
delete_message
alias_idREQUIRED- The alias identifier that owns the message.
message_idREQUIRED- The message identifier.
list_messages
alias_idREQUIRED- The alias identifier to use as the mailbox.
qOPTIONAL- Full-text search query. When provided, the search endpoint is used.
dirOPTIONAL- Mailbox folder.
limitOPTIONAL- Maximum messages to return (max 50).
cursorOPTIONAL- Pagination cursor from a previous response.
read_message
alias_idREQUIRED- The alias identifier that owns the message.
message_idREQUIRED- The message identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Aliases
List the current user's AgentMail aliases and account limits. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_aliasesControl Send Message
Send a new message. When confirmation_token is omitted, the first phase returns a confirmation token; the action automatically completes the second phase. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
send_messageVerify with List Messages
List or search messages in an alias mailbox. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_messagesSAFETY BOUNDARY
Operate AgentMail (QQ) with explicit limits
- Authorize AgentMail (QQ) with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_message` 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 AgentMail (QQ) rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AgentMail (QQ) task completed successfully.
CONNECTION MODEL
API key
AgentMail OAuth access token used with the Authorization Bearer header. Get one by running `agently-cli auth login` or completing the OAuth device flow.
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
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- 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 AgentMail (QQ).