Port vs Resend
Side-by-side trajectory, velocity, and editorial themes.
Port turns its AI catalog into an automation platform as Workflows hits open beta
Port is an internal developer portal that has spent 2026 turning its software catalog into an AI-and-automation platform. Recent months added an MCP gateway (external MCP servers into Port AI), BYO/OpenAI-compatible LLM endpoints, an Azure Anthropic provider, Skills and Memory for its AI assistant, and a public plugins repo. June's headline is Workflows reaching Open Beta — a visual, node-based builder for self-service automations.
Two arcs are converging: Port AI as an open, model-agnostic gateway (external MCP, any OpenAI-compatible endpoint, Azure-hosted Claude, Skills/Memory) and Workflows as a visual automation layer on top of the catalog. The steady monthly 'Big' feature and the plugins ecosystem signal Port positioning as the automation and agentic-operations hub for platform-engineering teams, not just a catalog of services.
Workflows likely moves from Open Beta toward GA with more triggers and actions, while Port AI keeps expanding its connector and model surface — the two being stitched into one agentic self-service experience.
Resend goes agent-native with a hosted, OAuth-backed MCP server for email.
Resend is a developer-first email API that has spent the last quarter widening on two fronts. It is building an agent-native surface — an official Claude Code plugin, mentions in AI chats, and now a hosted MCP server — while also creeping past transactional email into audience tooling with CSV contact import, in-email charts, and richer editor previews. The core remains a clean API for sending mail.
The direction is Resend-as-infrastructure that both humans and agents call directly. The MCP thread — a plugin in May, a hosted server in July — turns email into a tool an LLM can invoke over OAuth rather than hand-rolled keys, while the contacts and broadcast work points at competing with marketing-email incumbents, not just transactional senders. Distribution is shifting toward embedding where developers already are, via Vercel's marketplace and Auth0.
Expect the MCP surface to grow from sending into contact and analytics operations, and the audience and broadcast side to keep maturing toward a full marketing-email offering.
See more alternatives to Port →
See more alternatives to Resend →