Android Studio Setup

Once 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. Along with the MCP server, the install tool also installs Skills and Rules so that the built-in AI agent uses the WEEGLOO API the way it is meant to be used. Skills are guides that capture how to do a specific task well, and Rules are rules to follow across all tasks. You set everything up at once with the install tool, then enable the MCP server in Android Studio.

For details on the MCP server and on Skills and Rules, see the MCP and Skills and Rules pages respectively. This page covers only how to connect to Android Studio.

Prerequisites

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

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.

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

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

Connecting

For a default install, copy the install command on this page and run it once in your terminal. To go through the install steps and choose each one yourself, open Custom install. After installing, turn on the server in Android Studio settings to finish the connection.

MCP Server Configuration File

The install tool registers the servers 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.

Skills

The install tool sets up each Skill as a single directory and places it under .android-studio/skills/ in the project folder.

Rules

Android Studio has no separate concept of Rules. So the install tool puts the content that corresponds to Rules, that is, content that plays the same role as Claude Code's Rules, into the AGENTS.md file in the project folder.

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.
• Keeping up to date: Covers how to keep the Skills and Rules you installed up to date.
• 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.