lindo.ai
MCP (Model Context Protocol) server for Lindo AI — create websites, pages, and blog posts with AI directly from Claude, Cursor, Kiro, Windsurf, and other…
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Get Workspace: Get details about the current Lindo AI workspace (business name, plan, language, integrations).
- Update Workspace: Update workspace-level settings. Only provided fields are changed.
- Get Workspace Analytics: Get aggregated analytics across all websites in the workspace.
What data it sees
Do you need an account
No: the server works without sign-in
MCP (Model Context Protocol) server for Lindo AI — create websites, pages, and blog posts with AI directly from Claude, Cursor, Kiro, Windsurf, and other MCP-compatible tools.
How to connect
How to connect lindo.ai to Claude
The server address to paste into Claude settings:
https://lindoai.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect lindo.ai to ChatGPT
The server address to paste into ChatGPT settings:
https://lindoai.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect lindo.ai to Cursor
The server address to paste into Cursor settings:
https://lindoai.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (52)
Raw names from tools/list. Only developers need these.
| get_workspace | Get details about the current Lindo AI workspace (business name, plan, language, integrations). |
| update_workspace | Update workspace-level settings. Only provided fields are changed. |
| get_workspace_analytics | Get aggregated analytics across all websites in the workspace. |
| get_workspace_team | List workspace team members (owners, team collaborators). |
| add_workspace_team_member | Invite a new team member to this Lindo workspace. Creates a team record and sends a transactional invitation email from Lindo to the provided address. The email contains a link to accept the invite and join the workspace. It is not a marketing or cold email; the tool should only be used when the user clearly intends to grant an individual access. |
| remove_workspace_team_member | Remove a team member from the workspace. Revokes their access. |
| create_client | Create a new client record in the workspace. Only "name" is strictly required; if "email" is omitted, a placeholder address is generated so the record can be created. This tool does not send any email — use generate_magic_link separately if you need to share login access with the client. |
| list_clients | List clients in the workspace, paginated. Returns a `{ list, total }` result where `list` holds up to 12 items. Use `total` (the true, filter-aware count) with the `page` argument to fetch additional pages. |
| update_client | Update fields on an existing client. Only provided fields are changed. |
| delete_client | Delete a client. This cannot be undone. |
| assign_website | Assign an existing website to a client (grants them access). |
| generate_magic_link | Generate a short-lived magic login link for a client. The link authenticates the client into the Lindo app without a password and expires automatically. |
| create_website | Start an AI-generated website workflow. This is asynchronous — the tool returns a `record_id` immediately. Poll `check_website_status` with that `record_id` to track progress and get the final result. Optionally assigns the website to an existing or new client. |
| list_websites | List websites in the workspace, paginated. Returns a `{ list, total }` result where `list` holds up to 12 items. Use `total` (the true, filter-aware count) with the `page` argument to fetch additional pages. |
| get_website | Get full details for a single website (business info, theme, domain, activation state). |
| update_website | Update a website's business name and/or description. |
| delete_website | Delete a website. This cannot be undone. |
| update_website_settings | Update structured website settings (business info, theme, robots.txt, socials, custom header/footer code). |
| add_custom_domain | Attach a custom domain to a website (user is responsible for DNS configuration). |
| remove_custom_domain | Remove the custom domain from a website. The site reverts to its default Lindo subdomain. |
| get_website_team | List collaborators with access to a specific website. |
| get_website_analytics | Get analytics (visits, traffic sources, top pages) for a website. |
| create_page | Start an AI-generated page workflow for an existing website. This is asynchronous — the tool returns a `record_id` immediately. Poll `check_page_status` with that `record_id` to track progress and get the final result. |
| list_pages | List pages on a website, paginated. Returns a `{ list, total }` result where `list` holds up to 12 items. Use `total` (the true, filter-aware count) with the `page` argument to fetch additional pages. Only pages created via the API/SDK are returned. |
| get_page | Get details for a single page. |
| update_page | Update page metadata (display name, URL path, SEO). Only provided fields change. |
| delete_page | Delete a page. This cannot be undone. |
| publish_page | Publish a static HTML page at a given path. If a page already exists at that path it will be OVERWRITTEN — any existing content is replaced. |
| update_page_content | Replace the HTML content of an existing page. This overwrites the previous HTML entirely; the prior content is not preserved. Optionally updates SEO metadata. |
| unpublish_page | Unpublish a page so it is no longer publicly accessible. |
| get_page_html | Return the raw HTML of a page. |
| create_blog | Start an AI-generated blog post workflow for an existing website. This is asynchronous — the tool returns a `record_id` immediately. Poll `check_blog_status` with that `record_id` to track progress and get the final result. |
| publish_blog | Publish a new markdown blog post at a given path. |
| list_blogs | List blog posts on a website, paginated. Returns a `{ list, total }` result where `list` holds up to 12 items. Use `total` (the true, filter-aware count) with the `page` argument to fetch additional pages. Only blog posts created via the API/SDK are returned. |
| get_blog | Get details for a single blog post. |
| update_blog | Update blog post metadata (name, path, SEO). |
| delete_blog | Delete a blog post. This cannot be undone. |
| update_blog_content | Replace the markdown content of an existing blog post. This overwrites the previous markdown entirely; the prior content is not preserved. Optionally updates SEO and blog settings. |
| unpublish_blog | Unpublish a blog post so it is no longer publicly accessible. |
| get_blog_html | Return the rendered HTML of a blog post. |
| check_website_status | Poll the status of a website-creation workflow started by `create_website`. Pass the `record_id` you received from that tool. While the workflow is running, call this tool again after `poll_after_ms` milliseconds. Once `done` is true, `status` is `complete` (all pages generated), `partial` (some pages failed), or `errored`. `result.pages` lists every page (home + additional) with its individual status. |
| check_page_status | Poll the status of a page-creation workflow started by `create_page`. Pass the `record_id` you received from that tool. While the workflow is running, call this tool again after `poll_after_ms` milliseconds. Once `done` is true, `status` is `complete` or `errored`; when complete, `result` holds the published page info. |
| check_blog_status | Poll the status of a blog-creation workflow started by `create_blog`. Pass the `record_id` you received from that tool. While the workflow is running, call this tool again after `poll_after_ms` milliseconds. Once `done` is true, `status` is `complete` or `errored`; when complete, `result` holds the published blog info. |
| batch_create_websites | Start up to 25 website-creation workflows in one request. Returns one `record_id` per item. Poll the combined status with `batch_check_website_status`, or the individual statuses with `check_website_status`. |
| batch_create_pages | Start up to 25 page-creation workflows on a single website in one request. Returns one `record_id` per item. Poll with `batch_check_page_status` or `check_page_status`. |
| batch_create_blogs | Start up to 25 blog-creation workflows on a single website in one request. Returns one `record_id` per item. Poll with `batch_check_blog_status` or `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_check_page_status | Poll up to 25 page-creation workflows at once. Returns a rollup `status` plus a per-item array with the same shape as `check_page_status`. |
| 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`. |
| get_credits | Get the workspace's current Lindo credit balance and utilization. |
| get_client_credits | Get the credit balance allocated to a specific client. |
| allocate_credits | Re-allocate existing workspace-owned Lindo credits to a client. This never purchases credits; it only moves balance you already own. |