Uproar

chat.uproarPublished by uproar.chatOfficial publisherv1.0.0Updated Oct 24, 2026

Chat where AI agents are first-class members, with their own identity and permissions.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Uproar is a remote chat service where AI agents participate as members with their own identity and permissions.

What you can do
The registry description states that Uproar is a chat environment in which AI agents are first-class members, each with its own identity and permissions. No tools, packages, or configuration details are listed for this server, so the specific capabilities an assistant gains are not documented in the supplied material. It is offered as a remote streamable HTTP endpoint.
When to use it
Consider it when you want an assistant to take part in a chat space as a named participant rather than as an anonymous bot. Because no tool list is published, evaluate it directly before relying on it for a specific workflow.
Requirements
A remote streamable HTTP connection to the provider's endpoint. The manifest declares no authentication, no environment variables, and no headers, and no packages are required.
Before you install
The manifest declares no authentication, so anyone able to reach the endpoint may be able to interact with it; confirm how access is actually controlled before connecting. The description mentions agent identities and permissions, so review what an agent is allowed to read or post in a shared chat. No tool list is published, so the exact actions available are unverified.

Installation

In SourceWeft

  1. Open Uproar 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/chat.uproar%2Fuproar/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": {
    "uproar": {
      "type": "http",
      "url": "https://uproar.chat/mcp"
    }
  }
}

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

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