Forvibe MCP Server Overview

Connect Forvibe to supported AI clients through the hosted Model Context Protocol server.

Updated 2026-10-24
4 min read

Forvibe exposes a hosted, stateless Streamable HTTP MCP server at https://forvibe.app/mcp. Supported AI clients can read and manage your Forvibe projects without a local server process.

The public MCP surface currently contains 111 tools, 5 resource templates, and 4 prompts. The Tools Reference is checked against the server catalog in automated tests so additions and removals cannot silently leave this documentation behind.

What the public server can do

  • Projects and ASO: manage projects, keywords, competitors, rankings, visibility history, alerts, search, and top charts.
  • Store listings: read, stage, localize, version, and explicitly publish App Store Connect and Google Play listing changes.
  • Screenshots: inspect store screenshots, and plan, edit, translate, render, and push Screenshot Studio sets.
  • Reviews and review simulation: analyze App Store and Google Play reviews and run App Store metadata rejection-risk simulations.
  • Monetization: synchronize and manage subscriptions, in-app purchases, localizations, pricing indexes, and scheduled price changes on both stores.
  • App Store features: list and delete Custom Product Pages, and manage In-App Events that already exist in Forvibe, including localization and push status. New Custom Product Pages are made from a Screenshot Studio set.
  • The Forvibe agent: read your chats with the agent, send it messages, and approve or decline the steps it asks about. Where the autonomous agent is on, read its log, daily reviews, proposals, and results, and act on its proposals.

Forvibe's own console agent has additional internal tools. Workflow, Tracking, organization, attachment, project-deletion, and selected image-generation tools are not part of the public MCP contract. In particular, create Screenshot Studio sets (their opening pages use AI artwork), the custom product page sets made from them, and In-App Event artwork in the Forvibe dashboard; the public MCP can plan, manage, translate, and push the resulting records.

Documented clients

Use the client-specific guide because configuration keys, authentication support, plan limits, and UI labels differ:

  • Claude custom connectors (Claude web, Desktop, and mobile) and Claude Code
  • Cursor and Windsurf
  • VS Code with GitHub Copilot Agent mode
  • Gemini CLI and Gemini Code Assist Standard or Enterprise
  • ChatGPT web with Developer mode and a custom MCP app
  • OpenAI Codex in the ChatGPT desktop app, CLI, and IDE extension

Other Streamable HTTP MCP clients may also work if they can send a Bearer token or complete OAuth 2.1 discovery, but they are not covered by a verified setup guide here.

Authentication and safety

  • OAuth 2.1 + PKCE + Dynamic Client Registration: preferred when the client supports Forvibe's browser consent flow.
  • Personal API key: use Authorization: Bearer fvk_live_… for clients that need header-based authentication.
  • Listing edits are staged until publish_listings is called. Publishing and store pushes are outward-facing actions and should only run after an explicit request.
  • AI-powered operations can consume the same organization credits used by the Forvibe dashboard.

Start with the Quickstart, then follow the guide for your exact client.