Skip to main content
Glama
appolabs

Appo MCP

Official
by appolabs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_hookA

Generate a custom React hook for an @appolabs/appo SDK feature. Returns TypeScript code with types, error handling, and loading states.

generate_componentB

Generate a UI component that uses @appolabs/appo SDK features. Returns a complete React component with SDK integration.

scaffold_featureB

Scaffold complete feature integration including hook, component, and types. Returns multiple files with integration instructions.

validate_setupB

Validate @appolabs/appo SDK installation and configuration. Analyzes package.json and optionally checks import patterns.

check_permissionsB

Analyze permission handling patterns in code for a specific SDK feature. Returns analysis with suggestions for proper permission flow.

diagnose_issueB

Diagnose common @appolabs/appo SDK integration issues. Provides diagnosis with solutions and code fixes.

create_appA

Creates a new app for the authenticated user. Non-destructive — executes immediately. Authenticate once with appo login (or set APPO_TOKEN). Omit prep_mode when app source code is available in context.

list_appsA

Lists all apps owned by the authenticated user. Non-destructive.

configure_appA

Configures an app's content fields (name, base_url) and who prepares it (prep_mode). Reversible - executes immediately. Content-only, matching the CLI apps update; icon is set_icon, webview injection is a dashboard concern.

set_iconA

Sets an app's icon from a publicly reachable https URL. The server fetches, validates, and stores the image. Reversible — executes immediately.

set_permissionsA

Sets an app's native permissions. Pass permissions as an object of { name: boolean }; keys are tracking, camera, microphone, nfc. Only the keys you include change — the rest and every usage message are preserved. Reversible — executes immediately. Request only permissions the app actually uses (store-review discipline).

publish_appA

Starts publication to the chosen stores. Destructive — call with confirm:true to execute; without it returns a preview of the target stores.

unpublish_appA

Removes an app from the chosen stores. Destructive — call with confirm:true to execute; without it returns a preview of the target stores.

preview_appA

Returns the open-on-device payload: iOS TestFlight URL, Android deeplink, QR target URL, and per-platform readiness. Non-destructive — executes immediately.

get_app_overviewA

Returns app configuration, publication state, and metadata in one call. Start here. If app_id is omitted and you own exactly one app, that app is used.

get_build_statusB

Returns the status of a build by id. Poll until the status reaches ready (then publish_app) or failed. Non-destructive.

get_rejectionA

Returns the Appo publication status and the curated required action for a rejected app. Never exposes raw reviewer text. Non-destructive.

get_fix_recipeA

Returns code-free Appo remediation recipes for the current rejection. Non-destructive.

send_pushA

Sends a push to the app's devices. Destructive — call with confirm:true to send; without it returns a preview.

trigger_resubmissionA

Resubmits a rejected app for review. Destructive — call with confirm:true to execute; without it returns a preview. Requires a customer-owned Apple credential.

generate_universal_linksA

Generate the well-known configuration files needed for iOS Universal Links and Android App Links. Returns apple-app-site-association and assetlinks.json with hosting instructions.

Prompts

Interactive templates invoked by user choice

NameDescription
setup_wizardInteractive setup guidance for integrating @appolabs/appo SDK into a new or existing project
integrate_featureStep-by-step guide for integrating a specific SDK feature
debug_assistantInteractive troubleshooting assistant for SDK issues

Resources

Contextual data attached and managed by the client

NameDescription
API: pushAPI reference for appo.push
API: biometricsAPI reference for appo.biometrics
API: cameraAPI reference for appo.camera
API: locationAPI reference for appo.location
API: hapticsAPI reference for appo.haptics
API: storageAPI reference for appo.storage
API: shareAPI reference for appo.share
API: networkAPI reference for appo.network
API: deviceAPI reference for appo.device
Examples: pushCode examples for push feature
Examples: biometricsCode examples for biometrics feature
Examples: cameraCode examples for camera feature
Examples: locationCode examples for location feature
Examples: hapticsCode examples for haptics feature
Examples: storageCode examples for storage feature
Examples: shareCode examples for share feature
Examples: networkCode examples for network feature
Examples: deviceCode examples for device feature
Best PracticesIntegration best practices and patterns
TroubleshootingCommon issues and solutions
SDK OverviewOverview of @appolabs/appo SDK capabilities
Universal LinksGuide to setting up iOS Universal Links and Android App Links
Appo Ecosystem — start hereMap of all Appo resources (SDK, CLI, MCP, wrapper, dashboard, API) and when to use each — read before any Appo task

Latest Blog Posts

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/appolabs/appo-mcp'

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