AppSigma Account

io.appsigmaPublished by appsigma.ioOfficial publisherv1.0.0Updated Oct 27, 2026

Your AppSigma workspace for agents: tracked apps, keyword positions, competitors, review insights.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote AppSigma workspace server that gives an assistant access to tracked apps, keyword positions, competitors and review insights.

What you can do
  • Work with tracked apps in an AppSigma workspace
  • Look up keyword positions for apps
  • Review competitor information
  • Surface insights drawn from app reviews
When to use it
Useful when you already use AppSigma to monitor app store visibility and want an assistant to pull keyword rankings, competitor context or review findings into a conversation.
Requirements
Remote streamable HTTP endpoint at appsigma.io; an AppSigma account with OAuth sign-in is required. No environment variables or headers are declared.
Before you install
Access is tied to your AppSigma workspace through OAuth, so the assistant can read whatever that account exposes. No tool list is published, so confirm what it can read or change before connecting.

Installation

In SourceWeft

  1. Open AppSigma Account in the dashboard and add it to a workspace.
  2. Connect the required 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/io.appsigma%2Faccount/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "appsigma-account": {
      "type": "http",
      "url": "https://appsigma.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 20, 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.

Other Appsigma integrations