DomBot

All your domains, from every registrar, in one app + MCP.

DomBot pulls your whole domain portfolio — scattered across GoDaddy, Dynadot, Cloudflare, and more — into one desktop app, and serves the same portfolio to your AI agents through a built-in MCP server. It's free, open source, and local-first: your data and API keys stay on your machine.

Download for macOS, Windows, or Linux from dombot.ai or the Releases page, or try the live demo: the full app in your browser on an invented portfolio, no install and no account.

What it does

• One portfolio, every registrar. Aggregates all your domains across the registrars you configure into a single sortable, filterable table — search by name, filter by TLD / registrar / nameserver, and see registrar, creation and expiry dates, auto-renew, transfer lock, WHOIS privacy, and nameservers side by side. Expiry dates are color-coded by urgency, and at-risk domains (expired, grace, redemption, hold) get a status badge.
• Renewal costs at a glance. A renewals dashboard forecasts your spend: yearly total, amount due in the next 90 days, a month-by-month renewal chart, and breakdowns by registrar and TLD. Prices come from registrar quotes where available and a base per-TLD price database otherwise, and you can enter a price by hand for anything still unpriced.
• Marketplaces. Connect Afternic, Sedo and Atom accounts to see each name's listing, price, and 12-month views, leads and searches in the table, and list or delist names at your DomBot prices from the row menu or in bulk. Completed sales are recorded in each name's history. See Connecting marketplaces.
• Sales. Every sale in one place: what the markets report, and the private and imported sales you record, with fees, net, holding period and profit where what you paid is known. Filter by date, market, TLD or registrar and the totals above follow, in your preferred currency (a sale in another is converted at its month's average exchange rate); export to CSV. A sale waiting on the auth code unlocks the name and sends the code from the registrar in two clicks, and where the registrar holds the buyer's transfer for you to answer (Dynadot), one more approves it.
• Export. One click exports the current (filtered, sorted) view to a spreadsheet-friendly CSV.
• Instant, offline-friendly launch. The whole portfolio is cached on disk and painted the moment the app opens, with no network calls; you refresh on demand (it never auto-refreshes) and a timestamp flags when data is going stale.
• Agent-ready. An embedded local MCP server lets AI agents (Claude Code, Claude Desktop, any MCP client) read and manage the same portfolio — see Connecting an AI agent.

Configuring registrars

DomBot currently supports GoDaddy, Cloudflare, Dynadot, NameSilo, Spaceship, Namecheap, Porkbun, Gandi, NameBright, Name.com, 101domain, Unstoppable, and Namefi, with more on the way.

Add each registrar in Settings → Registrars with an API key from that provider's account — DomBot shows where to find each one. Credentials are stored encrypted on your device via your OS keychain (Electron safeStorage) and are never sent anywhere but the registrar's own API. See SECURITY.md for the full trust model and how to verify it yourself.

After saving a registrar’s first account, use Add another account inside its card to connect more. An account selector appears only for registrars with multiple accounts; single-account registrars keep the original flow. See multiple registrar accounts for migration and MCP selection.

Connecting marketplaces

DomBot supports Afternic, Sedo, and Atom. Add an account in Settings → Markets; each market's card says which keys it needs and where to get them (Sedo's partner ID and sign key come from applying to Sedo, and Atom's API access is a beta for sellers with 500+ listings). Market keys are stored encrypted like registrar keys and are sent only to that market's API. How the markets map into one model, and what each API can and can't do, is in docs/markets.md.

Connecting an AI agent

DomBot runs a local MCP server, bound to your machine only, so any MCP client can work with your portfolio. To connect Claude Code:

claude mcp add dombot --transport http http://127.0.0.1:4123/mcp

On first connect a browser page opens and DomBot's own window shows an Approve/Deny prompt with a matching confirmation code. Approve once and the client stays paired across restarts; manage or revoke paired clients in Settings → MCP Clients. The URL and a ready-to-paste connect command are also shown on the Home screen.

Claude Desktop (and other clients that can only launch a command) use the app itself as a stdio server. Copy the ready-made entry from Settings → MCP into claude_desktop_config.json; it looks like:

{
  "mcpServers": {
    "dombot": {
      "command": "/Applications/DomBot.app/Contents/MacOS/DomBot",
      "args": ["--mcp-stdio"]
    }
  }
}

No approval prompt is needed for this route — it runs as you, on your machine — and if DomBot isn't open when the client starts, it launches automatically.

This is the beginning of the README. Read the rest at the original. Read the full README ↗