Storylayer Publishing

io.github.mikeslonePublished by GitHub account mikeslonev1.2.3Updated Oct 24, 2026

Hosted MCP for Instagram, Facebook, X, LinkedIn, Pinterest, and Ghost. OAuth 2.1, 38 tools.

The publisher's own server: SnowSure — Snow & Ski

Overview

AI-generated overview

Hosted MCP server that lets an assistant publish and manage content across Instagram, Facebook, X, LinkedIn, Pinterest, and Ghost.

What you can do
A remote, hosted MCP endpoint for social publishing. According to the registry description it covers Instagram, Facebook, X, LinkedIn, Pinterest, and Ghost, and exposes 38 tools. It authenticates with OAuth 2.1. No tool list is published, so the exact operations are not documented here.
When to use it
Worth adding when an assistant should draft, schedule, or publish posts to several social platforms and a Ghost site from one connection, instead of using each platform's own tooling.
Requirements
A remote streamable HTTP endpoint at the provider's hosted app; no local package or runtime is needed. Authentication is OAuth 2.1, so an account with the provider and authorization of the connected social and Ghost accounts are required. Network access to the endpoint is needed.
Before you install
It connects to live social and publishing accounts, so tools may post, edit, or delete public content and act on the user's behalf. OAuth 2.1 grants access to those accounts; review the scopes requested and revoke access when no longer needed. Content and account data pass through the third-party hosted service.

Installation

In SourceWeft

  1. Open Storylayer Publishing 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.mikeslone%2Fstorylayer/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": {
    "storylayer-publishing": {
      "type": "http",
      "url": "https://app.storylayer.ai/api/mcp"
    }
  }
}

README

This repository has no README.

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. v1.2.3LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Snowsure integrations