AutoGLM MCP Server
Android screen analysis capabilities via MCP protocol.
Installation
Option 1: Using uvx (Recommended)
No manual installation required. Just add to AI agent MCP config:
{
"mcpServers": {
"autoglm-mcp": {
"command": "uvx",
"args": ["autoglm-mcp"],
"env": {
"AUTOGLM_BASE_URL": "https://api.z.ai/api/paas/v4",
"AUTOGLM_MODEL": "autoglm-phone-multilingual",
"AUTOGLM_APIKEY": "your-api-key-here"
}
}
}
}
Option 2: pip install
pip install autoglm-mcp
Then configure AI agent MCP:
{
"mcpServers": {
"autoglm-mcp": {
"command": "autoglm-mcp",
"env": {
"AUTOGLM_BASE_URL": "https://api.z.ai/api/paas/v4",
"AUTOGLM_MODEL": "autoglm-phone-multilingual",
"AUTOGLM_APIKEY": "your-api-key-here"
}
}
}
}
Environment Variables
| Variable | Description | Default |
|---|---|---|
AUTOGLM_APIKEY |
API key (required) | - |
AUTOGLM_BASE_URL |
API endpoint | https://api.z.ai/api/paas/v4 |
AUTOGLM_MODEL |
Model name | autoglm-phone-multilingual |
Usage
Ensure your phone is connected via ADB, then use the aiAsk tool in AI agent:
- "What are the coordinates to click the search button?"
- "How do I open Settings?"
Local Development & Debugging
Prerequisites
- Python >= 3.10
- Node.js >= 18 (for MCP Inspector)
- ADB installed and phone connected (
adb devicesshows your device)
Install from Source
cd mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
MCP Inspector (Recommended)
MCP Inspector is the official visual debugging tool for MCP servers — like Postman for MCP.
npx @modelcontextprotocol/inspector \
-e AUTOGLM_APIKEY="your-api-key-here" \
-e AUTOGLM_BASE_URL="https://api.z.ai/api/paas/v4" \
-e AUTOGLM_MODEL="autoglm-phone-multilingual" \
-- \
/path/to/file/mcp/.venv/bin/python -m autoglm_mcp.server
Then open http://localhost:6274 in your browser:
- Click Connect to connect to the server
- Switch to the Tools tab — you should see the
aiAsktool - Enter a question (e.g.
"What is on the screen?") and click Run Tool - Inspect the JSON-RPC request/response in the left panel
Use local mcp server
"autoglm-mcp": {
"command": "/path/to/file/mcp/.venv/bin/python",
"args": [
"-m",
"autoglm_mcp.server"
],
"env": {
"AUTOGLM_BASE_URL": "https://api.z.ai/api/paas/v4",
"AUTOGLM_MODEL": "autoglm-phone-multilingual",
"AUTOGLM_APIKEY": "xxx"
}
}
Metadata
Release files for autoglm-mcp 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| autoglm_mcp-1.0.0.tar.gz | 7.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autoglm_mcp-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.1 kB
Release files / autoglm_mcp-1.0.0.tar.gz
| Download URL | autoglm_mcp-1.0.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a94ced96379db18910f421046f0b8bcaeb4777bc1f21260f9b928c86ad5b7881
|
|
BLAKE2b-256 checksum How to use checksums |
5a1f2e93426591ebd5c2d5fc553ea9433bfd7a33cbc655e2b0b41c0e87a4f08a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / autoglm_mcp-1.0.0-py3-none-any.whl
| Download URL | autoglm_mcp-1.0.0-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e1a36205a538c37b761a71e8d9d97c955b418a6f839abc0d2b5bb6a001693990
|
|
BLAKE2b-256 checksum How to use checksums |
03ace84c1868e6ba4f48ae613271e2b7c438ae81e0f79affea2eba93ce868c70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for autoglm-mcp 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.