Entri MCP

Self-serve

Start today

1

Get the Startup plan
(up to 600 domains/yr)

2

Add Entri to your app

3

Your users connect their own domains

Cancel anytime

Need to connect more than 600 domains/yr?

Talk to sales.

More and more of your users are building inside a chat window. They ask an AI tool to draft a landing page, spin up a form, or launch a booking site, and the agent does it. Then they hit the last step: publishing on their own domain. Historically, that meant leaving the conversation, digging through account settings, and copying DNS records into a registrar dashboard.

Earlier this year we launched the Entri MCP server so AI tools could handle domain connection and purchase without users leaving the chat. Today we're publishing new developer docs for teams that already run their own MCP server: Build Your Own MCP Tools for Domain Connection.

If your platform already has an MCP server, you can now add Entri domain connection to it directly, instead of asking your users to install a second server.

Why this matters for your platform

Custom domains are one of the stickiest features a SaaS platform can offer: when a customer's site, form or storefront lives on their own domain, it becomes part of their brand, and they are less likely to switch tools. But that value only shows up if the customer actually finishes setup. As more of your users start their work in an AI assistant, the domain step is now happening in chat, and an agent that can't complete it sends users back to a settings page they may never reach.

What your team gets

  • An AI experience that finishes the job. With domain connection as a tool, publishing is part of the same request, so more customers end up live on their own domain.

  • No new DNS logic to build or maintain. The tools run on the same Entri Connect flows, provider coverage and DNS records you already use in your app, so your agent gets the same setup experience your customers already trust.

  • A small, scoped project. Pre-built tools, one input and a complete TypeScript example in the docs. For a team that already runs an MCP server, it is a contained project rather than a platform rebuild.

What your users get

  • Less context switching. Users go from “put this on my domain” to a connected domain, guided by the agent from start to finish.

  • No DNS knowledge required. Entri detects their provider and applies the records after they sign in, so users never have to find a DNS settings page or copy a record by hand.

  • Their accounts stay private. Users sign in with their DNS provider through Entri and never share a password with an AI agent.

  • A faster path to launch. Their page, form or site is live on a domain they own in a few steps, while they're still in the flow of building it.

Two ways to put Entri in front of an agent

1. The hosted Entri MCP server. Point any MCP-compatible client at https://mcp.entri.com/mcp and your users get Entri Connect and Entri Sell as ready-made tools. Configuration lives in your Entri Dashboard under MCP Settings. Read the Entri MCP docs.

2. Your own MCP tools (new). Build connect_domain and get_domain_connection_status into the MCP server you already run, on top of Entri's Sharing Links API. Your server holds the Entri credentials, resolves the right DNS records for the current user, and decides exactly what the agent sees. Your users get one server, one sign-in, and one experience that feels entirely like your product.

See it in action: Typeform

Typeform Pages is a landing page builder you talk to. A user describes their business, for example "a page for my yoga studio, with three membership tiers and a sign-up form," and Typeform AI builds an on-brand page with the form already in place. Users can do the same from Claude, ChatGPT or any other AI assistant connected to the Typeform MCP server.

For Typeform, connecting a custom domain was the most technical step of a launch and the one customers understood least. The people building these pages are marketers, founders and event organizers, and most of them have never opened a DNS settings page. Inside the Typeform builder, Entri already handled this behind a "Connect domain" button. In a chat, there's no button to click, so an agent could build the whole page and then stall at the step people found hardest, right before going live.

Typeform's answer was to make the user's part as small as possible: one link. Typeform gave its agents the ability to request an Entri setup link, check when the domain is ready, and connect it to the page. Those abilities work in Typeform AI inside the product and in any AI assistant connected to the Typeform MCP server.

Here's what that looks like:

User: Put my spring launch page on launch.acme.com

Agent: I've added launch.acme.com to your account. To finish, open this link. It takes you to your domain provider and sets everything up for you: [Entri setup link]. Let me know when you're done.

User: Done!

Agent: launch.acme.com is ready and now shows your Spring Launch page.

Want the full story? In a guest post on our blog, Typeform's Pol Borrellas explains how Typeform built this flow: "Put this page on my domain": how we let AI agents set up custom domains with Entri. 

How it works

Typeform's flow follows the same pattern any platform can build: two tools, and the domain is the only input to either one.

  1. The user asks the agent to connect a domain. The agent calls connect_domain.

  2. Your server creates an Entri sharing link. It sends Entri the domain and the exact DNS records that user needs, then returns the link to the agent. The agent never edits DNS settings itself and never sees the user's login details.

  3. The user follows the link. Entri detects the DNS provider. If Entri can configure that provider, the user signs in and Entri applies the records. If not, the page shows the records to add by hand and links to your DNS help center article.

  4. The agent checks before it reports back. When the user says they're done, the agent calls get_domain_connection_status. If DNS hasn't propagated yet, it says so and offers the link again instead of claiming it worked. In Typeform's case, the agent then connects the page and confirms it's live.

What this opens up

Once domain connection is a tool your agent can call, it stops being a settings-page chore and becomes one step in whatever your users are trying to get done.

  • AI website and page builders. "Build me a landing page and publish it on my domain" becomes a single request, from first draft to live URL.

  • Vertical SaaS copilots. A booking platform's assistant can launch a salon's site on the owner's own domain while it sets up their services and hours.

  • Email and SMS platforms. The records your server passes are whatever your product needs, so an agent can walk a customer through authenticating a sending domain during onboarding.

  • Onboarding and support agents. When a customer gets stuck on setup, your support assistant can send them a connection link and confirm when it's done, without opening a ticket.

  • Multi-step agentic workflows. Domain connection becomes a checkpoint in a larger automation. The agent confirms the domain is connected before it moves on to the next step, like launching a campaign or publishing a store.

  • Fully in-chat manual setup. Before sending a link, your agent can check whether the user’s DNS provider supports automatic setup (via POST /checkdomain). If it does, the agent shares the Entri link. If it doesn’t, the agent walks the user through the records to add, using the setup guide you already have, without leaving the chat. Available on the Premium tier and above.

What you need to get started

  • Your Entri applicationId and secret from the Entri Dashboard (kept on your server)

  • Optionally, your DNS help center article for users who need to add records by hand

  • An MCP server. The developer docs include a complete TypeScript example, and the structure works with any MCP SDK.

The developer docs also cover testing, including how to use the MCP Inspector to check your tool list and call tools directly.

Read the docs

Already an Entri customer and want help scoping this for your platform? Reach out to your account team. New to Entri? Book a call and we'll walk you through it.