Superflag

io.github.happycatlabsPublished by GitHub account happycatlabsv1.2.0Updated Oct 29, 2026

Connect agents to Superflag with scoped read, write, or read-write access through browser login.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Superflag is a remote MCP endpoint that connects agents to Superflag with scoped read, write, or read-write access granted through browser login.

What you can do
  • Connect an assistant to a Superflag account over a remote MCP endpoint.
  • Access is scoped as read-only, write, or read-write, chosen when connecting.
  • Authorization happens through a browser login rather than an API key.
  • No tool list is published, so the specific operations available are not documented here.
When to use it
Worth considering if you already use Superflag and want an AI assistant to work with that account under a limited read or write scope. Because no tools are documented, check the provider's own documentation before relying on it.
Requirements
A remote MCP connection to the Superflag endpoint over streamable HTTP. OAuth authentication is required, completed through a browser login. No environment variables or headers are declared.
Before you install
Granting write or read-write scope lets the assistant change data in your Superflag account; prefer read-only unless changes are intended. Access is tied to your browser login, so review which account and scope you authorize. The available tools are not listed, so verify capabilities before use.

Installation

In SourceWeft

  1. Open Superflag 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.happycatlabs%2Fsuperflag/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": {
    "superflag": {
      "type": "http",
      "url": "https://superflag.sh/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

3
  1. v1.2.0LatestOct 29, 2026
  2. v1.1.0Oct 26, 2026
  3. v1.0.0Oct 17, 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.