Xodia

ai.xodiaPublished by xodia.aiOfficial publisherv1.0.0Updated Nov 8, 2026

Build and edit your website in Xodia, a visual website builder for real code (Vite, React, HTML).

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Xodia is a remote MCP server that lets an assistant build and edit a website in a visual website builder that outputs real Vite, React or HTML code.

What you can do
  • Build and edit a website inside the Xodia visual builder.
  • Work with real code output such as Vite, React and HTML.
  • No tool list is published, so the exact actions the assistant can take are not documented in the supplied material.
When to use it
Consider it when you want an assistant to help create or modify a website through Xodia's visual builder rather than by hand-editing files.
Requirements
A remote MCP endpoint at app.xodia.ai over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Xodia account, and the assistant can change website content, so review edits before publishing. No tool list is published, so confirm what it can modify before connecting.

Installation

In SourceWeft

  1. Open Xodia in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.xodia%2Fxodia/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "xodia": {
      "type": "http",
      "url": "https://app.xodia.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 8, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.