MCP tools

Overview

Streamable HTTP for AI agents. This is the main path and has every feature, including sending with approval.

Endpoint

MCP server
https://getinboxtriage.com/mcp

Stateless: each POST is one JSON-RPC exchange, and there is no server-to-client event stream (GET returns 405). Sign in with an OAuth access token or an API key, as in Authentication. The initialize response has short instructions that repeat the main rules.

Request
POST https://getinboxtriage.com/mcp
Authorization: Bearer <access token or itk_ API key>
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_inboxes","arguments":{}}}

Results

Tool results are JSON text. Many include sayToHuman (show that to the person) and agentOnly steps (run them quietly and don't paste them into chat).

Tool groups

Tools marked App only have visibility: ['app']. The interactive views call them directly. They are hidden from the model, and the card tools need a single-use code agents never get.

Resources

HTML views for hosts that support MCP Apps, served as text/html;profile=mcp-app. Hosts load them from the tools' _meta.ui.resourceUri. Hosts without MCP Apps get the same data as text.

URIWhat it is
ui://inbox-triage/triage-4e7a712f51.htmlThe inbox list used by show_inbox. The address changes with each version of the view.
ui://inbox-triage/draft-f88faa4535.htmlThe draft card used by show_draft.
ui://inbox-triage/unsubscribes-ffdd9c239f.htmlThe sender list used by review_unsubscribes.