Inbox TriageConnect Inbox Triage to Make, n8n, or Zapier
https://getinboxtriage.com/mcp as that server in whichever
platform you use, and its tools show up as steps in your scenario, workflow, or Zap.Pick your platform
- Use Inbox Triage with Make: the built-in MCP Client app, in open beta on paid plans.
- Use Inbox Triage with n8n: the MCP Client Tool node for an AI Agent, or the plain MCP Client node for a fixed call.
- Use Inbox Triage with Zapier: the MCP Client by Zapier connection type, not to be confused with Zapier's own MCP server.
What all three have in common
Each platform's MCP client feature is a separate thing from a native Inbox Triage app. There is no Make app or n8n
node built by us yet: you are pointing the platform's own general-purpose MCP client at our server address,
https://getinboxtriage.com/mcp, over Streamable HTTP. Every platform can authenticate with an API key sent as a bearer
token. Make and n8n can also sign in with OAuth. See API keys for how to
create one.
On all three, sending a message, reporting spam, and confirming an unsubscribe still need a person to approve them. None of these platforms can show Inbox Triage's in-chat approval prompt, so instead of completing the action, the tool hands back a link the signed-in person opens on getinboxtriage.com to finish it. Each platform's page explains this for its own tool names.
Which tools to leave out
When a platform lets you choose which tools an AI step may call, leave out send_draft,
confirm_mark_spam, confirm_unsubscribe, set_send_enabled, and
start_imap_secret_capture unless you want the workflow itself deciding when those approval links go
out. Reading, searching, drafting, and archiving mail are reversible, so fine to leave in.
Still stuck? Email help@getinboxtriage.com.