Flaghand

com.flaghandPublished by flaghand.comOfficial publisherv0.1.4Updated Nov 7, 2026

Agents draft and schedule future social posts over MCP; immediate posting needs your passkey.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant draft and schedule future social media posts, with immediate posting gated by a passkey.

What you can do
  • Draft social media posts for the assistant to prepare on your behalf
  • Schedule posts to publish at a future time
  • Publish immediately only after passkey confirmation
When to use it
Useful when you want an assistant to help prepare and queue social media content ahead of time, while keeping a human check on anything that goes out right away.
Requirements
A remote MCP endpoint at app.flaghand.com over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The server can create and schedule posts that will later be published publicly under your account; review drafts before scheduling. Immediate posting is gated by a passkey, so keep that credential private. OAuth grants the server access to your Flaghand account.

Installation

In SourceWeft

  1. Open Flaghand 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/com.flaghand%2Fflaghand/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": {
    "flaghand": {
      "type": "http",
      "url": "https://app.flaghand.com/mcp/via/registry"
    }
  }
}

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

5
  1. v0.1.4LatestNov 7, 2026
  2. v0.1.3Nov 3, 2026
  3. v0.1.2Oct 29, 2026
  4. v0.1.1Oct 26, 2026
  5. v0.1.0Oct 26, 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.