Productivity

finemail.app

Provides AI-agent email management, allowing users to list inboxes, read, send, and manage messages.

1 endpoint38 known toolsFirst detected August 1, 2026Last detected September 15, 2026

ENDPOINT 1

https://finemail.app/api/mcp

No auth detected

MCP server metadata

Name: finemail-mcp
Version: 1.0.0

Capabilities

tools

Server instructions

FineMail gives AI agents their own real email inboxes on the connected account: read messages and threads, send, reply and forward, manage drafts, and administer inbox addresses, custom domains, webhooks and security rules. The mail is real, the addresses are real, and anything sent reaches an actual person. Orientation: call finemail_get_configuration once at the start of a session to see what the account already has, then finemail_list_inboxes. finemail_check_address_availability before finemail_create_inbox, because an address that is taken fails at creation rather than at check time. Reading: finemail_list_messages and finemail_list_threads for the overview, finemail_get_message and finemail_get_thread for the content, finemail_get_attachment for files. finemail_wait_for_email blocks until a message arrives, which is what makes verification codes and confirmation flows workable inside one conversation. Sending, and this is the part to be careful with: every send reaches a real inbox belonging to a real person, and it cannot be recalled. Show the user the recipient, the subject and the body and get an explicit yes before calling finemail_send_message, finemail_reply_message or finemail_forward_message. When there is any doubt, use finemail_create_draft and finemail_send_draft as two separate steps so the user reads the draft first. Never send to a list of addresses the user did not name. Domains and delivery: finemail_create_domain then finemail_verify_domain to send from an address the user owns. finemail_list_security_rules and finemail_create_security_rule control what is accepted inbound. finemail_get_usage reports the account's sending volume. Scope: FineMail handles the mailbox, not the application that produces the mail. If a user needs the form, app or database behind the messages, that is Fine Structure, the same publisher's separate platform.

Known tools 38

finemail_list_inboxes

List the authenticated user's AI-agent inboxes, their FineMail addresses, and mailbox counts.

Inferred read-only

finemail_list_messages

List owner-scoped FineMail messages, optionally filtered by agent, folder, or search text.

Inferred read-only

finemail_get_message

Get one full incoming or outgoing FineMail message owned by the authenticated user.

Potential side effects

finemail_send_message

Send a rich RFC email from an owned AI agent identity and persist its delivery record.

Potential side effects

finemail_mark_read

Mark an owner-scoped FineMail message as read or unread.

Potential side effects

finemail_archive_message

Archive or restore an owner-scoped FineMail message.

Potential side effects

finemail_check_address_availability

Validate a requested @finemail.app address and check whether it is globally available.

Inferred read-only

finemail_get_configuration

Read FineMail domain, sending, inbound-routing, and readiness configuration without exposing credentials.

Inferred read-only

finemail_get_inbox

Get one owned agent inbox and its usage counts.

Inferred read-only

finemail_create_inbox

Create an owned AI-agent inbox with a meaningful available address.

Potential side effects

finemail_update_inbox

Update an owned inbox identity, address, display name, or metadata.

Potential side effects

finemail_delete_inbox

Soft-delete an owned inbox while retaining its address and audit trail.

Potential side effects

finemail_list_threads

List and search conversation threads across owned inboxes.

Inferred read-only

finemail_get_thread

Get a complete owned email conversation with messages.

Potential side effects

finemail_update_thread

Add or remove labels and update archive/read state across an owned thread.

Potential side effects

finemail_delete_thread

Soft-delete an owned conversation thread.

Potential side effects

finemail_reply_message

Reply or reply-all to an owned message while preserving RFC thread headers.

Potential side effects

finemail_forward_message

Forward an owned message and optional original attachments.

Potential side effects

finemail_update_message

Update labels, read, archive, or quarantine state on an owned message.

Potential side effects

finemail_delete_message

Soft-delete an owned message.

Potential side effects

finemail_list_drafts

List draft and scheduled messages.

Inferred read-only

finemail_get_draft

Get one owned draft or scheduled message.

Potential side effects

finemail_create_draft

Create a draft or schedule it with an ISO-8601 send_at value.

Potential side effects

finemail_update_draft

Update or reschedule an owned draft.

Potential side effects

finemail_send_draft

Send an owned draft immediately.

Potential side effects

finemail_delete_draft

Delete a draft or cancel a scheduled send.

Potential side effects

finemail_wait_for_email

Long-poll for a matching inbound email without frequent client polling.

Potential side effects

finemail_get_attachment

Get safe metadata and an owner-authenticated download path for an owned attachment.

Inferred read-only

finemail_list_webhooks

List owner-scoped signed webhook subscriptions.

Inferred read-only

finemail_create_webhook

Create an HTTPS webhook and return its signing secret once.

Potential side effects

finemail_delete_webhook

Delete an owned webhook subscription.

Potential side effects

finemail_list_domains

List custom domains and their verified DNS state.

Inferred read-only

finemail_create_domain

Start custom-domain onboarding and return required DNS records.

Inferred read-only

finemail_verify_domain

Refresh DNS and SES verification state for an owned custom domain.

Inferred read-only

finemail_list_security_rules

List allow/block rules and inbound security policy.

Inferred read-only

finemail_create_security_rule

Create an allow or block rule for an address or domain.

Potential side effects

finemail_delete_security_rule

Delete an owned allow/block rule.

Potential side effects

finemail_get_usage

Get owner-scoped inbox, storage, sending, delivery, security, quota, and plan usage.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.finemail-mcp]
url = "https://finemail.app/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "finemail-mcp": {
      "type": "http",
      "url": "https://finemail.app/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: finemail-mcp
Remote MCP URL: https://finemail.app/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "finemail-mcp": {
      "url": "https://finemail.app/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "finemail-mcp": {
      "type": "http",
      "url": "https://finemail.app/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "finemail-mcp",
  "transport": "streamable-http",
  "url": "https://finemail.app/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for finemail.app was fetched 2026-08-03T13:58:12.851Z and is being refreshed.

Trust status Neutral

finemail.app is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.