Roost

dev.workers.perch-app.roostPublished by roost.perch-app.workers.devOfficial publisherv1.0.0Updated Oct 24, 2026

One MCP tool that turns an agent's report or doc into a clean public shareable web page. No signup.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Roost is a remote MCP server that turns an agent's report or document into a clean, public, shareable web page, with no signup required.

What you can do
Publish a report or document produced by the assistant as a public web page that can be shared by link. The server exposes a single tool for this conversion, so the assistant can hand off finished content and get back a page. No account or signup step is described.
When to use it
Useful when an assistant has produced a report or document and you want to share it as a readable web page rather than a raw file or chat transcript.
Requirements
A remote MCP endpoint reached over streamable HTTP; no packages, environment variables or headers are declared. No signup or account is mentioned.
Before you install
Published pages are described as public and shareable, so anything sent to the server should be treated as visible to anyone with the link. Avoid submitting confidential or personal content. The server is hosted by a third party, so content leaves your machine.

Installation

In SourceWeft

  1. Open Roost 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/dev.workers.perch-app.roost%2Froost/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": {
    "roost": {
      "type": "http",
      "url": "https://roost.perch-app.workers.dev/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

56% 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 listedRequired15 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.