Over the last 18 months, software development workflows underwent a historic transformation. With tools like Cursor, Claude Code, and Antigravity, scaffolding a complete production web application takes minutes.
Yet, despite this quantum leap, the deployment edge remained trapped in the early 2000s.
Once an agent finishes drafting an application, the developer is still forced to:
cname.vercel-dns.com or *.pages.dev).
Software engineering cannot reach true end-to-end autonomy as long as domain registration and DNS routing require manual browser clicks.
Today, we are launching LovieMe v0.6.0—a complete AI-native subdomain and Anycast DNS platform engineered from the ground up for both human engineers and autonomous AI agents.
The cornerstone of the v0.6.0 release is our native Model Context Protocol (MCP) server, packaged as lovieme-mcp.
Add it to your Cursor or Claude Code configuration:
{
"mcpServers": {
"lovieme": {
"command": "npx",
"args": ["-y", "lovieme-mcp"],
"env": {
"LOVIE_API_KEY": "lovie_live_your_token_here"
}
}
}
}
The MCP server exposes 5 deterministic tools:
check_availability(name): Validates subdomain syntax against RFC 1123. claim_subdomain(name): Instantly allocates ownership under *.lovie.me. manage_dns(subdomain, records): Programmatically creates, updates, or prunes Anycast records.apply_preset(subdomain, provider): Applies pre-verified cloud DNS profiles. list_subdomains(): Inspects current domain assets for multi-environment context.
When an AI assistant builds a micro-SaaS demo, it can now claim agent-tracker.lovie.me, wire up Cloudflare or Vercel routing, and provide the user with a verified live edge URL directly in chat.
npx lovie)
For terminal-first engineers, npx lovie eliminates GUI friction entirely:
$ npx lovie subdomains check neural-chat
✓ Subdomain 'neural-chat.lovie.me' is available!
$ npx lovie subdomains claim neural-chat --preset vercel
✓ Successfully claimed neural-chat.lovie.me
✓ Applied Vercel DNS Preset (CNAME -> cname.vercel-dns.com)
⚡ Active on 160+ Anycast edge nodes worldwide in 1.4s
The CLI features interactive browser OAuth for local terminal sessions and headless token support (LOVIE_API_KEY) for Docker containers and continuous integration pipelines.
Granting autonomous agents infrastructure access poses security hazards. If an untrusted agent or compromised script gains full administrative access, your entire zone is at risk.
LovieMe solves this with One-Way Cryptographic Tokens & Subdomain Sandboxing:
lovie_live_<48_hex> structure. They are shown once upon creation and stored exclusively as SHA-256 hashes.subdomains:read, subdomains:write, dns:write, webhooks:read). allowed_subdomains): pr-* or dev-preview). Any attempt to modify or prune production records returns an immediate 403 Forbidden.
Manual DNS configuration is notoriously error-prone. LovieMe provides 1-Click Verified Cloud Presets:
Instead of waiting blindly, LovieMe queries global DNS-over-HTTPS (DoH) backbones in parallel:
8.8.8.8) 1.1.1.1) 9.9.9.9)
The diagnostic engine confirms sub-2-second global propagation across North America, Europe, and Asia empirically.
Teams waste hours cleaning up stale test domains. The official GitHub Action (lovieme/action@v1) automates the full lifecycle:
name: Deploy Preview Edge
on:
pull_request:
types: [opened, synchronize, closed]
jobs:
preview-domain:
runs-on: ubuntu-latest
steps:
- name: Sync Ephemeral Subdomain
uses: lovieme/action@v1
with:
subdomain: pr-${{ github.event.number }}-myapp
target: ${{ steps.build.outputs.preview_url }}
token: ${{ secrets.LOVIE_API_KEY }}
When a PR is opened, a dedicated subdomain is created. When the PR is merged or closed, the subdomain is automatically deleted.
Under DNS standards (RFC 1034 section 3.6.2 and RFC 2181), if a CNAME record exists at a node, no other data records may exist at that node. Setting an A record alongside a CNAME causes silent resolution failure (SERVFAIL) across major resolvers.
LovieMe's Conflict Engine inspects RRsets prior to persistence, blocks illegal collisions at the API perimeter, and surfaces one-click automated repair workflows to keep your edge records healthy.
/llms.txt Discovery
https://www.lovie.me/api/v1/webhooks/catch/[id]) streaming live Stripe, GitHub, and Clerk payloads to your browser via WebSockets. No ngrok or local tunnels needed./llm.txt, /api/v1/openapi.json allow web-browsing models to autonomously read and execute LovieMe APIs without human intervention.
Modern infrastructure should match the speed of the models generating our software.
lovieme/action@v1)
Built by Sagar Kewat. What edge DNS challenges are you facing with your AI agents? Let me know in the comments!