Library

win.postappPublished by postapp.winOfficial publisherv0.1.0Updated Oct 24, 2026

Publish one HTML file, get a live installable app URL. No account, no review, no queue.

VerifiedStreamable HTTPWeb executableFiles & StorageDeveloper Tools

Overview

AI-generated overview

Publishes a single HTML file to a live, installable app URL and lets an assistant browse or search the published library.

What you can do
This remote MCP server turns one HTML file into a hosted, installable app URL, with no account, review, or queue involved. It also exposes the published library for browsing and searching. Publishing requires a bearer publishing key; without one, the library can still be browsed and searched read-only.
When to use it
Worth adding when an assistant should ship a self-contained HTML page as a shareable, installable app, or look through what others have already published. Read-only browsing needs no key, so it can be tried before committing to publishing.
Requirements
A remote streamable HTTP endpoint at postapp.win; nothing to install locally. Publishing needs an Authorization header carrying a bearer publishing key, obtained by solving a proof-of-work challenge at the key endpoint. Omitting the header allows read-only browsing and searching. Network access is required.
Before you install
The Authorization header carries a publishing key, so treat it as a secret and avoid exposing it in logs or shared configuration. Publishing makes content publicly reachable at a live URL, and the input states there is no review or queue, so anything published is effectively immediate and hard to retract. The key endpoint asks for a proof-of-work challenge to be solved.

Installation

In SourceWeft

  1. Open Library in the dashboard and add it to a workspace.
  2. 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/win.postapp%2Flibrary/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.

{
  "mcpServers": {
    "library": {
      "type": "http",
      "url": "https://postapp.win/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% 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

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

  • 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

    Publish an icon in the registry entry.

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