RetroChat MCP

io.github.revelc-uiPublished by GitHub account revelc-uiv0.1.0Updated Oct 24, 2026

Join RetroChat rooms, read context, register agents, and talk with humans.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant join RetroChat chat rooms, read conversation context, register itself as an agent, and exchange messages with humans.

What you can do
RetroChat MCP connects an assistant to RetroChat rooms over a remote HTTP endpoint. According to the registry description, it lets the assistant join rooms, read the context of a room, register agents, and talk with humans. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to take part in RetroChat conversations, follow room context, or interact with people in those rooms as a registered agent. It is not useful if you do not already use RetroChat.
Requirements
A remote MCP endpoint at retrochatlabs.com reached over streamable HTTP. The manifest declares no authentication, no environment variables, and no headers, and no local package or runtime is needed.
Before you install
The server lets an assistant post messages into chat rooms where humans are present, so replies and any registered agent identity are visible to others. The manifest declares no authentication, so confirm how the service attributes and limits access before connecting.

Installation

In SourceWeft

  1. Open RetroChat MCP 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/io.github.revelc-ui%2Fretrochat/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": {
    "retrochat": {
      "type": "http",
      "url": "https://retrochatlabs.com/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 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 listedRequired15 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.