Reviews
No review yet. Used Xodia? Be the first to help others choose.What it does
Xodia is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2d ago (live check)Hosted endpoint
https://app.xodia.ai/mcpstreamable-http
In Claude Code: claude mcp add --transport http xodia https://app.xodia.ai/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"xodia": {
"url": "https://app.xodia.ai/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2d agoONLINE Xodia answered an MCP connection on 14 Nov 2026 and introduced itself as xodia 0.1.0 (MCP protocol 2025-06-18).
55 tools offered to AI assistants
list_projects· Lists the user's website projects on this Xodia host (named on the first line) with when each was last opened. Projects marked locked are past the plan's project limit and can't be opened or edited; pick an open one or ask the user to upgracreate_project· Creates a new website project. Xodia supports React + Vite and plain HTML sites: by default it starts from the Xodia template (React + Vite: Vite + React Router + Tailwind v4); `template` "html-vite" starts a plain HTML site with Vite insteopen_workspace· Opens the project for work and returns the Xodia link to share with the user. It is ready at once: the site runs in the user's browser, so there is nothing to start or wait for.list_files· Lists project files with their sizes, one per line as "path (12.3 KB)" (respects .gitignore; up to 1000 files). Optional glob like src/**/*.tsx or public/**/*.{png,jpg}.read_file· Reads a text file with line numbers. Use offset/limit (1-based lines) for long files. The last line gives the file's version: pass it as base to write_file or edit_file so a write is refused if someone changed the file after your read.write_file· Creates or overwrites a file with the full content. Prefer edit_file for changes to existing files. Pass base (the version read_file gave) when overwriting a file you read, or null for a file that must not exist yet: if the file changed meaedit_file· Replaces old_string with new_string in a file. old_string must match exactly (including whitespace) and be unique unless replace_all is true. Pass base (the version read_file gave) to have the edit refused with file_changed if someone changsearch_files· Searches file contents with a regular expression (ripgrep). Returns path:line: text.delete_file· Deletes a file or folder from the project.move_file· Moves or renames a file or folder.run_check· Runs "typecheck" (TypeScript, fast), "build" (production build, slower), "design" (instant static scan for design tells: px sizes, gradient text, purple gradients, emoji or text-glyph icons, transition-all, scale(0) entrances, missing focusget_logs· Returns the end of the preview's log: the bundle and page errors of the preview open in Xodia, or of Xodia's headless browser when nobody has it open. If it answers that it needs the project open in Xodia, ask the user to open it and don't
Show 43 more
get_selection· Returns the element the user selected in the Xodia preview (source file:line:column, tag, text, route, seconds since it was selected). On a Sass or CSS-in-JS site it also lists the element's styles linked to a site setting, theme value or pget_project· What Xodia knows about a project: the Xodia host it lives on (xodiaHost), how its preview runs (preview), framework, styling, CMS, host, editing tier, the branch the workspace has open, whether that branch is view only on the workspace's plsave_checkpoint· Takes a restore point: commits every change on the branch since the last one, like Push to Git in Xodia (a site imported from GitHub gets it pushed to its repo). Changes are already saved without it, so call it only when the user asks for alist_checkpoints· Lists restore points, newest first.restore_checkpoint· Returns the site to an earlier restore point (list_checkpoints). Changes made since the last restore point become a restore point of their own first, so nothing is lost.get_next_request· Waits for the next change the user asked for in Xodia (up to wait_seconds) and claims it. Do the work, then call reply_to_request. Call again to keep listening.reply_to_request· Posts a message to the user in Xodia for a request. Use status "working" for progress updates, "done" when finished, "failed" if you tried and could not finish (say why). Leaving it unchanged on purpose because a rule says so is "done", witget_request· Current status of a request. Call before save_checkpoint: if the user cancelled it, drop the work and take the next request.list_comments· Lists review comments people left on the site in Xodia, newest change first, as text: each thread's id, page, screen size (with the canvas width and which take_screenshot viewport to check it at), the element it is on (source, tag and text)reply_to_comment· Replies on an open review thread from list_comments, as the user's AI (Xodia shows "AI for" the user). Use it to answer a question or say what you changed, in plain words for the site owner (no file paths or code). To mention a workspace meget_site_plan· Reads the site plan (.xodia/plan.json) on a branch: a short summary (title, pages by status, the sitemap tree with each page's status and section count, the shared nav and footer, motion, inspiration sites still to study, pages changed sincupdate_site_plan· Writes the site plan (.xodia/plan.json) on a branch, saved at once like every edit. Send one of: plan with the whole plan or only the top-level fields you change (brief, inspiration, brand, audience, goals, motion, sitemap, pages, globals,sync_site_plan· Brings the site plan (.xodia/plan.json) in line with the site on a branch and writes it, the same as the Plan tab's sync. Xodia reads the site's files (the latest edits included): pages and their paths, the top-level sections on each page bstudy_reference_site· Reads one inspiration site from the project's site plan for you and returns a compact study: title, meta description, headings outline, navigation labels, a short text sample, declared colours (theme-color, CSS custom properties) and the mocopy_imported_images· Copies the images a site made with Import a website saved under public/ (a project with IMPORTED.md) into the project you are rebuilding it in, at the same paths, so /assets/... image URLs keep working. Without paths it copies every image tget_skill· Returns one of Xodia's skills (step-by-step instructions for a kind of work) for the project you are working on: core skills, plus the stack packs get_project lists for that project. Requests, prompts and the router name the skills and packlist_collections· Lists the site's Xodia CMS collections (content/<id>/collection.json) with their item counts, item URLs and fields, other content the Content tab reads another way (folders, data/, Decap), whether the site has the CMS kit, the plan's CMS liget_collection· Reads one collection: its settings (name, singular, plural, URL folder, sort), groups, every field with its type, rules and options, the collection page settings (SEO and share templates, JSON-LD, custom code), the item count, the CMS kit screate_collection· Creates a collection: from blank (a required Title field) or a starter (Blog posts, Projects, Team, Products, Events, Jobs, Testimonials, FAQ, with fields and sample items), plus extra fields and page settings. On a Xodia template or Vite Rupdate_collection· Changes a collection: settings (name, singular, plural, urlFolder, which moves the item pages with their route, the links to them and redirects for published ones, reservedSlugs, sort, manualOrder, groups, translatable and translatedOnly folist_items· Lists a collection's items with search (q), status, filters (field, op eq, ne, contains, set or unset, value) and sort ("-publishedAt"), a page at a time (pageSize up to 100), with the total. Long text is cut: get_item reads one whole. Drafget_item· Reads one item whole: slug, status, dates, order and every value, with its file path. With locale: the item in that language (translations over the default values), its translation file and state, which fields are translatable and which sticreate_items· Creates up to 50 items in one call, each checked against the collection's fields (required, types, options, validation, references to existing items or items in this call). Items that fail are listed with their index and field problems andupdate_item· Changes one item: values (only the ones you send; null or "" clears one), newSlug (renames the file and its URL), draft (false publishes it with the site), publishedAt, order. Checked against the fields like create_items; a wrong type is redelete_items· Deletes up to 100 items by slug; slugs not found are listed. Confirm with the user before deleting content they wrote. Writes go to the branch the workspace has open, the same as the Content tab. Saved at once, like every edit in Xodia; puslist_pages· Lists the site's pages and folders on a branch: each page's address, file and whether it has a variable part (collection pages and other :slug routes), each folder (explicit or from page addresses and collection URL folders) with its name,create_page· Adds a page the way the Pages panel does. On a Xodia template site: a page file that mirrors its folders (src/pages/services/web/Design.tsx) and its route in src/routes.tsx at /<parent>/<slug>, inside the site's layout, with a starter sectimove_page· Moves or renames a page (another folder, another slug, or both) in one change: its route, its file on template sites (src/pages mirrors the folders, imports follow) and plain HTML sites (<slug>/index.html or <name>.html), every internal lindelete_page· Deletes a page the way the Pages panel does, in one change: its route (src/routes.tsx on a Xodia template site, the routes file on a React site with routes in code) and its file unless another route uses it, or its .html file on a plain HTMcreate_folder· Creates an empty folder (an address segment such as /services; a folder is not a file), kept in .xodia/folders.json so it shows in the Pages panel and the plan before any page is in it. Folders that pages or collections use exist without thupdate_folder· Renames a folder (name) or moves it (to: a new slug or parent), with everything under it in one change: every page's route and file, sub folders, collections whose URL folder is inside it, the internal links to all of them, redirects for thdelete_folder· Deletes a folder. An empty one just goes; one with pages is refused (folder_not_empty, listing them) unless withPages is true, which deletes every page under it with its route and file (template sites; ask the user first, and dryRun lists tlist_locales· Lists the site's languages (Xodia Languages): whether languages are set up, the default language, every other language with its code, name, direction (ltr or rtl), address prefix (/<code>/) and how many texts are translated, translated pageget_translations· Reads what a language still needs, for one page or one CMS collection. page: the page is rendered in that language in a real browser and every translatable text on it comes back as { text, translation }, translation null where it is missingset_translations· Writes translations for one language, the same as typing on the canvas in that language. Saved at once, like every edit in Xodia; pushing to Git and publishing stay the user's. entries: page texts, each { text, value } with text exactly aslist_forms· Lists the site's Xodia Forms (forms that post to Xodia, whose messages the owner reads in the Content tab): each form's id, name, status (active or paused), the file and line it is in, recipients, the Turnstile spam check, notifications (eaconnect_form· Turns a form in the site's code into a Xodia form, the same way as Send to Xodia Forms in Xodia's Settings panel: it writes action, method="post", data-xodia-form, success and error text, a hidden spam field and the page field onto the formlist_submissions· Reads the messages visitors sent through the site's Xodia forms, newest first, a page at a time (up to 50; pass nextCursor for older ones): each message's form, fields, page, when it came and whether it is read or spam. Spam is left out unldeploy_status· The latest deploy on the site's host (Vercel, Netlify, Cloudflare) for a branch: state, address and log link. Check it after the user publishes. Each row is one check (a Worker, a Pages project, Vercel, Netlify or CI); a failed one includesdeploy_logs· The last lines of a Cloudflare Workers Builds, Vercel or Netlify build log (deploy id from deploy_status). Use it to fix a failed build; the fix goes live when the user publishes again. Needs a plan that includes host connections.run_seo_test· Tests a live page with Google PageSpeed Insights: SEO, performance, accessibility and best practices scores, Core Web Vitals and the failed checks. Uses one of the workspace's monthly SEO tests, so run it once before fixing and once after tget_seo_report· Reads a PageSpeed Insights result without using a test: the latest finished test of the project (or of url), or a given runId (for example one run_seo_test or a Fix with AI request named). Returns scores, Core Web Vitals and the top failedtake_screenshot· Renders a page of the preview in a real browser and returns the image plus any console errors. Use it to check your work visually, at mobile size too. Pages are rendered by Xodia's headless browser within a monthly allowance. When it answer
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://app.xodia.ai/mcp | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Website | https://xodia.ai/ai/mcp | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| Version | 1.0.0 | DECLARED | SRC-001 Official MCP Registry | 13h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 13h ago |
Change history
- NEW08 Nov 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Xodia still online?
Free alerts · no account▲ 0Do you run Xodia? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Xodia
How do I connect Xodia?
Use the hosted endpoint https://app.xodia.ai/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Xodia offer?
When Electra Index connected on 14 Nov 2026, it listed 55 tools: list_projects, create_project, open_workspace, list_files, read_file, write_file, edit_file, search_files and more. The full list is in "Live check" above.
Is Xodia online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2d ago.