SaaS Pro Max

io.github.abdurshdPublished by GitHub account abdurshdv0.3.0Updated Oct 31, 2026

Product analytics, error tracking, feature flags and SaaS operations with scoped OAuth access.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Remote MCP endpoint for SaaS Pro Max that gives an assistant scoped OAuth access to product analytics, error tracking, feature flags and SaaS operations.

What you can do
  • Product analytics: read and work with product usage data through the hosted service.
  • Error tracking: inspect application errors reported to the platform.
  • Feature flags: manage feature flag settings as part of SaaS operations.
  • SaaS operations: handle day-to-day operational tasks in the SaaS Pro Max account.
  • The exact tool list is not published, so the precise actions available are not documented here.
When to use it
Useful when your team already runs on SaaS Pro Max and wants an assistant to look at analytics, errors and feature flags, or carry out operational tasks, without leaving the chat. Less relevant if you do not use that platform.
Requirements
A remote MCP endpoint at saaspro.dev reached over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so you need a SaaS Pro Max account and must complete the OAuth consent flow. No environment variables or headers are declared.
Before you install
Access is granted through OAuth with scopes, so review which scopes you approve during consent. The tool list is not published, so it is unclear which actions read data and which change feature flags or other settings; treat write operations with care. Analytics and error data from your product is handled by a third-party hosted service.

Installation

In SourceWeft

  1. Open SaaS Pro Max 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.github.abdurshd%2Fsaas-pro-max/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": {
    "saas-pro-max": {
      "type": "http",
      "url": "https://saaspro.dev/api/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. v0.3.0LatestOct 31, 2026

Score

83% 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
  • 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.