Skip to main content
Glama
Appknox MCP Server

Appknox MCP Server

Official
by appknox

Appknox MCP Server

A Model Context Protocol server that wraps the Appknox CLI for mobile application security testing.

Prerequisites

Related MCP server: PS_MobSF_MCP_Server

Installation

npm install -g @appknox/mcp-server

Configuration

Authentication

Configure your access token using Appknox CLI:

appknox init

This will prompt for your access token and save it to ~/.config/appknox.json.

Alternatively, set the APPKNOX_ACCESS_TOKEN environment variable if you prefer not to use the config file.

For additional configuration options (API host, region, proxy), see Appknox CLI documentation.

Claude Desktop Setup

Add to your Claude Desktop config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "appknox": {
      "command": "npx",
      "args": ["-y", "@appknox/mcp-server"]
    }
  }
}

If you haven't run appknox init, you can set the token directly in the config:

{
  "mcpServers": {
    "appknox": {
      "command": "npx",
      "args": ["-y", "@appknox/mcp-server"],
      "env": {
        "APPKNOX_ACCESS_TOKEN": "your-token-here"
      }
    }
  }
}

Environment Variables

Variable

Description

Default

APPKNOX_ACCESS_TOKEN

Your Appknox API access token

Read from ~/.config/appknox.json

APPKNOX_CLI_PATH

Absolute path to the Appknox CLI binary

/usr/local/bin/appknox

LOG_LEVEL

Logging level (debug, info, warn, error)

info

If the Appknox CLI is installed in a non-standard location, set APPKNOX_CLI_PATH:

{
  "mcpServers": {
    "appknox": {
      "command": "npx",
      "args": ["-y", "@appknox/mcp-server"],
      "env": {
        "APPKNOX_CLI_PATH": "/opt/homebrew/bin/appknox"
      }
    }
  }
}

Restart Claude Desktop after updating.

Available Tools

The MCP server exposes Appknox CLI commands as tools:

Tool

Description

appknox_whoami

Show current authenticated user information

appknox_organizations

List all organizations accessible to the user

appknox_projects

List projects with optional filtering by platform, package name, or search query

appknox_files

List all files (app versions) for a specific project. Requires project_id

appknox_analyses

List security analysis results (vulnerabilities) for a file. Requires file_id

appknox_vulnerability

Get detailed information about a specific vulnerability

appknox_owasp

Fetch OWASP category details by ID

appknox_upload

Upload an APK/IPA file for security scanning. Returns file_id

appknox_cicheck

Check vulnerabilities against a risk threshold (for CI/CD pipelines)

appknox_sarif

Generate a SARIF report for integration with code analysis tools

appknox_reports_create

Create a vulnerability report for a file

appknox_reports_download

Download vulnerability report as CSV. Returns content directly

appknox_dastcheck

Check DAST (dynamic scan) status and results

Tool Workflow

Most tools require IDs that come from other tools:

appknox_projects → project_id → appknox_files → file_id → appknox_analyses
                                                       → appknox_reports_download
                                                       → appknox_cicheck
                                                       → appknox_sarif

Usage Examples

Basic Queries

"Who am I logged in as?"
"List all my organizations"
"Show me all my projects"
"List projects with package name containing 'com.example'"

Working with Projects and Files

"List all files for project ID 1234"
"Show me the latest scan results for project 'MyApp'"
"What vulnerabilities were found in file ID 56789?"

Uploading and Scanning

"Upload /Users/me/Downloads/myapp.apk for security scanning"
"Upload the app at /Users/me/Desktop/app.ipa and tell me the file ID"

Important: File paths must be absolute paths on your local machine (e.g., /Users/username/Downloads/app.apk). Drag-and-drop uploads or sandbox paths won't work.

Security Analysis

"Show all critical and high vulnerabilities for file ID 12345"
"Check if file ID 12345 passes the security threshold for 'high' risk"
"Run a CI check on file 12345 with medium risk threshold"

Reports and Documentation

"Download the vulnerability report for file ID 12345"
"Generate a SARIF report for file 12345 with high risk threshold"
"Get details about vulnerability ID 67890"
"What is OWASP M1_2016?"

CI/CD Integration Scenarios

"Upload /path/to/app.apk and check if it has any critical vulnerabilities"
"Scan the app and fail if there are any high-risk issues"
"Generate a SARIF report I can upload to GitHub Security"

Dynamic Analysis (DAST)

"Check the DAST scan status for file ID 12345"
"What are the dynamic scan results for file 12345 with medium risk threshold?"

Troubleshooting

Appknox CLI not found: Verify installation with which appknox Authentication failed: Check your token with echo $APPKNOX_ACCESS_TOKEN Debug logging: Set LOG_LEVEL=debug in your environment

Development

# Clone and build
git clone https://github.com/appknox/appknox-mcp.git
cd appknox-mcp
npm install
npm run build

# add to mcp config
 "appknox": {
    "command": "node",
    "args": ["/abosolute/path/to/appknox-mcp/build/index.js"]
  }

See CONTRIBUTING.md for contribution guidelines.

Resources

License

MIT

Available Tools

13 tools
appknox_analysesA

List all security analysis results (vulnerabilities) for a specific file. Requires file_id which can be obtained from appknox_files.

Inputs: file_id (required).

appknox_cicheckA

Check for vulnerabilities based on risk threshold. Fails if vulnerabilities above threshold are found. Requires file_id (from appknox_files) and risk_threshold.

Inputs: file_id (required), risk_threshold (required), timeout_minutes.

appknox_dastcheckB

Check the status of a dynamic scan and display results when complete. Requires file_id (from appknox_files) and risk_threshold.

Inputs: file_id (required), risk_threshold (required).

appknox_filesA

List all files (app versions) for a specific project. Requires project_id which can be obtained from appknox_projects.

Inputs: project_id (required), limit, offset, version_code.

appknox_organizationsA

List all organizations accessible to the authenticated user

Inputs: no named parameters.

appknox_owaspA

Get OWASP category details by ID (e.g., M1_2016)

Inputs: owasp_id (required).

appknox_projectsA

List all projects with optional filtering by platform, package name, or search query

Inputs: limit, query, offset, platform, +1 more.

appknox_reports_createA

Create a vulnerability analysis report for a file. Returns the report ID.

Inputs: file_id (required).

appknox_reports_downloadA

Download a vulnerability report for a file in CSV format. Requires file_id (from appknox_files). Automatically creates a new report if one does not exist. Returns the CSV content directly as text - no file path needed.

Inputs: file_id (required).

appknox_sarifC

Generate a SARIF (Static Analysis Results Interchange Format) report for the scanned file

Inputs: file_id (required), risk_threshold (required), output_path, timeout_minutes.

appknox_uploadA

Upload a mobile application package (APK/IPA) for security scanning. Returns the file ID. IMPORTANT: The file_path must be an absolute path on the HOST machine filesystem (e.g., /Users/username/Downloads/app.apk on Mac, or C:\Users\username\Downloads\app.apk on Windows). Paths inside Claude Desktop sandbox (/mnt/user-data/, /tmp/ inside sandbox) will NOT work. The user must provide the real path where the file exists on their actual computer, not paths from drag-and-drop uploads.

Inputs: file_path (required).

appknox_vulnerabilityB

Get detailed information about a specific vulnerability

Inputs: vulnerability_id (required).

appknox_whoamiA

Get information about the currently authenticated Appknox user

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools target distinct resources (projects, files, analyses, reports), so agents can generally tell them apart. The main overlap risk is between appknox_cicheck and appknox_dastcheck, which both check vulnerabilities against a risk threshold but for static vs dynamic scans, which could cause misselection.

    Naming Consistency2/5

    The appknox_ prefix is consistent, but the suffix pattern is highly varied: bare nouns (organizations, projects, files), verbs (upload, whoami), compound nouns (cicheck, sarif), and noun_verb pairs (reports_create, reports_download). There is no predictable verb_noun convention, making the naming feel chaotic.

    Tool Count5/5

    13 tools is well-scoped for a mobile app security platform. Each tool serves a distinct part of the workflow—auth, orgs, projects, files, upload, checks, vulnerability details, and reports—without unnecessary bloat or excessive granularity.

    Completeness4/5

    The tool set covers the core lifecycle: authenticate, navigate orgs/projects/files, upload packages, perform static and dynamic checks, view vulnerability details, and generate/download reports. Minor gaps exist, such as update/delete operations for projects or files, but agents can work around these for typical scanning workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      C
      quality
      D
      maintenance
      A Node.js-based Model Context Protocol implementation that provides a standardized interface for integrating Mobile Security Framework's security analysis capabilities into automated workflows and third-party tools.
      71
      24
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      This is an MCP (Model Context Protocol) compatible tool that allows MobSF (Mobile Security Framework) to scan APK and IPA files directly via Claude, 5ire, or any MCP-capable client.
      24
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Model Context Protocol server for security research automation, integrating multiple security testing tools into LLM-driven workflows for secret scanning, static analysis, and vulnerability discovery.
      57
      Apache 2.0