Weegloo Docs - Android Studio Setup

When you connect the WEEGLOO MCP server to Android Studio, its built-in AI agent can directly create, read, and modify resources such as Content Type, Content, and Media. You set everything up at once with the install tool, then just turn on the MCP server in Android Studio's settings.

MCP itself, the server groups, and the file upload server are covered in MCP. This page covers only the steps to connect to Android Studio.

Prerequisites

Running the install commands below requires Node.js. First, check whether it is installed and whether the version is 18 or higher with the following commands.

Terminal

node --version # v18 or higher is OK npx --version # OK if a version is printed

If Node.js is installed but npx is not, update npm to the latest version with the command below. Updating npm installs npx along with it.

Terminal

npm install -g npm@latest

If Node.js is not installed or its version is too old, install Node.js using the method that fits your operating system.

Terminal

brew install node

If you do not have Homebrew, install it first from brew.sh, or download Node.js directly from nodejs.org.

Android Studio must also be installed. If you do not have it yet, you can get it from Download Android Studio.

Connecting

Follow the guide below. After you run the install command, turn on the server in Android Studio's settings to finish the connection.

Android Studio is strongly not recommended for Weegloo integration

Android Studio's built-in AI agent (Gemini) can be used for UI work. However, for coding tasks such as Weegloo integration, it is highly unstable due to AI performance issues, so we strongly recommend using a different AI agent, such as Claude Code or Codex. Verified on 2026.1.1 Patch 2 and earlier.

Install MCP · Skills

Copy the install command and run it in your terminal. Be sure to run it inside the project folder you want to connect.

Terminal

$ npx weegloo@latest -y \ --agent androidstudio \ --token wgl_••••••••••••

Authenticate MCP

After installing, enable the MCP servers in Android Studio.

1.Go to Settings → Tools → AI → MCP Servers, then click the JSON View tab.
2.Check Enable MCP Servers.
3.Confirm that weegloo and weegloo-upload are present in the configuration.
4.Click Apply. When you see notifications that weegloo and weegloo-upload connected, the connection is complete.

Inspecting the Configuration File Yourself

The install tool automatically creates and manages the configuration file, so you do not need to check it yourself. The content below is reference material for users who need the concrete configuration file structure and paths.

The install tool registers the server in mcp.json inside Android Studio's settings directory. This directory's name includes a version (for example, AndroidStudio2025.1), and the install tool finds and uses the most recent directory. The locations per operating system are as follows.

macOS: ~/Library/Application Support/Google/AndroidStudio<version>/mcp.json
Windows: %APPDATA%\Google\AndroidStudio<version>\mcp.json
Linux: ~/.config/Google/AndroidStudio<version>/mcp.json

The weegloo server connects to https://ai.weegloo.com/mcp over HTTP and uses a Personal Access Token in the Authorization header for authentication. The weegloo-upload server, which handles files, runs via npx and uses the same token.

{
  "mcpServers": {
    "weegloo": {
      "httpUrl": "https://ai.weegloo.com/mcp",
      "headers": {
        "Authorization": "Bearer <Personal Access Token>"
      },
      "timeout": -1,
      "enabled": true,
      "trust": false,
      "includeTools": [],
      "excludeTools": []
    },
    "weegloo-upload": {
      "command": "npx",
      "args": ["-y", "weegloo-upload"],
      "env": {
        "UPLOAD_API_URL": "https://upload.weegloo.com/v1",
        "AUTH_BEARER_TOKEN": "<Personal Access Token>"
      }
    }
  }
}

To change the server group, append a group value to the end of the weegloo server's httpUrl. For example, to use all tools, write it as https://ai.weegloo.com/mcp?group=all. For the tool composition of each group, refer to MCP Server Groups.

Because the actual token is stored as-is in the configuration file, be careful not to expose this file publicly or commit it to a shared repository.

What to Do Next

MCP: Covers the foundations of the connection, such as server groups and the file upload server.
Skills and Rules: Covers what the Skills and Rules that the install tool sets up alongside it are.
Migrating Static Pages with AI: Follow the flow of migrating a real page into a content-based service with the MCP connection you set up.