Xodia

Lets your AI build and edit websites in Xodia: read and write site files, create pages and CMS collections, run typecheck, design and link checks, take screenshots, manage forms and translations, and pick up change requests the user sends from the visual editor. Remote server at https://app.xodia.ai/mcp (Streamable HTTP, OAuth sign-in). Free plan, no card.

Hosted MCP Server

npx add-mcp 'https://app.xodia.ai/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

The MCP website builder: Xodia's MCP server

URL: https://xodia.ai/ai/mcp Description: Xodia is an MCP website builder: connect Claude, Cursor or any MCP client with OAuth, then build and edit your site. Setup, every tool, prompt and error. Last updated: 2026-11-16

Every plan

Xodia is a website builder your AI works in over MCP. Any MCP client connects to its remote server over Streamable HTTP, signs in with OAuth and gets 57 tools and 10 prompts to plan, build and edit real websites in Xodia. This page shows how to set it up, then lists every tool and prompt, with how sign-in works and what a failed call returns.

The full technical reference, kept up to date with every release, is in the docs: MCP server reference.

Start free Connect your AI

Free plan. No card needed.

Set it up

Connect your AI to Xodia in five steps

From sign-up to your first change, with any MCP app. Nothing to install or run on your computer.

  1. 1

    Create a Xodia workspace

    Sign up with GitHub, Google or email. You can connect your AI on every plan, Free included, with no card.

  2. 2

    Add the server to your AI app

    Add https://app.xodia.ai/mcp as a remote MCP server, with Streamable HTTP as the transport if your app asks. In Claude Code, Xodia's plugin adds it for you.

  3. 3

    Sign in and approve access

    Your app opens Xodia's sign-in page in the browser. Approve access and the app registers itself, so there is no key or client ID to copy.

  4. 4

    Open a project

    Ask your AI to list your projects or create a new one. It opens the project and gives you the link, so you can watch the live preview in Xodia while it works.

  5. 5

    Ask for a change and review it

    Describe what you want. Your AI reads the files, edits them, runs checks and takes screenshots. Its changes stay in Xodia for you to review, save and publish.

Steps for each app: Claude Code, the Claude app, Cursor, Codex and VS Code.

Every endpoint, tool, prompt and error code, for developers: the MCP server reference in the docs.

Connection

Endpoint and sign-in

Point your client at one address. It discovers the sign-in from the server's metadata, registers itself and asks you to approve access in the browser.

Endpoint

MCP server URL https://app.xodia.ai/mcp

Transport

Streamable HTTP. No local process to install or run.

Sign-in

OAuth 2.1 with the authorization code flow and PKCE (S256). Clients register themselves with dynamic client registration, so there is no client ID or key to copy. Registration /oauth/register Authorization /oauth/authorize Token /oauth/token Every path is on https://app.xodia.ai. Without signing in, a client can call initialize, tools/list and prompts/list to see what Xodia offers; the prompt list stays empty until it signs in. Every tool call needs sign-in: without it, the server answers 401 with the address of its sign-in metadata.

Discovery

Clients find the sign-in from the server's metadata: /.well-known/oauth-protected-resource /.well-known/oauth-authorization-server AI apps and directories can read the server card, with the server's name, endpoint and tools, at either address: /.well-known/mcp/server-card.json /.well-known/mcp.json

Listed in

Official MCP Registry, Glama and mcptry, as ai.xodia/xodia.

Scopes

xodia and offline_access. The second lets your client stay signed in without asking again.

Tokens

Access tokens last 1 hour; refresh tokens 60 days. Disconnect an app in Xodia at any time to end its access.

Plans

Free, Starter, Pro and Agency.

Tools

57 tools, in 17 groups

Tool names as your client lists them, with what each one does. Read only tools change nothing; for the ones marked destructive, clients that follow MCP's hints ask you first.

  • Projects

    • list_projects Read only Lists your workspace's website projects and when each was last opened.
    • create_project Starts a new website from the Xodia template (Vite, React Router and Tailwind v4) or as plain HTML on Vite.
  • Workspace and preview

    • open_workspace Opens the project and shares its Xodia link; the preview runs in your browser, with nothing to wait for.
    • get_project Read only Reads the site's framework, styling, CMS, host, editing tier, branch and the files changed since the last restore point.
  • Files

    • list_files Read only Lists the project's files with their sizes.
    • read_file Read only Reads a file, with line numbers.
    • write_file Destructive Creates or replaces a file.
    • edit_file Destructive Changes part of a file by exact replacement, so edits stay small and safe.
    • search_files Read only Searches the code for text or a pattern.
    • delete_file Destructive Deletes a file or folder.
    • move_file Destructive Moves or renames a file or folder.
    • copy_imported_images Copies the images an imported website saved into the project you rebuild it in, at the same paths.
  • Checks and logs

    • run_check Read only Runs a typecheck, a production build or a design check (design tells, low contrast, over-long lines, motion that stutters or ignores the visitor's motion setting) and reports every finding.
    • get_logs Read only Reads the preview's log: bundle and page errors.
    • get_match_report Read only Reads how close each page Convert to React made is to your live site: the match, colours and images, and the weakest sections with the reason.
    • check_match Read only Measures one page again against your imported site after a change, so your AI sees which sections rose or dropped.
  • Selection

    • get_selection Read only Gets the element you selected in Xodia, with its place in the source.
  • Checkpoints

    • save_checkpoint Destructive Takes a restore point of the site, when you ask it to. Changes are saved without it.
    • list_checkpoints Read only Lists restore points, newest first.
    • restore_checkpoint Destructive Takes the site back to an earlier restore point without losing current work.
  • Requests from Xodia

    • get_next_request Waits for the next change you ask for in Xodia and picks it up.
    • reply_to_request Posts progress and the result back to you in Xodia.
    • get_request Read only Checks a request's status, so cancelled work is dropped.
  • Review comments

    • list_comments Read only Reads your team's review comments with their page, screen size and element, so your AI checks each one at the right size.
    • reply_to_comment Answers a review comment as your AI. Only a person resolves it.
  • Site plan

    • get_site_plan Read only Reads your site plan: brand, audience, pages and the sections on each, navigation and motion, with each page's progress, plus Xodia's section layouts and page templates.
    • update_site_plan Destructive Writes the site plan, checked before it is saved; each page's progress is read from the site, so your AI rarely sets it by hand.
    • sync_site_plan Destructive Brings the site plan in line with the site: new pages and sections join the plan, and anything that would drop your intent waits for your review.
    • study_reference_site Read only Reads an inspiration site from your plan for your AI: its structure, colours, fonts, layout and how it moves, as direction only, never to copy.
  • CMS

    • list_collections Read only Lists the site's CMS collections with their fields and item counts.
    • get_collection Read only Reads one CMS collection: its fields, settings and collection page.
    • create_collection Adds a CMS collection, such as blog posts or team members, with the fields you need.
    • update_collection Destructive Changes a CMS collection's name, settings or fields.
    • list_items Read only Lists the items in a CMS collection, with search and filters, in any of the site's languages.
    • get_item Read only Reads one CMS item with all its fields, in any of the site's languages.
    • create_items Adds one or more items to a CMS collection.
    • update_item Destructive Changes the fields of a CMS item, or its translation in another language.
    • delete_items Destructive Deletes CMS items.
  • Forms

    • list_forms Read only Lists the site's Xodia Forms with their fields, recipients, settings and this month's messages.
    • connect_form Connects a form on the site to Xodia Forms, so its messages arrive in the Content tab and by email.
    • list_submissions Read only Reads the messages visitors sent through the site's forms, newest first, for members only; read only.
  • Languages

    • list_locales Read only Lists the site's languages, their addresses and translated counts, and how many languages the site may have.
    • get_translations Read only Shows what a page or CMS collection still needs in a language, with each text and its translation.
    • set_translations Destructive Writes the translations your AI made for a language, page texts and CMS items, saved at once for you to check.
  • Pages and folders

    • list_pages Read only Lists the site's pages and folders, like the Pages panel.
    • create_page Adds a page, inside a folder if you like, or a folder's own page.
    • move_page Destructive Moves a page to a new address, with a redirect from the old one and its links updated.
    • delete_page Destructive Deletes a page and its route, and lists the links that still point to it. A dry run shows what would go first.
    • create_folder Adds a folder to group pages under one address.
    • update_folder Destructive Renames a folder or moves it, and every page in it, to a new address.
    • delete_folder Destructive Deletes a folder, keeping its pages or removing them too.
  • Skills

    • get_skill Read only Loads one of Xodia's skills for the work at hand.
  • Deploys

    • deploy_status Read only Shows the latest deploy on your host: state, address and log link.
    • deploy_logs Read only Reads a failed build's log so your AI can fix it.
  • SEO and speed

    • run_seo_test Tests a live page with Google PageSpeed Insights: scores, Core Web Vitals and failed checks.
    • get_seo_report Read only Reads the latest PageSpeed result without using a test.
  • Screenshots

    • take_screenshot Read only Captures the live preview in a real browser, at desktop or phone size, with console errors, and can measure how smoothly the page animates.

Prompts

10 prompts to start from

Clients that support MCP prompts list these, each with an argument for what you want. In Claude Code, Xodia's plugin turns them into /xodia commands.

  • build <what to build> Build or redesign a Xodia website from a description
  • work [project name] Listen for change requests from Xodia and work through them
  • animate <what should move, and when> Add interactions and animation to a Xodia site: hover, reveals, scroll effects, page transitions
  • content <what to add or change> Add or change CMS content and collections on a Xodia site: posts, projects, team, drafts
  • polish [page, section or component] Give a Xodia page or component a finishing pass on the small design details
  • tidy [project name, and anything to leave alone] Tidy a Xodia site: fix its layout and text, keep the design, check every page and report what changed
  • fix [what looks wrong] Find and fix what's broken in a Xodia preview
  • review [project name] Review a Xodia project's draft changes before saving or publishing
  • seo [page or goal] Check and improve a Xodia site's SEO and AI search readiness
  • speed [page] Make a Xodia site load faster

Requests

Request kinds and the skills they load

Requests sent from Xodia's ask box arrive through get_next_request with a kind. Each kind names the skills to follow; your client loads them with get_skill. The skills are written by developers with 18+ years of building websites.

Stack pack skills for the site's framework, styling, app tools, CMS and host load the same way; CMS and host packs come with Starter, Pro and Agency.

  • Auto (auto) Let the agent decide. Skills: Request router, Guardrails.
  • Content (content) Wording, images, links. Skills: Content changes, CMS content, Copywriting, Site linking, Page settings, Languages and regions, Image optimiser, Finish a site from an AI builder, Safe edits, Verify, Site memory (AGENTS.md).
  • Design (design) Look and layout. Skills: Design system, Colour and themes, Extract design tokens, Accessibility, App screens, Interactions, SVG animation, Matching art, Icons, Navigation, Fonts, favicon and 404, Image optimiser, Polish, Tidy a site, Finish a site from an AI builder, Safe edits, Verify, Design critique, Site memory (AGENTS.md).
  • Page (page) New or restructured pages. Skills: Plan and confirm, Design direction, New page, Rebuild an imported site, Tidy a converted site, Finish a site from an AI builder, New section, Section layouts, Components, Navigation, Forms, App screens, App data, Languages and regions, Fonts, favicon and 404, Draft pages, Page settings, Redirects and retired pages, Design system, Colour and themes, Icons, Matching art, UI states, Image optimiser, Copywriting, SEO basics, Site linking, Safe edits, Verify, Design critique, Site memory (AGENTS.md).
  • Fix (fix) Something is broken. Skills: Visual fixer, App data, Environment and hosts, Analytics and scripts, Image optimiser, Safe edits, Verify, Site memory (AGENTS.md).
  • Ask (question) A question, no changes. Skills: Request router.

Errors

Errors come back as tool results, with a hint

A failed call doesn't break the session. It returns a normal tool result marked as an error, with a JSON error object your AI can read and act on.

code

A short machine name for what went wrong, such as a plan limit or a file that isn't there.

message

What went wrong, in plain words.

hint optional

What to do next, written for your AI: retry, pick another project, ask you to upgrade or publish first.

action optional

What you can do about it in Xodia, such as upgrading or signing in again.

details optional

Extra facts about the failure, such as the limit that was reached.

retryable optional

Present and true when the same call may work if tried again.

What reply_to_request returns when another app has already taken the request:

{
  "error": {
    "code": "request_claimed",
    "message": "Another agent has taken over this request.",
    "hint": "Stop working on it and call get_next_request."
  }
}

Primary sources

Official docs

Updated November 13, 2026

Questions

MCP questions

What is an MCP website builder?

A website builder that an AI app can work in through the Model Context Protocol. In Xodia, your AI reads and edits your site's real code, runs checks and takes screenshots through Xodia's MCP tools, while you watch the live preview and edit visually yourself.

How do I connect my AI to Xodia?

Add https://app.xodia.ai/mcp to your AI app as a remote MCP server, then sign in to Xodia when it asks. The five steps above cover it, and each AI app's page has its exact steps.

Do I need to install anything?

No. The server runs on Xodia, and your AI app connects to it over the internet. In Claude Code you can add Xodia's plugin, which sets up the server and adds the /xodia commands.

Can I connect on the Free plan?

Yes. MCP access comes with every plan, Free included, within each plan's limits. Your AI's own usage is on your plan with that AI app. See pricing.

Do I need an API key?

No. Clients sign in with OAuth and register themselves, so there is no key or client ID to create or paste.

Does my client need to support OAuth?

Yes. Without signing in, a client can only see the list of tools. Every tool call needs a signed-in client, and signing in goes through OAuth in your browser.

Which clients have setup steps?

Xodia's own setup guide covers Claude Code, the Claude app, Cursor, Codex and VS Code. Any other client that speaks Streamable HTTP with OAuth connects the same way.

Can my client publish the site?

No. Tools edit files as changes kept in Xodia and save restore points when you ask. Saving to the live branch of a site imported from GitHub is protected, and you deploy from Xodia yourself.

How do I disconnect an AI app?

Every app you connect is listed under Connected apps in Xodia. Disconnect one there at any time to end its access.

Keep exploring

Other ways to connect

Connect your MCP client and start editing.

Start free See pricing