Approvibe
Approvibe hosts the pages that the App Store and Google Play require for a mobile app (privacy policy, terms of use, support page, account deletion page), plus a smart link (one URL that sends iPhone users to the App Store, Android users to Google Play and desktop visitors to a page with a QR code). Pages are written by the developer or their AI agent and published through an MCP server or a REST API. Published URLs never break, even when the slug changes or the subscription ends.
The developer is the publisher of their pages and responsible for their content; Approvibe provides templates, an SDK reference, store requirements and lint checks, and hosts the pages.
Connect an agent
- MCP server (Streamable HTTP, JSON): https://approvibe.com/mcp, with the header
Authorization: Bearer sa_…(API key created in the dashboard: https://approvibe.com/dashboard/api-keys) - Claude Code:
claude mcp add --transport http approvibe https://approvibe.com/mcp --header "Authorization: Bearer sa_YOUR_KEY" - REST API: https://approvibe.com/api/v1 (OpenAPI: https://approvibe.com/api/v1/openapi.json)
Tools (MCP) / endpoints (REST)
- get_store_requirements — GET /api/v1/store-requirements
- get_templates — GET /api/v1/templates?type=&locale=
- get_sdk_reference — GET /api/v1/sdks?query=
- list_apps / create_app — GET, POST /api/v1/apps
- get_app / update_app — GET, PATCH /api/v1/apps/{id}
- declare_sdks — PUT /api/v1/apps/{id}/sdks
- get_page / upsert_page — GET, PUT /api/v1/apps/{id}/pages/{privacy|terms|support|delete-account}
- publish_app — POST /api/v1/apps/{id}/publish
- change_slug — POST /api/v1/apps/{id}/slug
- get_stats — GET /api/v1/apps/{id}/stats?days=
- list_requests / update_request — GET /api/v1/requests, PATCH /api/v1/requests/{id}
Page variables
{{app_name}}, {{developer}}, {{contact_email}}, {{last_updated}}, {{third_party_services}} (declared SDKs with the data they collect). Link other pages with relative links: privacy policy.
Public URLs of an app
- https://approvibe.me/{slug} — smart link
- https://approvibe.me/{slug}/privacy, /terms, /support, /delete-account — pages (?lang=fr to force a language)
- https://approvibe.me/{slug}/qr.svg — QR code
- https://approvibe.me/studio/{studio_slug} — the developer's studio page listing their apps (get_studio_page / update_studio_page)
Suggested prompt
Publish the store pages of this mobile app with Approvibe (MCP server "approvibe").
- Call get_store_requirements.
- Read this project: dependencies (package.json / pubspec.yaml / Podfile / build.gradle), the data the app collects, whether it has accounts, ads, in-app purchases, analytics.
- Call get_sdk_reference and match the dependencies against the
packagesfield. - Find the app with list_apps, or create it with create_app: its name, plus store_urls with the Apple ID / Android package name (they exist before publication) or the store URLs. Set the contact email and the developer name.
- Call declare_sdks with the matching SDK ids.
- Call get_templates, then write the 4 pages (privacy, terms, support, delete-account) with upsert_page in English, adapted to what the app REALLY does. Remove every [bracketed] placeholder and fix the lint warnings. Never invent data practices; ask me when unsure.
- Call publish_app and give me the URLs to paste in App Store Connect and the Play Console.