Uber APK Signer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TCP_HOST | No | TCP host for tcp transport | localhost |
| MCP_TCP_PORT | No | TCP port for tcp transport | 3000 |
| MCP_TRANSPORT | No | Transport type: stdio or tcp | stdio |
| MCP_SERVER_NAME | No | Server name | uber-apk-signer-mcp |
| MCP_MAX_FILE_SIZE | No | Max file size in bytes | 104857600 |
| MCP_ALLOW_INSECURE | No | Allow insecure connections | false |
| MCP_SERVER_VERSION | No | Server version | 1.0.0 |
| UBER_APK_SIGNER_PATH | Yes | Path to your uber-apk-signer tool | |
| UBER_APK_SIGNER_TIMEOUT | No | Timeout for signing operations in milliseconds | 300000 |
| UBER_APK_SIGNER_LOG_LEVEL | No | Log level: debug, info, warn, error | info |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sign_apkA | Sign an APK file using Uber APK Signer. Only apkPath is required - other parameters can use defaults or be configured. |
| verify_apk_signatureB | Verify the signature of an APK file |
| list_keystoresB | List available keystores in a directory |
| create_keystoreC | Create a new keystore for APK signing |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: creating, listing, signing, and verifying. No overlap, and descriptions reinforce the differences.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (create_keystore, list_keystores, sign_apk, verify_apk_signature).
With 4 tools, the server covers the essential operations for APK signing without unnecessary extras, perfectly scoped for its purpose.
Core workflow (create keystore, sign, verify, list) is covered, but missing a delete/update keystore tool is a minor gap.