Your idea.
An Android app.
One conversation.

From an idea to a working starting point.

AppCreator24 provides a remote MCP server that lets compatible AI assistants create Android apps and update apps previously created through the service.

Build community spaces, quizzes, audio and video apps, content guides, forums, games and more. The result is an initial configurable app structure. Further customization is available in the AppCreator24 web editor.

Bring AppCreator24 to your assistant.

Add a custom remote MCP connection in your preferred MCP-compatible client. The exact menu and availability depend on your AI provider, plan and workspace permissions.

1. Add a remote MCP server.

   Use the HTTPS endpoint above and select Streamable HTTP if your client asks for a transport.

2. Choose no authentication.

   This endpoint does not use OAuth or an API key. The app-creation flow does not require an AppCreator24 account.

3. Discover the tool.

   The connection exposes GenerateApp, displayed as “Create or edit Android apps and build APKs.” Your client may ask you to review or approve write actions.

The endpoint is a protocol interface, not a webpage. Opening it directly in a browser can return HTTP 405; a compatible client connects using POST.

Start with a conversation.

Select the AppCreator24 connection in your assistant and describe your app. Its name, language, theme, welcome message and sections become the inputs to the creation tool.

These are conversation examples, not live creation buttons.

Once the app request succeeds, the assistant receives download and edit links. New apps are compiled in a queue, so the download may not be available immediately.

One tool. Create or update.

The same tool handles both operations. previous_id: "0" creates an app. A complete identifier from an earlier successful response selects an existing app for editing.

Supported language values

An edit does not regenerate the app icon. The app name, icon and other advanced settings can be managed in the AppCreator24 web editor.

Choose the building blocks.

Each section has a type, title and content string. Slots 1–6 determine the requested order. These are the accepted info_N formats.

Supported game genres

URLs represent real resources supplied to the app. The MCP validates URL format but does not search for resources or verify their availability, format, permissions or continued accessibility.

See the request shape.

These examples show the arguments sent by an MCP client. They are documentation only; this page never sends creation or editing requests.

Create a community app

A new Spanish-language app with a chat and a forum:

{
  "theme": "green",
  "previous_id": "0",
  "name": "Walking Club",
  "description": "Una comunidad para compartir rutas y salidas.",
  "welcome": "Bienvenido al club",
  "language": "spanish",
  "type_1": "chat",
  "title_1": "Chat",
  "info_1": "",
  "type_2": "forum",
  "title_2": "Foro",
  "info_2": "Rutas@Salidas@General"
}

A complete quiz content string

A four-question quiz with four answers per question, where the first answer is correct:

1+1?;2;3;4;5|2+2?;4;3;5;6|3+3?;6;3;4;5|4+4?;8;3;4;5

Update an existing app

The argument structure is the same as creation. previous_id contains the complete id from the earlier successful result, and the payload contains all final sections. The tool has no operation to retrieve the current configuration. An edit containing only a new section would remove the old sections.

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "GenerateApp",
    "arguments": {
      "theme": "blue",
      "previous_id": "0",
      "name": "My Community",
      "description": "A community chat app.",
      "welcome": "Welcome!",
      "language": "english",
      "type_1": "chat",
      "title_1": "Community",
      "info_1": ""
    }
  }
}

Understand the response.

A successful tool result has isError: false, a readable message in content, and these fields in structuredContent:

Errors and uncertain outcomes

• Validation error: the input is rejected before a request is sent to the app backend. The error text identifies the invalid field or format.
• Backend failure or timeout: the app may already have been created or changed. Repeating a call can create a duplicate app or repeat an edit; the operation is not idempotent.
• Web-editor response: some app-management situations return an edit link with an error message directing management to AppCreator24.

Tool execution errors use isError: true. Malformed protocol requests and unknown methods use JSON-RPC errors. An HTTP 200 response alone does not establish that an app request succeeded.

Built for compatible MCP clients.

For the 2025 protocol versions, the client performs initialize and sends notifications/initialized before normal tool use. Subsequent requests carry the negotiated MCP-Protocol-Version.

For 2026-07-28, requests carry per-request metadata in params._meta (protocol version and client capabilities), plus matching MCP-Protocol-Version and Mcp-Method headers. Tool calls also carry Mcp-Name: GenerateApp. This version does not use the earlier initialization handshake.

The tool is annotated as a write operation, potentially destructive when replacing sections, non-idempotent, and interacting with external entities. Client authorization and approval policies still apply.

See the Model Context Protocol documentation for protocol definitions. A client’s version support, origin policy and account settings can affect connection compatibility.

A few useful details.

Help with AppCreator24 MCP.

This integration is provided by Vinebre Software S.L., the operator of AppCreator24. This page explains connection settings, supported app features, editing behavior and common errors.

Contact AppCreator24

For help beyond this documentation, use the support and contact options on the AppCreator24 website. The homepage offers a contact form; if you already use the AppCreator24 control panel, you can also contact support from there.

For a connection problem, include your AI client, the approximate date and time, the action you attempted and the error message. For an app problem, describe the affected app and what happened. Do not include your app-management code, complete editing link, passwords or API keys in a public report.

Before repeating an interrupted request

If a creation or update timed out, check your existing result or web editor before trying again. The operation may already have taken effect, and another creation call can produce a duplicate app.

See the MCP Privacy Policy and MCP Terms of Service for information about data handling and use of the integration.