<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Jean Carlos</title>
    <description>The latest articles on DEV Community by Jean Carlos (@jean_carlos_4fc0f8981eb24).</description>
    <link>https://dev.to/jean_carlos_4fc0f8981eb24</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204191%2Fffc16a1b-d765-49a5-89f8-247ab06b29a7.jpg</url>
      <title>DEV Community: Jean Carlos</title>
      <link>https://dev.to/jean_carlos_4fc0f8981eb24</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jean_carlos_4fc0f8981eb24"/>
    <language>en</language>
    <item>
      <title>How to keep shared short links and QR codes working when a campaign destination changes</title>
      <dc:creator>Jean Carlos</dc:creator>
      <pubDate>Fri, 06 Nov 2026 16:36:19 +0000</pubDate>
      <link>https://dev.to/jean_carlos_4fc0f8981eb24/how-to-keep-shared-short-links-and-qr-codes-working-when-a-campaign-destination-changes-3h69</link>
      <guid>https://dev.to/jean_carlos_4fc0f8981eb24/how-to-keep-shared-short-links-and-qr-codes-working-when-a-campaign-destination-changes-3h69</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I work with &lt;a href="https://je4ndev.com" rel="noopener noreferrer"&gt;JE4NDEV&lt;/a&gt;, the remote studio that built &lt;a href="https://urlpivot.app/" rel="noopener noreferrer"&gt;URLPivot&lt;/a&gt;. This article explains a durable pattern for campaign links and QR codes. URLPivot is one product that implements that pattern; every product claim below is taken from its public pages, and every general HTTP, UTM or QR claim links to official docs at the end. Self-serve links only: no call or meeting pitch.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;You ship a SaaS waitlist. The short link goes into the launch newsletter. The QR goes on conference badges and a one-pager at the booth. Two weeks later the waitlist should become the public docs, or the beta signup should move to a new subdomain. The destination changed. The shared and printed addresses did not.&lt;/p&gt;

&lt;p&gt;That is when campaigns quietly break. People still open the old URL. The page 404s, lands on an unrelated homepage, or shows a stale offer. The QR did not fail. It still encodes the same string. The string still points at a place that is no longer useful.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: the destination moves after the share
&lt;/h2&gt;

&lt;p&gt;A campaign URL has two lives:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The public address&lt;/strong&gt; people click, copy or scan: the short link in email, the QR on a badge, the link in a launch thread.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The destination&lt;/strong&gt;: the waitlist, docs section, pricing page or changelog that you want them to land on &lt;em&gt;today&lt;/em&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Those lives diverge as soon as something gets printed or forwarded. A PDF in an inbox, a laminated badge, a newsletter that already went out: none of them update when the product moves.&lt;/p&gt;

&lt;p&gt;Minting a new short link and asking everyone to switch splits click history and leaves the old QR opening the wrong flow.&lt;/p&gt;

&lt;h2&gt;
  
  
  How redirects and short links work (high level)
&lt;/h2&gt;

&lt;p&gt;At HTTP level, a redirect is simple. The browser requests a URL. The server answers with a &lt;code&gt;3xx&lt;/code&gt; status and a &lt;code&gt;Location&lt;/code&gt; header. The browser follows it. MDN's guide on &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections" rel="noopener noreferrer"&gt;HTTP redirections&lt;/a&gt; states that redirect responses have status codes that start with &lt;code&gt;3&lt;/code&gt;, and a &lt;code&gt;Location&lt;/code&gt; header holding the URL to redirect to.&lt;/p&gt;

&lt;p&gt;Two shapes matter for campaigns:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;temporary&lt;/strong&gt; redirect (for example &lt;code&gt;302&lt;/code&gt; or &lt;code&gt;307&lt;/code&gt;) says the destination may change again; crawlers should not treat it as the permanent home.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;permanent&lt;/strong&gt; redirect (for example &lt;code&gt;301&lt;/code&gt; or &lt;code&gt;308&lt;/code&gt;) says the public URL has moved for good.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A managed short link is a stable public URL your tool resolves with a redirect to the destination you configured. The visitor barely notices the hop. You care, because that hop is where you change the destination without changing the public address.&lt;/p&gt;

&lt;p&gt;QR codes sit one layer below. &lt;a href="https://www.iso.org/standard/83389.html" rel="noopener noreferrer"&gt;ISO/IEC 18004&lt;/a&gt; defines how a QR symbol encodes data. It does &lt;strong&gt;not&lt;/strong&gt; define what the payload means. If the payload is a URL, the phone opens that URL and normal HTTP rules apply. Change the bytes inside the QR and you need a new print. Keep the same URL string and you can change what that URL does on the server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why hardcoding the destination fails
&lt;/h2&gt;

&lt;p&gt;Hardcoding means the public address &lt;em&gt;is&lt;/em&gt; the destination: the newsletter links straight to &lt;code&gt;/waitlist-oct&lt;/code&gt;, the badge QR encodes a full docs path with UTM query params, the one-pager prints a changelog URL. That works until the path, host, offer or tracking changes. Then every channel that already carried the old string is wrong.&lt;/p&gt;

&lt;p&gt;UTM parameters make the trap sharper. Google's Analytics help on &lt;a href="https://support.google.com/analytics/answer/10917952" rel="noopener noreferrer"&gt;custom campaign URLs&lt;/a&gt; says you add &lt;code&gt;utm_source&lt;/code&gt;, &lt;code&gt;utm_medium&lt;/code&gt;, &lt;code&gt;utm_campaign&lt;/code&gt; (and related fields) to the &lt;strong&gt;destination URLs&lt;/strong&gt; used in referral links. If those parameters are baked into a printed QR, you cannot retag without reprinting. If they live on the destination behind a stable public URL, you can adjust tagging when the offer moves.&lt;/p&gt;

&lt;h2&gt;
  
  
  The design pattern: stable public URL → editable destination
&lt;/h2&gt;

&lt;p&gt;Treat the thing you share and print as infrastructure, not as the offer:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create one &lt;strong&gt;stable public URL&lt;/strong&gt; for each durable entry point (newsletter CTA, badge, packaging insert).&lt;/li&gt;
&lt;li&gt;Point that URL at the &lt;strong&gt;current destination&lt;/strong&gt; through a redirect you control.&lt;/li&gt;
&lt;li&gt;When the campaign evolves, &lt;strong&gt;edit the destination&lt;/strong&gt;. Do not mint a new public URL unless the campaign itself is new.&lt;/li&gt;
&lt;li&gt;Keep the QR image generated from the stable public URL. Archive that PNG or SVG with the campaign so reprints stay identical.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Examples that fit product and SaaS work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SaaS launch:&lt;/strong&gt; &lt;code&gt;…/go/launch&lt;/code&gt; → waitlist today, docs tomorrow, pricing after GA.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Product docs:&lt;/strong&gt; &lt;code&gt;…/go/docs-start&lt;/code&gt; → the current "start here" guide after a docs reorg.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Conference badge:&lt;/strong&gt; &lt;code&gt;…/go/conf-2026&lt;/code&gt; → live demo signup during the event, then the on-demand recording.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Email newsletter:&lt;/strong&gt; &lt;code&gt;…/go/issue-47-cta&lt;/code&gt; → the feature post; later a follow-up survey, without editing archived HTML.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Print for a product campaign:&lt;/strong&gt; packaging insert or booth poster → the current campaign landing page while creative iterates.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The shared artifact stays put. Only the redirect target moves.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical checklist before you share or print
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Decide the durable entry points.&lt;/strong&gt; One public URL per channel that will outlive a single destination. Do not reuse one public URL for unrelated campaigns if you need clean history.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Put UTMs on the destination, not inside the printed code.&lt;/strong&gt; Build the tagged destination with Google's &lt;a href="https://ga-dev-tools.google/ga4/campaign-url-builder/" rel="noopener noreferrer"&gt;Campaign URL Builder&lt;/a&gt; or by hand (&lt;code&gt;utm_source&lt;/code&gt;, &lt;code&gt;utm_medium&lt;/code&gt;, &lt;code&gt;utm_campaign&lt;/code&gt; at minimum). Set the managed link's destination to that tagged URL. The QR encodes only the stable public URL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test the redirect the way a stranger will.&lt;/strong&gt; Open the public URL in a private window on phone and desktop. Confirm the final page matches today's offer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Export and archive the QR of the stable URL.&lt;/strong&gt; Future reprints must regenerate from the same public URL, not from whatever destination is current that day.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Group related entry points.&lt;/strong&gt; Badge + newsletter + docs CTA can be separate managed links under one campaign Page or workspace so destinations move together.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prefer temporary semantics while the offer is still moving.&lt;/strong&gt; Switch to permanent only when the public URL itself is retiring.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Know the fixed-content caveat.&lt;/strong&gt; Some QR payloads are not ordinary URLs. URLPivot's public site notes that &lt;strong&gt;Pix has fixed QR content&lt;/strong&gt;: changing a managed link destination does not rewrite a Pix QR the way it rewrites a URL QR.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;If agents help operate links, scope their permissions.&lt;/strong&gt; Prefer workspace-scoped tokens that can list links and change destinations without billing or admin powers. Revoke when the campaign ends.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  One product that implements the pattern (URLPivot)
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Disclosure (product):&lt;/strong&gt; URLPivot is built by JE4NDEV. I am writing about it because we built it for this failure mode. Try it yourself; do not take marketing copy as proof of your results.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;From the public product pages, URLPivot offers links, QR codes and Pages for what comes after sharing: change destinations without replacing the link or QR you already shared. That maps to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a &lt;strong&gt;managed link&lt;/strong&gt; with a stable public address and an editable destination&lt;/li&gt;
&lt;li&gt;a &lt;strong&gt;reusable QR&lt;/strong&gt; for that public address&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pages&lt;/strong&gt; that gather managed links into one focused public destination, with button destinations you can update without rebuilding the Page&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;views and clicks&lt;/strong&gt;, plus campaign signals the site describes as including referrer and approximate country; the JE4NDEV project page also notes human/bot traffic signals without retaining raw IP addresses&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;workspaces&lt;/strong&gt; to separate client or brand work, with an option on paid plans to connect an eligible domain&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;workspace-scoped MCP access&lt;/strong&gt;: connect an MCP client with a revocable workspace token; operate links and Pages within token permissions; no billing or administration access (the project page adds that agents can list and create links and change destinations, without billing, deletion, admin or DNS permissions)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Self-serve entry points:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Temporary homepage demo without an account: &lt;a href="https://urlpivot.app/" rel="noopener noreferrer"&gt;urlpivot.app&lt;/a&gt; (private temporary demo, valid for two hours; no customer data or real campaign metrics)&lt;/li&gt;
&lt;li&gt;Free account without a card: &lt;a href="https://urlpivot.app/signup" rel="noopener noreferrer"&gt;urlpivot.app/signup&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Plan limits: &lt;a href="https://urlpivot.app/pricing" rel="noopener noreferrer"&gt;urlpivot.app/pricing&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Studio project page: &lt;a href="https://je4ndev.com/en/projects/urlpivot" rel="noopener noreferrer"&gt;je4ndev.com/en/projects/urlpivot&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;URLPivot's own Page: &lt;a href="https://urlpivot.app/p/urlpivot" rel="noopener noreferrer"&gt;urlpivot.app/p/urlpivot&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The public site does not establish customer volume, revenue or campaign performance. Use the demo or Free plan to verify the pattern on your own links.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrap-up
&lt;/h2&gt;

&lt;p&gt;Shared links and printed QR codes fail less often when you stop treating the destination as the thing you publish. Publish a stable public URL. Point it at today's destination with a redirect you control. Put UTMs on that destination. Archive the QR of the stable URL. When the campaign moves (waitlist to docs, live demo to recording, launch page to pricing), edit the destination and leave the badges, newsletter archive and packaging insert alone.&lt;/p&gt;

&lt;p&gt;To try a product that already wires the pattern together, start at &lt;a href="https://urlpivot.app/" rel="noopener noreferrer"&gt;urlpivot.app&lt;/a&gt; or create a Free account at &lt;a href="https://urlpivot.app/signup" rel="noopener noreferrer"&gt;urlpivot.app/signup&lt;/a&gt;. If you only needed the checklist, you can implement the same idea with any redirect you fully control.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fact sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;URLPivot homepage (stable public address, editable destination, reusable QR, Pages, views/clicks, temporary demo without account, MCP client with revocable workspace token / workspace permissions, Pix fixed QR content note): &lt;a href="https://urlpivot.app/" rel="noopener noreferrer"&gt;https://urlpivot.app/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;URLPivot pricing (Free without a card; plan limits; MCP agents with workspace permissions): &lt;a href="https://urlpivot.app/pricing" rel="noopener noreferrer"&gt;https://urlpivot.app/pricing&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;URLPivot signup (create account without a card): &lt;a href="https://urlpivot.app/signup" rel="noopener noreferrer"&gt;https://urlpivot.app/signup&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;URLPivot official Page: &lt;a href="https://urlpivot.app/p/urlpivot" rel="noopener noreferrer"&gt;https://urlpivot.app/p/urlpivot&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;JE4NDEV URLPivot project page (stable link, reusable QR, Pages, views/clicks, human/bot signals without retaining raw IP addresses, workspace-scoped MCP access limits, demo without signup, proof boundary): &lt;a href="https://je4ndev.com/en/projects/urlpivot" rel="noopener noreferrer"&gt;https://je4ndev.com/en/projects/urlpivot&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;JE4NDEV English home (studio context; URLPivot listed as a product): &lt;a href="https://je4ndev.com/en/" rel="noopener noreferrer"&gt;https://je4ndev.com/en/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;MDN, Redirections in HTTP: &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections" rel="noopener noreferrer"&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Redirections&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;MDN, 301 Moved Permanently: &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301" rel="noopener noreferrer"&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/301&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;MDN, 302 Found: &lt;a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302" rel="noopener noreferrer"&gt;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/302&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Analytics Help, URL builders / UTM parameters on destination URLs: &lt;a href="https://support.google.com/analytics/answer/10917952" rel="noopener noreferrer"&gt;https://support.google.com/analytics/answer/10917952&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google, GA4 Campaign URL Builder: &lt;a href="https://ga-dev-tools.google/ga4/campaign-url-builder/" rel="noopener noreferrer"&gt;https://ga-dev-tools.google/ga4/campaign-url-builder/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;ISO, ISO/IEC 18004:2024 QR code symbology specification: &lt;a href="https://www.iso.org/standard/83389.html" rel="noopener noreferrer"&gt;https://www.iso.org/standard/83389.html&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Unverified / out of scope (flagged)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;No public &lt;code&gt;/docs&lt;/code&gt; page was found at urlpivot.app/docs (HTTP 404 at research time); do not invent doc URLs.&lt;/li&gt;
&lt;li&gt;Exact redirect status code URLPivot returns per hop (301 vs 302 vs 307 vs 308) is &lt;strong&gt;not&lt;/strong&gt; stated on the public pages reviewed; the article therefore speaks in general MDN terms only.&lt;/li&gt;
&lt;li&gt;"Human/bot traffic signals" and "without retaining raw IP addresses" are taken from the JE4NDEV project page wording; raw implementation detail beyond that page is unverified.&lt;/li&gt;
&lt;li&gt;Catalogue examples on the URLPivot homepage (fictional Pages) are illustrative only and are not used as customer proof here.&lt;/li&gt;
&lt;li&gt;No customer counts, open rates, scan rates or revenue figures are claimed; none are published as verified metrics on the pages above.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>marketing</category>
      <category>saas</category>
    </item>
    <item>
      <title>Let your AI assistant draft customer replies (with a human in the loop): elozi-mcp</title>
      <dc:creator>Jean Carlos</dc:creator>
      <pubDate>Wed, 04 Nov 2026 18:59:56 +0000</pubDate>
      <link>https://dev.to/jean_carlos_4fc0f8981eb24/let-your-ai-assistant-draft-customer-replies-with-a-human-in-the-loop-elozi-mcp-23mo</link>
      <guid>https://dev.to/jean_carlos_4fc0f8981eb24/let-your-ai-assistant-draft-customer-replies-with-a-human-in-the-loop-elozi-mcp-23mo</guid>
      <description>&lt;p&gt;I build Elozi, a customer-service workspace. I wanted AI assistants to help with support without giving them free rein, so I published elozi-mcp (MIT, v0.1.1).&lt;/p&gt;

&lt;p&gt;It is a small stdio bridge that connects desktop agents (Claude Desktop, Claude Code, Cursor, Codex or any MCP stdio client) to Elozi's hosted endpoint. It stores no data locally, adds no telemetry and does not retry tool calls automatically.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Permissions come from the token.&lt;/strong&gt; In the Elozi panel you create an agent of type "Agent via MCP" and a service identity with channels, departments, capabilities, validity and daily quotas. The assistant only sees tools your token allows. A good start is &lt;code&gt;conversation.read&lt;/code&gt; plus &lt;code&gt;reply.submit&lt;/code&gt;: it reads and drafts, a person approves. Add &lt;code&gt;reply.send&lt;/code&gt; or &lt;code&gt;conversation.manage&lt;/code&gt; only when you want it to act alone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Requirements:&lt;/strong&gt; Node.js 22+ and an &lt;code&gt;ELOZI_API_TOKEN&lt;/code&gt; (starts with &lt;code&gt;elozi_svc_&lt;/code&gt;, shown once).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Install / run:&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx &lt;span class="nt"&gt;-y&lt;/span&gt; elozi-mcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Cursor example&lt;/strong&gt; (&lt;code&gt;~/.cursor/mcp.json&lt;/code&gt;):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"mcpServers"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"elozi"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"command"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"npx"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"args"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"-y"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"elozi-mcp"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"env"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"ELOZI_API_TOKEN"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"elozi_svc_YOUR_TOKEN"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Claude Code users can also connect over HTTP directly:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;claude mcp add &lt;span class="nt"&gt;--transport&lt;/span&gt; http elozi https://elozi.je4ndev.com/api/agent/mcp &lt;span class="nt"&gt;--header&lt;/span&gt; &lt;span class="s2"&gt;"Authorization: Bearer &lt;/span&gt;&lt;span class="k"&gt;${&lt;/span&gt;&lt;span class="nv"&gt;ELOZI_API_TOKEN&lt;/span&gt;&lt;span class="k"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Keep the token in private config only, never in chats or URLs.&lt;/p&gt;

&lt;p&gt;npm: &lt;a href="https://www.npmjs.com/package/elozi-mcp" rel="noopener noreferrer"&gt;https://www.npmjs.com/package/elozi-mcp&lt;/a&gt;&lt;br&gt;
Repo: &lt;a href="https://github.com/JE4NVRG/elozi" rel="noopener noreferrer"&gt;https://github.com/JE4NVRG/elozi&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mcp</category>
      <category>ai</category>
      <category>opensource</category>
      <category>node</category>
    </item>
    <item>
      <title>Transactional email for a one-person app: what you actually need</title>
      <dc:creator>Jean Carlos</dc:creator>
      <pubDate>Sat, 24 Oct 2026 07:58:27 +0000</pubDate>
      <link>https://dev.to/jean_carlos_4fc0f8981eb24/transactional-email-for-a-one-person-app-what-you-actually-need-4n0p</link>
      <guid>https://dev.to/jean_carlos_4fc0f8981eb24/transactional-email-for-a-one-person-app-what-you-actually-need-4n0p</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Disclosure:&lt;/strong&gt; I build MepMail, an open-source (AGPL-3.0) email API that runs on Amazon SES and accepts Resend's request format. This post is about my own tool. MepMail isn't affiliated with or endorsed by Resend. This post was drafted with AI assistance and reviewed for accuracy.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;When you ship a side project on your own, email is easy to underestimate. You need sign-up confirmations, password resets, and maybe a receipt. You don't need a sales call, a contract, or a new SDK to learn. This is the checklist I use, and how MepMail fits each point.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. A free tier you can stay on for a while
&lt;/h2&gt;

&lt;p&gt;Most solo apps send a handful of emails a day for months. MepMail's Send Free tier gives you &lt;strong&gt;100 emails a day with no card&lt;/strong&gt;: one domain, one workspace, 1,000 contacts, and 1 MB of attachments per message. The limit is daily (UTC) and there are no overage charges. Up to 50% past the limit, sends keep going; after that they wait in a queue for the next day instead of failing.&lt;/p&gt;

&lt;p&gt;Paid Send plans exist for when you grow. Check &lt;a href="https://mepmail.dev/pricing" rel="noopener noreferrer"&gt;https://mepmail.dev/pricing&lt;/a&gt; for current numbers rather than trusting a blog post.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. No lock-in to a new SDK
&lt;/h2&gt;

&lt;p&gt;If you already use the official &lt;code&gt;resend&lt;/code&gt; package, you can keep it. MepMail accepts the same request shapes for the compatible sending flows, so the change is the key and the base URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Resend&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;resend&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;resend&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Resend&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;RESEND_API_KEY&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;baseUrl&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://api.mepmail.dev&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;

&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;resend&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;emails&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;send&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;to&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;subject&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;html&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or set &lt;code&gt;RESEND_BASE_URL=https://api.mepmail.dev&lt;/code&gt; in your environment. If your stack only speaks SMTP, there's a relay at &lt;code&gt;smtp.mepmail.dev:2587&lt;/code&gt; with STARTTLS, authenticated with an API key.&lt;/p&gt;

&lt;p&gt;To be honest about it, "compatible" doesn't mean "identical". Automated contract tests pin &lt;code&gt;resend@6.27.0&lt;/code&gt; for Node only. Some endpoints (&lt;code&gt;automations&lt;/code&gt;, &lt;code&gt;events&lt;/code&gt;, &lt;code&gt;logs&lt;/code&gt;, &lt;code&gt;oauthGrants&lt;/code&gt;) return &lt;code&gt;404&lt;/code&gt;. Inbound over the API and SSO aren't covered. Go and Ruby need a trailing slash on the base URL, while Node, Python, Rust and Elixir must not have one. The Java SDK hard-codes its URL, so use HTTP or SMTP there. The full list is at &lt;a href="https://docs.mepmail.dev/sdks" rel="noopener noreferrer"&gt;https://docs.mepmail.dev/sdks&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Moving data shouldn't take a weekend
&lt;/h2&gt;

&lt;p&gt;If you're moving an existing account, one command copies contacts, segments, topics, templates, webhooks (signing secrets included), suppressions and domains:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npx @mepmail/cli migrate plan &lt;span class="nt"&gt;--from&lt;/span&gt; resend   &lt;span class="c"&gt;# read-only preview&lt;/span&gt;
npx @mepmail/cli migrate &lt;span class="nt"&gt;--from&lt;/span&gt; resend
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;@mepmail/cli&lt;/code&gt; is at 0.2.4 on npm. It respects the source's rate limit, keeps keys in memory only (never on disk, no telemetry), can be re-run as a diff, and &lt;code&gt;migrate rollback&lt;/code&gt; deletes only what it created. Sent history, API keys and DKIM records stay behind. You publish new DNS records and create new keys.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Guardrails you'd otherwise build yourself
&lt;/h2&gt;

&lt;p&gt;A solo dev doesn't have time to babysit reputation. MepMail handles the boring parts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Hard bounces and complaints become suppressions automatically.&lt;/li&gt;
&lt;li&gt;RFC 8058 one-click unsubscribe headers and a hosted unsubscribe page.&lt;/li&gt;
&lt;li&gt;Webhooks signed with Standard Webhooks signatures, with a secret you can rotate.&lt;/li&gt;
&lt;li&gt;Every email gets 21 deliverability checks in the dashboard, from DMARC alignment to List-Unsubscribe.&lt;/li&gt;
&lt;li&gt;Idempotency via the &lt;code&gt;Idempotency-Key&lt;/code&gt; header, so a retried request doesn't send twice.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this guarantees inbox placement. Content, your domain's history and the receiving side still matter.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Expect some setup time
&lt;/h2&gt;

&lt;p&gt;Plan for lead time before your first real send. Your domain has to pass DNS verification (DKIM and MAIL FROM on SES), and new accounts may go through a security review before they can send at volume. Start this a few days before you need it, not the night before launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. An exit door
&lt;/h2&gt;

&lt;p&gt;The platform is AGPL-3.0. If you'd rather run it yourself, it self-hosts with Docker against your own AWS SES account. You keep SES's own console and pay AWS directly. MepMail Cloud also lets you download the exact source of the version it's running.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about the bigger providers?
&lt;/h2&gt;

&lt;p&gt;They're good products, and they keep investing. This month, for example, Resend announced Forge, its own mail transfer agent. MepMail isn't trying to out-build anyone at that layer. It runs on Amazon SES. The pitch is narrower: a free daily allowance, an SDK you already know, an open codebase, and a short path in or out.&lt;/p&gt;

&lt;p&gt;If you try it and a call your app depends on behaves differently, tell me in the comments. That's the most useful feedback I can get.&lt;/p&gt;

</description>
      <category>email</category>
      <category>webdev</category>
      <category>node</category>
      <category>sideprojects</category>
    </item>
  </channel>
</rss>
