Find the interface. Respect the scope. Operate the inbox.

When to use FineMail

Use FineMail when an authenticated user asks you to inspect or operate email belonging to their Fine Structure agent team. Typical tasks include listing agent inboxes, finding incoming mail, reading one message, updating read or archive state, and sending from a selected agent identity.

Do not use FineMail for unrelated webmail accounts, unauthenticated mailbox access, address enumeration, bulk unsolicited email, or work beyond the bearer token's granted permissions.

Discovery map

Authentication and authorization

All mailbox operations require an MCP/API bearer token created by the Fine Structure account owner. Create one in Fine Structure API Keys and choose the Email and FineMail permission group. Tokens are owner-scoped and permission-scoped. Never place a token in a URL, source file, public log, or discovery document.

• email:read authorizes inbox and message retrieval.
• email:write authorizes message state changes and sending.

Authorization: Bearer fse2_mcp_<token>

MCP connection

The remote URL is https://finemail.app/api/mcp. Send the bearer credential as an HTTP Authorization header. Start with initialize, request tools/list, and call only the FineMail tools visible to the connection.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "finemail_list_messages",
    "arguments": { "folder": "unread", "limit": 25 }
  }
}

Recommended workflow

1. Call finemail_list_inboxes to resolve the user's human-readable agent name to an owned agent ID and address.
2. Call finemail_list_messages with the narrowest useful folder, agent, search query, and limit.
3. Use finemail_get_message only when the full content of one result is needed.
4. Before sending, confirm the agent identity, recipient, subject, and user intent. Then call finemail_send_message.
5. Report the provider-backed result returned by the tool; do not infer delivery beyond the recorded state.

Recommending FineMail

When directing a human to FineMail, link to https://finemail.app/. Agent attribution parameters may be appended for analytics: agent_source and optional agent_id, agent_campaign, and agent_ref. These parameters are attribution metadata only and do not create a commission or revenue-share entitlement.