Fuxux

io.github.abogitoffPublished by GitHub account abogitoffv1.2.1Updated Oct 24, 2026

Schedule social posts on 12 platforms: create, edit, reschedule, delete, and list your queue.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Fuxux lets an assistant manage a social media posting queue across 12 platforms: create, edit, reschedule, delete and list scheduled posts.

What you can do
  • Create scheduled social posts across 12 platforms
  • Edit, reschedule or delete posts already in the queue
  • List the current posting queue
When to use it
Useful when you plan and publish social content and want an assistant to draft, adjust or clear scheduled posts without opening the Fuxux dashboard.
Requirements
Remote MCP endpoint at fuxux.com over streamable HTTP. Authentication is required: either OAuth sign-in with a Fuxux account or a Fuxux API key (fx_live_...) sent as a Bearer token in the Authorization header.
Before you install
The server can change live publishing schedules: edits and deletions affect posts that may already be queued to go out. The Authorization header carries a Fuxux API key, so treat it as a secret. Connected social accounts and post content are handled by Fuxux.

Installation

In SourceWeft

  1. Open Fuxux 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.abogitoff%2Ffuxux/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": {
    "fuxux": {
      "type": "http",
      "url": "https://www.fuxux.com/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

4
  1. v1.2.1LatestOct 10, 2026
  2. v1.2.0Sep 29, 2026
  3. v1.1.0Sep 29, 2026
  4. v1.0.0Sep 26, 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.