Mythex

ai.mythexPublished by mythex.aiOfficial publisherv1.1.0Updated Oct 31, 2026

Build and publish web, Android and iPhone apps from your AI client, in Arabic, English and 60+ more.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Mythex lets an AI client build and publish web, Android and iPhone apps, with support for Arabic, English and 60+ more languages.

What you can do
  • Build web, Android and iPhone apps from within an AI client.
  • Publish the resulting apps.
  • Work in Arabic, English and more than 60 other languages.
When to use it
Useful when you want an assistant to take an app idea through building and publishing for web and mobile without leaving the chat client, including for Arabic or other non-English projects.
Requirements
A remote MCP endpoint at mcp.mythex.ai over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Publishing apps is an outward-facing action that may make content public, so review what is released. The server requires OAuth authorization of a Mythex account; no pricing or data-handling details are provided in the listing.

Installation

In SourceWeft

  1. Open Mythex 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.mythex%2Fmythex/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": {
    "mythex": {
      "type": "http",
      "url": "https://mcp.mythex.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

2
  1. v1.1.0LatestOct 31, 2026
  2. v1.0.0Sep 20, 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.