Hosted MCP server/Marketing

AppSigma - App Store ASO for AI agents MCP server

Hosted at appsigma.io·Streamable HTTP

AppSigma tracks App Store keyword rankings, competitors, and reviews for your apps. The provider documents two servers that should both be added: appsigma.io/mcp uses OAuth sign-in and covers your own app workspace, while api.appsigma.io/mcp uses an X-API-Key header and exposes the whole App Store, 22 tools, charts, price history, and cross-country reviews with 1,000 free credits for competitor research.

appsigma.io Streamable HTTP OAuth for appsigma.io/mcp; X-API-Key header for api.appsigma.io/mcp Server not checked yet Reviewed 2026-11-16
About

Where it fits

App marketers and ASO specialists who want their own rankings plus broad App Store research in the same assistant.

  • Sign in to your app workspace and check keyword rankings.
  • Compare competitors with the App Store research server.
  • Pull price history and cross-country reviews.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Add both AppSigma servers

The first server covers your own apps and uses OAuth sign-in. The second covers the whole App Store (22 tools, charts, price history, cross-country reviews) and uses an X-API-Key header.

  1. Add your app workspace (OAuth)

    Add the appsigma.io endpoint and complete the browser sign-in when your client asks.

    opencode mcp add appsigma --url https://appsigma.io/mcp
  2. Add the App Store research server (API key)

    Add the second endpoint with an AppSigma API key in the X-API-Key header. The provider says to add both servers.

    claude mcp add --transport http appsigma-store https://api.appsigma.io/mcp --header "X-API-Key: <APPSIGMA_API_KEY>" --scope project

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://appsigma.io/mcp
Host
appsigma.io · /mcp
Transport
Streamable HTTP
Authentication
OAuth for appsigma.io/mcp; X-API-Key header for api.appsigma.io/mcp
Server name
appsigma-app-store-aso-for-ai-agents
Listing type
Community or directory listing

The installer uses the server name appsigma-app-store-aso-for-ai-agents. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that appsigma-app-store-aso-for-ai-agents appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Sign in to your app workspace and check keyword rankings. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

AppSigma - App Store ASO for AI agents documentationhttps://appsigma.io/agent