mcpbeat

Inbox Preview MCP Server

ai.powerline/inbox-preview
answering

Inbox Preview is answering right now. Last checked moments ago. It exposes 4 tools.

Render HTML/.eml emails in real Gmail, Outlook & Yahoo web clients and screenshot them

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
561 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add inbox-preview --transport http https://api.powerline.ai/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inbox-preview": {
      "url": "https://api.powerline.ai/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inbox-preview]
url = "https://api.powerline.ai/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "inbox-preview": {
      "url": "https://api.powerline.ai/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "inbox-preview": {
      "url": "https://api.powerline.ai/v1/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

clients
list_clients
List the email clients this deployment can render right now, with their rendering tier, engine, and capabilities
job
get_job
Get the status and screenshots for a preview job. Poll until status is "completed".
screenshot
get_screenshot
Fetch a rendered screenshot. Returns the image URL for the given job, client, width, and environment (color scheme / images).
submit
submit_preview
Submit an email for rendering across email clients — full HTML, or a complete raw .eml (base64). Provide exactly one of html/eml. Returns a job ID to poll for results.

Endpoints

URLTransportStateLatencyChecked
https://api.powerline.ai/v1/mcp streamable-http answering 576 ms 0 min ago

Inbox Preview — questions

Answers built from our own checks of this server.

What can Inbox Preview do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_job, get_screenshot, list_clients, submit_preview. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Inbox Preview working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 561 ms. The bar chart above shows every period we have measured.
How do I connect Inbox Preview?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Inbox Preview need an API key?
No. Inbox Preview completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Inbox Preview?
It answers our handshake in 561 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.