Which integrations are available for this server?

Allows signing of Android APK files, enabling secure distribution and installation of Android applications. Provides access to the Uber APK Signer tool for signing APK files, verifying signatures, and managing keystores for Android applications.

How do I use Uber APK Signer MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Uber APK Signer MCP Server Sign app.apk using the default debug keystore." That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Uber APK Signer MCP Server

by OdellMoreno

Overview Schema Related Servers Score Discussions

TypeScript

Local

Uber APK Signer MCP Server

An MCP (Model Context Protocol) server that provides access to the Uber APK Signer tool through your chat LLM. This allows you to sign APK files, verify signatures, manage keystores, and perform other APK signing operations directly from your chat interface.

Features

Sign APK Files: Sign APK files using existing keystores
Verify Signatures: Verify the signature of APK files
Keystore Management: List available keystores and create new ones
Flexible Transport: Support for both stdio and TCP transport modes
Configurable: Environment-based configuration for easy customization

Related MCP server: android-mcp

Prerequisites

Node.js 18.0.0 or higher
Uber APK Signer tool installed and accessible in your PATH
Java Runtime Environment (JRE) for APK signing operations

Installation

Clone this repository:

git clone <your-repo-url>
cd uber-apk-signer-mcp

Install dependencies:

npm install

Build the project:

npm run build

Configuration

The server automatically loads configuration from a .env file in your project directory, or you can set environment variables directly.

Environment Variables

You can configure the server using environment variables:

# Uber APK Signer configuration
export UBER_APK_SIGNER_PATH="/path/to/uber-apk-signer"
export UBER_APK_SIGNER_TIMEOUT=300000
export UBER_APK_SIGNER_LOG_LEVEL=info

# MCP Server configuration
export MCP_SERVER_NAME="uber-apk-signer-mcp"
export MCP_TRANSPORT="stdio"  # or "tcp"
export MCP_TCP_HOST="localhost"
export MCP_TCP_PORT=3000

# Security settings
export MCP_ALLOW_INSECURE=false
export MCP_MAX_FILE_SIZE=104857600

Using a .env File (Recommended)

Create a .env file in your project directory for easier configuration:

# Required: Path to your uber-apk-signer tool
UBER_APK_SIGNER_PATH=/path/to/uber-apk-signer

# Optional: Uber APK Signer settings
UBER_APK_SIGNER_TIMEOUT=300000        # 5 minutes timeout
UBER_APK_SIGNER_LOG_LEVEL=info        # debug, info, warn, error

# Optional: Server settings
MCP_SERVER_NAME=uber-apk-signer-mcp    # Server name
MCP_SERVER_VERSION=1.0.0               # Server version
MCP_TRANSPORT=stdio                    # stdio or tcp

# Optional: Security settings
MCP_ALLOW_INSECURE=false               # Allow insecure connections
MCP_MAX_FILE_SIZE=104857600            # Max file size (100MB)

Note: The .env file is automatically ignored by Git to keep your personal paths private.

Uber APK Signer Path

Make sure the Uber APK Signer tool is accessible. You can either:

Add it to your system PATH, or
Set the UBER_APK_SIGNER_PATH environment variable to the full path

Usage

Starting the Server

Stdio Transport (Default)

npm start

TCP Transport

npm start -- --port 3000 --host localhost

Available Tools

The MCP server provides the following tools:

1. Sign APK (`sign_apk`)

Sign an APK file using a keystore. Only apkPath is required - other parameters use smart defaults.

Parameters:

apkPath (required): Path to the APK file to sign
keystorePath (optional): Path to the keystore file (defaults to ~/.android/debug.keystore)
keystorePassword (optional): Password for the keystore (defaults to android)
keyAlias (optional): Alias of the key to use for signing (defaults to androiddebugkey)
keyPassword (optional): Password for the key (defaults to android)
outputPath (optional): Output path for the signed APK (auto-generated if not provided)

Examples:

Simple signing (development/testing):

{
  "apkPath": "./app.apk"
}

Production signing with custom keystore:

{
  "apkPath": "./release.apk",
  "keystorePath": "~/keys/release.keystore",
  "keystorePassword": "mysecret",
  "keyAlias": "release-key",
  "keyPassword": "mysecret"
}

Chat usage:

"Can you sign my app.apk file?" (uses debug keystore defaults)
"Sign my release.apk with my production keystore" (asks for keystore details)

2. Verify APK Signature (`verify_apk_signature`)

Verify the signature of an APK file.

Parameters:

apkPath (required): Path to the APK file to verify

Example:

{
  "apkPath": "/path/to/app.apk"
}

3. List Keystores (`list_keystores`)

List available keystores in a directory.

Parameters:

directory (optional): Directory to search for keystores (default: current directory)

Example:

{
  "directory": "/path/to/keystores"
}

4. Create Keystore (`create_keystore`)

Create a new keystore for APK signing.

Parameters:

keystorePath (required): Path where to create the keystore
keystorePassword (required): Password for the keystore
keyAlias (required): Alias for the key
keyPassword (required): Password for the key
commonName (optional): Common name for the certificate
organization (optional): Organization name

Example:

{
  "keystorePath": "/path/to/new-keystore.jks",
  "keystorePassword": "newpass123",
  "keyAlias": "release",
  "keyPassword": "newkey123",
  "commonName": "My App",
  "organization": "My Company"
}

Integration with Chat LLMs

MCP Client Configuration

The server supports stdio transport and can be integrated with any MCP-compatible client. Here are configuration examples for popular clients:

Claude Desktop

{
  "mcpServers": {
    "uber-apk-signer": {
      "command": "node",
      "args": ["/path/to/uber-apk-signer-mcp/dist/index.js"],
      "cwd": "/path/to/uber-apk-signer-mcp"
    }
  }
}

Ollama

# In your Ollama configuration
mcp_servers:
  uber-apk-signer:
    command: node
    args: ["/path/to/uber-apk-signer-mcp/dist/index.js"]
    cwd: "/path/to/uber-apk-signer-mcp"

Custom MCP Client

import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { StdioClientTransport } from '@modelcontextprotocol/sdk/client/stdio.js';

const client = new Client({
  name: 'my-client',
  version: '1.0.0',
});

const transport = new StdioClientTransport({
  command: 'node',
  args: ['/path/to/uber-apk-signer-mcp/dist/index.js'],
  cwd: '/path/to/uber-apk-signer-mcp',
});

await client.connect(transport);

Generic Configuration

Most MCP clients use a similar configuration structure:

{
  "mcpServers": {
    "uber-apk-signer": {
      "command": "node",
      "args": ["/path/to/uber-apk-signer-mcp/dist/index.js"],
      "cwd": "/path/to/uber-apk-signer-mcp"
    }
  }
}

Note: Replace /path/to/uber-apk-signer-mcp with the actual path to your installation directory.

Development

Project Structure

src/
├── index.ts              # Main server entry point
├── tools/
│   └── apk-signer-tools.ts  # MCP tool implementations
├── services/
│   └── apk-signer.ts        # APK signing service
└── config/
    └── config.ts             # Configuration management

Building

npm run build

Development Mode

npm run dev

Testing

npm test

Troubleshooting

Common Issues

"Uber APK Signer not found"
- Ensure the tool is installed and accessible
- Check the UBER_APK_SIGNER_PATH environment variable
- Verify the tool works from command line
"Permission denied"
- Check file permissions for APK and keystore files
- Ensure the server has read/write access to the working directory
"Keystore password incorrect"
- Verify the keystore password and key password
- Check if the keystore file is corrupted
"APK file not found"
- Verify the APK file path is correct
- Ensure the file exists and is readable

Debug Mode

Enable debug logging by setting:

export UBER_APK_SIGNER_LOG_LEVEL=debug

Security Considerations

Keystore Security: Keep your keystore files and passwords secure
File Access: The server needs access to APK and keystore files
Network Security: When using TCP transport, consider firewall rules
Input Validation: All inputs are validated before processing

Contributing

Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Submit a pull request

License

MIT License - see LICENSE file for details.

Support

For issues and questions:

Check the troubleshooting section
Review the logs with debug mode enabled
Open an issue on GitHub
Contact your internal team for Uber APK Signer specific issues

Available Tools

4 tools

create_keystoreC

Create a new keystore for APK signing

ParametersJSON Schema

Name	Required	Description	Default
`keystorePath`	Yes	Path where to create the keystore
`keystorePassword`	Yes	Password for the keystore
`keyAlias`	Yes	Alias for the key
`keyPassword`	Yes	Password for the key
`commonName`	No	Common name for the certificate	APK Signer
`organization`	No	Organization name	Your Organization

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'Create', implying a write operation, but fails to mention whether it overwrites existing files, what happens if the path already exists, the type of keystore generated, or any authentication requirements. For a tool that creates a sensitive artifact, this is insufficient transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but at the expense of completeness. It is front-loaded with the core action, but there is no structured information about when to use the tool or what it returns. It could be reorganized to include bullet points or additional context without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has 6 parameters (4 required), no output schema, and no annotations, the description is insufficiently complete. It does not mention return values, error conditions, or prerequisites (e.g., directory existence). For a file-creating tool with multiple optional fields, more context is needed for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All six parameters have descriptions in the schema (100% coverage), so the baseline is 3. The description does not add any additional meaning beyond what the schema provides. It does not explain domain-specific conventions (e.g., key alias uniqueness) or relationships between parameters (e.g., keyPassword and keystorePassword). The description adds no value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new keystore for APK signing' clearly states the action (Create) and the resource (keystore) with a specific purpose (APK signing). It distinguishes from sibling tools like list_keystores, sign_apk, and verify_apk_signature, which are different operations. However, it could be more specific (e.g., keystore format) and does not explicitly differentiate itself from potential sibling tools that might also create something.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. Sibling tools suggest it should be used before signing APKs, but the description does not mention prerequisites, typical workflow placement, or situations where another tool might be more appropriate. The one-sentence description lacks any usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_keystoresB

List available keystores in a directory

ParametersJSON Schema

Name	Required	Description	Default
`directory`	No	Directory to search for keystores	.

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It does not disclose whether the list is recursive, what format the results are in, or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, no unnecessary words. However, it is minimal and could be slightly expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description lacks details about output format, recursion behavior, and edge cases, making it incomplete for a tool with one parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter 'directory', which already has a description. The tool description does not add new information beyond what the schema provides, so it meets the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'keystores in a directory', which distinguishes it from sibling tools like create_keystore, sign_apk, and verify_apk_signature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool vs alternatives, nor any exclusion criteria or context recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sign_apkA

Sign an APK file using Uber APK Signer. Only apkPath is required - other parameters can use defaults or be configured.

ParametersJSON Schema

Name	Required	Description	Default
`apkPath`	Yes	Path to the APK file to sign (required)
`keystorePath`	No	Path to the keystore file (defaults to ~/.android/debug.keystore)	~/.android/debug.keystore
`keystorePassword`	No	Password for the keystore (defaults to "android")	android
`keyAlias`	No	Alias of the key to use for signing (defaults to "androiddebugkey")	androiddebugkey
`keyPassword`	No	Password for the key (defaults to "android")	android
`outputPath`	No	Output path for the signed APK (optional, auto-generated if not provided)

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavioral traits. It does not disclose side effects (e.g., overwriting files), output location, error handling, or prerequisites beyond defaults. This is insufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It states the purpose and key usage guidance efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (6 simple parameters, no output schema), the description is minimal but lacks details on output (e.g., signed APK path) and behavioral traits. It meets basic needs but could be more complete for a signing operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the description adds minimal value beyond reinforcing that apkPath is required and other parameters have defaults. It does not provide syntax, format, or additional context not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Sign an APK file using Uber APK Signer', specifying the action (sign), resource (APK file), and tool (Uber APK Signer). It distinguishes from sibling tools like create_keystore and verify_apk_signature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that only apkPath is required and other parameters can use defaults or be configured, providing clear guidance on minimal usage and flexibility. It implies usage when signing an APK, but does not explicitly state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

verify_apk_signatureB

Verify the signature of an APK file

ParametersJSON Schema

Name	Required	Description	Default
`apkPath`	Yes	Path to the APK file to verify

TDQS

B3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description does not disclose what the verification checks (e.g., against a keystore), prerequisites, side effects, or whether it is read-only. Minimal behavioral context beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, no waste, but too minimal to convey useful context. Could be expanded without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, no annotations, and only one parameter. The description omits crucial details like what the verification returns (success/failure, signer info) and error conditions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the single parameter. The tool description adds no additional meaning beyond what the parameter description provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'verify' and the resource 'APK signature'. It distinguishes from sibling tools like 'sign_apk' and keystore management tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, such as whether to use it before or after signing, or how it differs from verification via other means.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: creating, listing, signing, and verifying. No overlap, and descriptions reinforce the differences.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (create_keystore, list_keystores, sign_apk, verify_apk_signature).

Tool Count5/5

With 4 tools, the server covers the essential operations for APK signing without unnecessary extras, perfectly scoped for its purpose.

Completeness4/5

Core workflow (create keystore, sign, verify, list) is covered, but missing a delete/update keystore tool is a minor gap.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Appcircle MCP
io.appcircle
MCP server for Appcircle mobile CI/CD platform.
CI/CD & DevOps Developer Tools
2
JFrog Remote MCP Server
io.github.jfrog
MCP Server for JFrog, providing tools for development and artifact management.
Developer Tools CI/CD & DevOps Cloud Platforms
215
Certifier MCP BOAuth
io.certifier
Official MCP server for Certifier to issue, manage, and track certificates and badges.
Education & Learning Tools
2
podcasts A
com.petabloom
An MCP server that provides tools to discover and retrieve podcast episodes transcripts.
Entertainment & Media Search
52

Related MCP Servers

Apktool MCP Server
Developer Tools RAG Systems Code Execution
zinja-coder
A
license
A
quality
C
maintenance
An MCP server that integrates with Apktool to provide live reverse engineering support for Android applications using Claude and other LLMs through the Model Context Protocol.
Updated 2 months ago (2026-07-02 14:20 UTC)
16
642
Apache 2.0
android-mcp
OS Automation App Automation
tomdwipo
F
license
Not graded
quality
C
maintenance
A lightweight MCP server for Android operating system automation. This server provides tools to interact directly with Android devices and app interaction with control
Updated 10 months ago (2025-10-20 05:56 UTC)
3
Fables MCP Server
Developer Tools CI/CD & DevOps
Atum246
A
license
Not graded
quality
D
maintenance
An MCP server that provides AI agents with tools to build, deploy, and manage Flutter applications, including APK/AAB generation, keystore management, and CI/CD integration.
Updated 4 months ago (2026-04-29 00:01 UTC)
7
1
MIT
re-apktool
Penetration Testing Code Analysis
Heretek-RE
A
license
A
quality
C
maintenance
MCP server for Android APK triage, providing tools to parse APK headers, list DEX classes, and decode AndroidManifest.xml using apktool or androguard backends.
Updated 3 months ago (2026-06-10 19:49 UTC)
5
1
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OdellMoreno/uber-apk-signer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Uber APK Signer MCP Server

Features

Prerequisites

Installation

Configuration

Environment Variables

Using a .env File (Recommended)

Uber APK Signer Path

Usage

Starting the Server

Stdio Transport (Default)

TCP Transport

Available Tools

1. Sign APK (sign_apk)

2. Verify APK Signature (verify_apk_signature)

3. List Keystores (list_keystores)

4. Create Keystore (create_keystore)

Integration with Chat LLMs

MCP Client Configuration

Claude Desktop

Ollama

Custom MCP Client

Generic Configuration

Development

Project Structure

Building

Development Mode

Testing

Troubleshooting

Common Issues

Debug Mode

Security Considerations

Contributing

License

Support

Available Tools

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

1. Sign APK (`sign_apk`)

2. Verify APK Signature (`verify_apk_signature`)

3. List Keystores (`list_keystores`)

4. Create Keystore (`create_keystore`)