Pixelfed Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Pixelfed instance API: instance info and public timelines.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that connects an assistant to a Pixelfed instance's API for instance information and public timelines.

What you can do
Read instance information from a Pixelfed server, such as its configuration and metadata, through the instance API. Browse public timelines to see posts shared publicly on that instance. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to look up details about a Pixelfed instance or follow its public timeline while working on the desktop. It is not aimed at private accounts, posting, or managing a profile.
Requirements
Runs as a local process on the user's machine, installed from the npm package pixelfed-mcp over stdio, so Node.js is needed. Desktop only; no web execution. No environment variables, headers, or authentication are declared, though the target Pixelfed instance must be reachable over the network.
Before you install
Only public instance data and public timelines are described, so treat anything read as public. No credentials are declared, but confirm which instance the server points at before use, since requests go to that third-party server. Posting or account-changing actions are not documented.

Installation

In SourceWeft

  1. Open Pixelfed Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.