getstoreready-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projects | List the authenticated user's GetStoreReady projects. |
| create_project | Create a new GetStoreReady project. Returns its id and editor URL. |
| get_project | Get a summary of a project — name, platforms, screen count, store languages, and editor URL. |
| get_screens | List screenshot screens on a project with text layer ids, current copy, and device image asset ids. Use this before update_screen_text or when planning copy from screenshots. |
| get_screen_imagesA | Return raw app screenshot images (device layer assets) as vision input for the host AI. Use with your client vision to read UI content, then call update_screen_text. Also returns a JSON index mapping images to screen indices. |
| upload_screenshots | Upload one or more raw app screenshots. Prefer "path" (a local file path — the server reads it directly, no base64 round-trip through the tool call) over "data" (base64), which is only a fallback for images that do not exist as a local file. Not tied to a project yet — pass the returned assetIds to apply_template or place_screenshot_image. |
| list_templates | List available templates from the GetStoreReady API with this user's owned/locked state. Use categories, name, and excerpt to pick a fit — do not hardcode template keys in the agent. |
| apply_template | Apply a template to a project, either by its exact key or 'random' to pick any unlocked one. RECOMMENDED FLOW: call this WITHOUT assetIds first — it applies instantly with the template's own placeholder content and shows up live in an already-open editor tab. Then call upload_screenshots + place_screenshot_image to fill in real photos one screen at a time (each placement also shows up live). |
| place_screenshot_image | Place an already-uploaded image into a screen that already exists on a project. Each call shows up live in an already-open editor tab. |
| update_screen_textA | Update the marketing headline/body text on one screen (template text layer, not in-app UI text). Preserves template highlight styling (italic accent, pill) when the layer uses runs — call get_screens to see highlightStyle/templateHighlight. Optionally pass highlightPhrase to control which word gets the accent (e.g. "workouts" or "#habits"). |
| update_screen_designC | Update one screen design — background color/gradient and/or multiple text layers at once. |
| bulk_update_designsB | Apply the same background (e.g. white) and/or text updates across multiple or all screens. Example: set every screen background to solid white. |
| list_store_languagesC | List active and available store languages for a project. |
| add_store_languageA | Add one or more store languages to a project (e.g. de_DE for German). Does not translate — call translate_project after. |
| get_listingB | Get store listing / ASO text for a project in one locale. |
| update_listingC | Update store listing / ASO text for a project in one language. |
| get_ai_creditsA | Check AI credit balance and whether translation is available. |
| estimate_translationA | Estimate AI credit cost before translating listing copy and/or screen text. Always call this before translate_project when credits matter. |
| translate_project | AI-translate store listing copy and/or screenshot text layers between store languages. Deducts AI credits. Call estimate_translation first. Requires a registered account (not guest). |
| export_project | Enqueue a PNG/ZIP export for the project. Optionally wait for completion and save locally. |
| detect_app | Inspect a local mobile app repository and infer stack, app name, platforms, locales, and marketing-relevant screens (tabs/routes). Use before bootstrap_store_project. |
| discover_screenshots | Find existing marketing/store screenshots under common folders (marketing/, fastlane/screenshots/, screenshots/, etc.) inside an app repo. Returns local file paths ready for upload_screenshots. |
| capture_screenshots | Capture marketing screenshots from a local Flutter / React Native / Swift app using the iOS Simulator (simctl + optional Maestro) or Android emulator (adb). Writes PNGs under marketing// by default. Prefer Maestro or deepLinks for distinct screens; without them later shots may duplicate the home screen. Requires macOS+Xcode for iOS. After capture, call discover_screenshots or bootstrap_store_project. |
| bootstrap_store_project | Create a GetStoreReady project from a local app repo: detect metadata, find screenshots, upload them, apply a template, and return screen text layers for copywriting. After this, use update_screen_text (and optionally update_listing) with marketing copy. |
| get_app_store_link | Get App Store Connect link status for a project (credential label, app id, bundle id). Requires Premium/Pro. Set up credentials in the web UI first. |
| preview_app_store_push | Review what would be pushed to App Store Connect — blockers, warnings, locale plans, and optional remote diff vs the live store. Call this before push_to_app_store. |
| push_to_app_store | Enqueue an App Store Connect push (listing + screenshots). Requires Premium/Pro and a linked app. Always call preview_app_store_push first and confirm with the user when blockers exist. |
| get_app_store_push_jobB | Get status of an App Store push job. Optionally wait until it completes. |
| get_google_play_linkA | Get Google Play Console link status for a project (credential, package name). Requires Premium/Pro. Set up credentials in the web UI first. |
| preview_google_play_pushA | Review what would be pushed to Google Play — blockers, warnings, locale plans, and optional remote diff. Call before push_to_google_play. |
| push_to_google_playA | Enqueue a Google Play push (listing, screenshots, app icon). Requires Premium/Pro and a linked app. Call preview_google_play_push first. |
| get_google_play_push_jobC | Get status of a Google Play push job. Optionally wait until it completes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/getstoreready/getstoreready-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server