Resend MCP server with Linkeddit: competitor alert emails sent from your own domain

The Resend MCP server is Resend's own connector for AI clients, and it covers the whole account, not just sending. The Agent Index lists 85 tools, 38 of them reads and 45 writes, and Resend's docs group them as emails, received emails, templates, contacts, broadcasts, automations, events, domains, segments, topics, contact properties, API keys, webhooks, logs and an editor link to the Resend dashboard. Audienceful's roundup counts over 100 tools, so treat any single number as a snapshot.

It is hosted at https://mcp.resend.com/mcp, and the same open-source code runs locally as the resend-mcp package. Resend's Claude page says the official Claude connector bundles the MCP server with every Resend skill in one install. Two things stay outside it. It describes your own sending, never what competitors do, and it cannot listen for events: Carly's guide notes the server can configure webhooks for bounces and opens but has nothing on the receiving end.

Linkeddit finds and dates the change, and Resend delivers the email. Compete tracks competitor blogs, changelogs and monitored pricing and landing pages, with a priority and a reason on each signal. Answer Radar records which brands the five answer engines name and recommend. Both come with one plan at $60 a month. Linkeddit writes no copy and sends no mail, so the customer's own assistant decides what the email says.

Claude sits between them. It reads compete_signals_get, then drafts the email, then asks Resend to create it as a broadcast or a template. Resend's docs list create and send as separate actions on broadcasts, which is the seam to use: have Claude create the broadcast, open it in the Resend dashboard through the editor link, read it, and only then send.

This is the problem sellers describe in their own words. "I literally have a browser folder with their product pages and I open them every morning to check if they changed prices, launched sales, or added new items," said a Shopify merchant on Reddit. The folder is the data job, and the email is the delivery job, so they belong in different tools.

A read-only compete_signals_get filtered to high priority returned two signals on Linkeddit's test project, plausible.io, both for the week of 2026-10-26. Matomo published critical PHP security updates and guidance, with a note that self-hosted users now carry maintenance overhead. Fathom launched an AI assistant named Luna. Each carries a title, category, source name, source link and a why_it_matters line, which is the raw material for a two-line alert.

The monitor list is what makes a weekly alert possible. compete_monitors_get listed five competitor monitors on the same project, all set to weekly, each with a next run of 2026-11-04. Linkeddit's side runs on its own clock, so the alert is ready whenever you ask for it.

A read-only answer_results_get on the project shows the other half. ChatGPT named plausible in 16 of 18 admissible samples, a presence rate of 89%, and plausible held 16 of 78 vendor mentions, a 20.5% share of voice. Perplexity returned no usable samples, and the result reports that as unmeasured rather than zero. An alert that says so is more useful than one that hides it.

No, Claude acts when you start it. A weekly alert happens in one of two ways: you run the same saved prompt each week, or a scheduler you already use starts a Claude session. Resend does support scheduled sends, and its docs describe scheduling, rescheduling and cancelling them, so Claude can queue the email for Monday morning once you have approved the content. That schedules delivery, not the research, and these pages do not pretend otherwise.

Send only to people who expect the mail: your own team, or a small list that opted in. A competitor alert is an internal briefing, so a segment of your own pricing, product and sales staff is the safe default. If you want to push the same insight to customers, that is a marketing broadcast with its own consent rules, and it should be written and approved as one.

Check the sending domain, the key and the confirmation step. Carly's guide says Resend will not send from an unverified domain, which is the usual reason a first MCP send fails with nothing obviously wrong in the prompt. It also warns that a full-access API key lets an AI client delete domains and rotate keys, so prefer OAuth in the connector directory or a key limited to sending.

Audienceful's roundup adds the sharpest warning: Resend's send tools act as soon as they are called, so your AI client's approval prompt is the safety net. Set the connector to ask before each write, and keep the prompt to a draft. Then read the result for a wrong price, a missing source link or a claim the data does not support. On the test project, an empty brief or a partial run should appear in the email as a stated gap.

Three, all from the same data. The first is a weekly digest: the headline change, where an engine named a competitor instead of you, and moves grouped by priority. The second is a response to a competitor pricing or messaging change, written for the people who must decide, with the source link and the date on the signal. The third is comparison content: Claude reads the competitor signals and Search's competitor data, then drafts the points a comparison email or page should make.

For the second and third, Claude can also use a Resend template with {{{VARIABLE}}} placeholders so the layout stays fixed and only the facts change week to week.