add_custom_domain
Add a custom domain to a website.
LABSCO SUMMARY
Magic links for client access is the tell that this is built for agencies — the hardest part of client work is showing someone their site without onboarding them.
Agency platforms live or die on the client handoff, and requiring every client to create an account is where most of them lose. Generating a magic login link per client sidesteps it entirely. The other structurally right decision is separating publish from update: publish_page and unpublish_page exist alongside update_page_content, so changing a page and making it live are different acts rather than one implicit one. Note that the AI build and edit tools are asynchronous — an agent calling create_website and reporting success has reported a job starting, not a site existing.
What it is
An agency-oriented website platform client with four layers: the workspace and its team, clients and their access, websites created and edited by AI, and the pages, domains and analytics under each.
What you get
- create_website and edit_website both start asynchronous AI workflows rather than returning a finished site, so building is a job you track.
- Clients as first-class objects — created, listed, updated, deleted — with assign_website linking a site to one and generate_magic_link producing access without provisioning an account.
- Pages with a real publishing lifecycle: list, get, update metadata, publish a static page with HTML content, update content in place, unpublish, and delete.
- Custom domains added and removed per website, and website settings updated separately from website details.
- Analytics at two levels — workspace-wide and per website — so an agency view and a client view are both available.
- Team membership managed at both workspace and website scope.
Requirements
LINDO_API_KEY. Website creation and editing are asynchronous workflows, so those calls return something to track rather than a finished result.
Setup effort
One command plus a key — npx -y @lindoai/mcp-server, then supply credentials
USE CASES
01
Building a site from a brief
Start the AI creation workflow and track the job, rather than treating the call's return as a finished site.
02
Getting a client into their own site
Create the client, assign the website, and generate a magic link so they can see it without an onboarding flow.
03
Changing a page and deciding when it goes live
Update the content, then publish it as a separate act — and unpublish rather than delete when something needs to come down temporarily.
04
Putting a site on the client's own domain
Add the custom domain to the website and adjust the site settings around it.
05
Reporting on how sites are performing
Read the per-website analytics for a client conversation and the workspace analytics for your own.
06
Managing who works on what
Add and remove team members at workspace level, and read the team assigned to a specific website.
50 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_workspace_team_member
Add a team member to the workspace.
allocate_credits
Allocate credits to a client.
assign_website
Assign a website to a client.
batch_check_blog_status
Poll up to 25 blog-creation workflows at once. Returns a rollup status plus a per-item array with the same shape as check_blog_status.
batch_check_website_status
Poll up to 25 website-creation workflows at once. Returns a rollup status (scheduled/running/complete/partial/errored) plus a per-item array with the same shape as check_website_status.
batch_create_blogs
Start up to 25 blog-creation workflows on a single website in one request. Returns one workflow_id per item. Poll with batch_check_blog_status or check_blog_status.
batch_create_websites
Start up to 25 website-creation workflows in one request. Returns one workflow_id per item. Poll the combined status with batch_check_website_status, or the individual ones with check_website_status.
check_blog_status
Poll the status of a blog-creation workflow started by create_blog. Pass the workflow_id you received from that tool. While running, call this again after poll_after_ms ms. Once done is true, status is complete or errored; when complete, result holds the published blog info.
check_edit_status
Poll the status of a website-edit workflow started by edit_website. Pass the workflow_id you received from that tool. While running, call this again after poll_after_ms ms. Once done is true, status is complete or errored; when complete, result holds the changed pages.
check_website_status
Poll the status of a website-creation workflow started by create_website. Pass the workflow_id you received from that tool. While the workflow is running, call this again after poll_after_ms ms. Once done is true, status is complete (all pages generated), partial (some failed), or errored. result.pages lists every page (home + additional) with its individual status.
create_blog
Create an AI-generated blog post on a website. Starts an asynchronous workflow and returns a workflow_id immediately — poll check_blog_status with that id to track progress and get the final result.
create_client
Create a new client in the workspace.
create_website
Create a new website using AI. Starts an asynchronous workflow and returns a workflow_id immediately — poll check_website_status with that id to track progress and get the final result. Optionally assign to a client by providing client_id (existing) or client_email (lookup or create new).
delete_blog
Delete a blog post from a website.
delete_client
Delete a client from the workspace.
delete_page
Delete a page from a website.
delete_website
Delete a website from the workspace.
edit_website
Edit an existing website (across its pages) using AI. Starts an asynchronous workflow and returns a workflow_id immediately — poll check_edit_status with that id to track progress and get the final result.
generate_magic_link
Generate a magic login link for a client.
get_blog
Get blog post details.
get_blog_html
Get the HTML content of a blog post.
get_client_credits
Get client credit balance.
get_credits
Get workspace credit balance.
get_page
Get page details.
get_page_html
Get the HTML content of a page.
get_website
Get website details.
get_website_analytics
Get website analytics.
get_website_team
Get website team members.
get_workspace
Get workspace details.
get_workspace_analytics
Get workspace analytics.
get_workspace_team
Get workspace team members.
list_blogs
List all blog posts on a website.
list_clients
List all clients in the workspace.
list_pages
List all pages on a website.
list_websites
List all websites in the workspace.
publish_blog
Publish a static blog post with markdown content.
publish_page
Publish a static page with HTML content.
remove_custom_domain
Remove a custom domain from a website.
remove_workspace_team_member
Remove a team member from the workspace.
unpublish_blog
Unpublish a blog post from a website.
unpublish_page
Unpublish a page from a website.
update_blog
Update blog post metadata.
update_blog_content
Update the content of an existing blog post.
update_client
Update an existing client.
update_page
Update page metadata.
update_page_content
Update the content of an existing page.
update_website
Update website details.
update_website_settings
Update website settings.
update_workspace
Update workspace details.
BEFORE YOU INSTALL
What to know first
Tools you get
50 tools when we connected. The documentation covers only ten tools; pages, most blog tools, custom domains, workspace management and every delete are available but undocumented. The API key requires a Business or Whitelabel plan.
Requires
- npx on PATH
- LINDO_API_KEY in your environment
Where it runs
Of the 6 documented clients, 5 run the server on your machine and 1 connects to a hosted endpoint.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 50 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @lindoai/mcp-serverHosted endpoint
Any MCP client — remote
ENDPOINT URL
https://mcp.lindo.ai/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Claude Desktop, Claude Code, Cursor, Kiro, Windsurf
JSON
{
"mcpServers": {
"lindo": {
"command": "npx",
"args": [
"-y",
"@lindoai/mcp-server"
],
"env": {
"LINDO_API_KEY": "<YOUR_LINDO_API_KEY>"
}
}
}
}
