MCP SETUP GUIDE
Connect AppGazers to ChatGPT for App Market Research
Set up AppGazers as a remote MCP server in the supported ChatGPT surface, authenticate with OAuth, and run an evidence-led app research prompt.
ChatGPT can use remote MCP servers on supported surfaces. For AppGazers, add https://appgazers.com/mcp as a Streamable HTTP server where the current ChatGPT interface offers MCP servers, then authenticate in the browser. ChatGPT desktop/IDE setup and ChatGPT on the web are distinct flows.
At a glance
| Surface | Setup route | Important boundary |
|---|---|---|
| ChatGPT desktop / Codex host | Settings → MCP servers → Add server → Streamable HTTP → Authenticate | Desktop, CLI, and IDE share the saved host configuration; restart open clients after saving |
| ChatGPT web | Developer mode, where available, then add the remote MCP app | Availability depends on the current plan and product surface |
| AppGazers | Use https://appgazers.com/mcp and OAuth | No manually copied secret or token-bearing URL is needed |
Choose the correct ChatGPT surface
OpenAI documents MCP servers in the ChatGPT desktop app through Settings → MCP servers. Add a server name, choose Streamable HTTP, enter the AppGazers endpoint, save the configuration, and restart open desktop, CLI, or IDE sessions on that Codex host before selecting Authenticate. Those local surfaces share the saved configuration.
ChatGPT on the web has a separate Developer mode path for MCP apps, subject to the availability OpenAI describes for the account. Do not use a local desktop configuration as proof that chatgpt.com is connected.
Add the remote endpoint and approve OAuth
Enter https://appgazers.com/mcp, not an API key or a token-bearing URL. The assistant should open the AppGazers authorization flow. Sign in with Google only on the expected AppGazers domain, review the requested scope, and return to ChatGPT after consent.
If authentication fails, remove the server entry, confirm the URL has no trailing path or copied secret, and retry from the supported MCP settings surface. If your account lacks the setting, consult OpenAI’s current availability documentation rather than bypassing OAuth.
Run a traceable market-research request
Start with read-only research. A narrow request produces a memo you can inspect instead of a broad claim about an entire app category.
Try this prompt
Use the AppGazers MCP tools to compare three [category] apps in [country]. Return each app’s store link, relevant catalog or rank evidence, estimated downloads or revenue explicitly marked as estimates, two recent review themes, and the sources retrieved. End with three hypotheses, each labeled as an inference rather than a fact.Check evidence and control access
Open the store links and compare the reported country and date with your question. Treat estimates as model outputs and public ad evidence as coverage-limited. Do not ask ChatGPT to infer private revenue, targeting, or intent from incomplete data.
Use mcp:read for research. Only approve mcp:user when you intentionally want an assistant to work with your AppGazers watchlist; review connected assistants later from the MCP page and revoke connections you no longer use.
Official sources reviewed
- OpenAI: MCP in ChatGPT — Official desktop and IDE MCP setup guidance.
- OpenAI: Developer mode and MCP apps — Official ChatGPT web Developer mode guidance.
- AppGazers MCP — AppGazers endpoint and OAuth scope guidance.
RESEARCH YOUR NEXT APP
Start with a niche. Leave with evidence.
AppGazers is free during beta. The research workspace opens after Google sign-in.
Explore rising apps