Apparent

fyi.apparentPublished by apparent.fyiOfficial publisherv1.0.0Updated Oct 26, 2026

Mobile app analytics in plain words: live activity, reviews and sales, ads, and why a number moved.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP server that gives an assistant plain-language mobile app analytics: live activity, reviews, sales, ads, and explanations of metric changes.

What you can do
  • Ask about live app activity and usage trends.
  • Review app store reviews and sales figures.
  • Look into ad performance.
  • Get plain-language explanations of why a metric moved.
When to use it
Useful when you want an assistant to answer questions about a mobile app's performance — activity, reviews, revenue, ads — or to help explain a change in a metric without digging through dashboards yourself.
Requirements
A remote MCP endpoint at app.apparent.fyi using streamable HTTP. Requires an Apparent personal token, created on the Connect page under Your agents, sent as a bearer token in the Authorization header. No local runtime or environment variables needed.
Before you install
The Authorization header carries a personal access token; keep it secret and revoke it if exposed. The token is described as read-only, so the server should not change data, but it does expose your app's analytics, reviews and sales data to the assistant.

Installation

In SourceWeft

  1. Open Apparent in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/fyi.apparent%2Fapparent/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "apparent": {
      "type": "http",
      "url": "https://app.apparent.fyi/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.