iran-apps-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IRAN_APPS_MCP_PROXY | No | Optional HTTP proxy for requests to both stores. A comma-separated list is tried in turn. System proxy variables are ignored. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ap_searchA | Search Cafe Bazaar and/or Myket for apps and games by name; returns package names, ratings and store URLs. Use first to find a package name, then ap_app for details or ap_compare for both stores. Bazaar cards carry rating, category, approximate installs and a price when paid; Myket cards only name and tagline (ap_app has the rest). |
| ap_appA | Get one app's metadata from one store: version, rating and rating count, installs, size, update date, developer, price, description. Bazaar also gives version_code, a 1-5 star histogram, changelog and permission count; Myket also the first publish date and developer_id. installs is approximate (a rounded range). Prices are Toman, 0 = free. Metadata only: no APK download. To see both stores at once use ap_compare. |
| ap_compareA | Compare one package across Cafe Bazaar and Myket: version, rating, rating count, installs, size, update date, price. Returns each store's figures (null when the app is not listed there) and a diff: which store has the newer version, the rating difference (bazaar minus myket). Use for "is the app up to date on Myket?" or "which store rates it higher". Ratings are not shared between stores. |
| ap_topA | List the top ('best') or newest ('new') apps or games of a store, per category or store-wide. Store-wide 'best' is Bazaar's trending list or Myket's editorial must-have list (no ranking guarantee). 'new' needs a category. Get slugs from ap_categories (they differ per store). Then ap_app or ap_compare on a package. |
| ap_categoriesA | List the category slugs of a store for apps and games, to pass as ap_top category. Slugs differ between the stores (Bazaar 'tools' = Myket 'productivity'). Myket names are Persian. The Bazaar game list is the set that was verified to return results, not necessarily every game category. |
| ap_similarA | List apps the store shows as related to one app: Bazaar gives three groups (related, others also installed, similar), Myket one. Use to find alternatives or competitors of an app; then ap_compare or ap_app on a result. |
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 6 tools
Each tool has a distinct role: search finds packages, ap_app fetches single-store details, ap_compare spans both stores, ap_top returns rankings, ap_categories supplies slugs, and ap_similar surfaces related apps. The main mild overlap is between ap_search and ap_top as discovery entry points, but descriptions clearly delineate their use.
All tools share a uniform 'ap_' prefix followed by a short lowercase noun/verb token (ap_search, ap_app, ap_compare, ap_top, ap_categories, ap_similar). No mixed conventions or camelCase deviations.
Six tools form a tight, well-scoped set for a read-only multi-store app explorer. Each tool earns its place with no redundancy or padding.
The surface covers the core read-only lifecycle: discovery (search, top, categories, similar), detail (app) and cross-store comparison (compare). Metadata-only is an explicit design choice, so missing APK download is expected; a review or developer-lookup tool would round it out further.