Connect DiscoverApps over MCP
One MCP server. Muse, ChatGPT, Claude, Cursor, or any MCP-capable agent. Explore niches, watch apps, see what changed.
{
"mcpServers": {
"discoverapps": {
"url": "https://api.discoverapps.dev",
"headers": {
"Authorization": "Bearer <API_KEY>"
}
}
}
}Add your Bearer API key from /start after you sign in. <API_KEY> is a slot, not a real key.
credits stretch · agents are the UI · no ASO cockpit.
What MCP is
MCP is how an agent calls tools over a standard connector. DiscoverApps is one MCP server: explore a niche, watch an app, see what changed. You paste the block once, then ask in the host you already use.
Auth
Sign in at /start and create an API key. Every call sends Authorization: Bearer <API_KEY>. The copy block uses <API_KEY> as a slot.
Tools you’ll get
explore_nicheExplore a nichewatch_appWatch an appdiff_appSee what changed
What you can ask
| You say | What happens |
|---|---|
| Explore hiking apps in the US | Niche landscape of related apps |
| What’s already shipping in focus timers? | Browse a slice before you build |
| Watch TrailNotes | Adds a watch on that listing |
| What changed on TrailNotes this week? | Digest / listing diff |
| Show the timeline for FocusFlow | Listing history over time |
FAQ
- Do I need credits first?
- Yes, $14 to start from /start, then connect MCP.
- Is this an ASO dashboard?
- No. Agents are the UI; digests and history, not a cockpit.
- Where do I get an API key?
- After sign-in at /start.
- Does it work offline / without the host?
- You use DiscoverApps through your agent.
- What about automated monitoring?
- $19/mo for watches, digests, and webhooks.
- Which hosts work?
- Muse, ChatGPT, Claude, Cursor, or any MCP-capable agent.
- What if I see an auth error?
- Replace <API_KEY> with a key from /start. The slot is not a real key.
Muse