AppFollow is an app store optimization and review management platform that tracks reviews, ratings, keyword rankings, and metadata for apps on the App Store and Google Play.
Agen.co connects to AppFollow through AppFollow's own hosted MCP server as an Official connector. Each user signs in with their own AppFollow account, so there is no app to register and no credentials to copy. AppFollow restricts which callback addresses can complete the sign-in, so you must ask AppFollow to allow Agen.co's before you connect.
Prerequisites
Prerequisites
- An AppFollow account for each person whose agents will use the connector.
- AppFollow must allow Agen.co's callback URLs before the sign-in can complete. Only AppFollow can add them, so this step cannot be done from Agen.co — see the steps below.
The errors you see until the callback URLs are allowed
The errors you see until the callback URLs are allowed
AppFollow must allow both callback URLs, and each one fails differently:
- If the Callback URL is not allowed, Connect fails: the sign-in tab shows
{"error":"invalid_request","hint":"invalid_redirect_uri"}instead of a login page. - If only the Gateway callback URL is missing, Connect and Add still succeed. The failure appears later: the first tool call from a user returns an authorization link, and opening it shows the same
invalid_redirect_urierror.
The callback URLs are specific to your Agen.co environment, so you request this once per environment.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- In the Select connector drawer, search for
AppFollowand select it. The Add AppFollow panel opens. - Copy both read-only URLs shown in the panel:
- Callback URL — completes the initial OAuth handshake between Agen.co and AppFollow.
- Gateway callback URL — used by the Agen.co MCP gateway for per-user authorization at runtime.
Contact AppFollow support, send both URLs, and ask them to allow the Agen.co callback hosts as redirect hosts for the AppFollow MCP server. AppFollow checks redirect URLs by host, so asking for the host rather than the exact path avoids a second request if a path changes. Wait for AppFollow's confirmation before you continue.
Return to the Add AppFollow panel (reopen it if you closed it) and fill in the field:
| Field | Required | Description |
|---|---|---|
| Instance Slug | Yes | Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Prefilled with appfollow. Use lowercase kebab-case. You can change it later from the connector's settings. |
| Callback URL | — | Read-only. Send it to AppFollow to allow (see above). |
| Gateway callback URL | — | Read-only. Send it to AppFollow to allow as well (see above) — the MCP gateway uses it for per-user authorization at runtime. |
- Click Connect. AppFollow opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
- Sign in to AppFollow and approve access.
- Back in Agen.co, the panel switches to Select the tools to import from AppFollow. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even if the AppFollow tab reported success.
AppFollow does not issue refresh tokens for this connection, so the connection must be re-authorized when its access token expires.
AppFollow's MCP server gives agents the same data as your AppFollow dashboard, scoped to your account:
| Area | What it covers |
|---|---|
| Apps | Find and track apps from the App Store and Google Play |
| Reviews | Read reviews, ratings, and review sentiment |
| ASO | Keyword rankings and opportunities, and app metadata |
| Reports | Shareable reports |
AppFollow keeps its tool list behind sign-in and does not publish one, so exact tool names are not listed here. The tool selection screen that appears after Connect shows exactly what your account serves, and you can turn off any tool you do not want agents to use. The areas above follow AppFollow's MCP page (checked 2026-10-07), not a tool list, so treat them as unverified and check the tool selection screen for what is actually available.
Enabling the AppFollow connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.