HRUM 바로

ai.hrumPublished by hrum.aiOfficial publisherv1.0.0Updated Oct 29, 2026

Draft copy and design changes for a 바로 site; only the site owner can publish them.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

HRUM 바로 lets an assistant draft copy and design changes for a 바로 website, with publishing left to the site owner.

What you can do
  • Draft copy for a 바로 site.
  • Draft design changes for a 바로 site.
  • Hand drafts to the site owner, who is the only one who can publish them.
  • No tool list is published, so the exact operations are not documented in the manifest.
When to use it
Useful when you maintain a 바로 site and want an assistant to prepare text or design edits as drafts for review, rather than editing the live site directly.
Requirements
A remote MCP endpoint at api.hrum.ai over streamable HTTP. A bearer token is required in the Authorization header: a 바로 AI key obtained from the HRUM console.
Before you install
The server requires a 바로 AI key sent as a bearer token in the Authorization header; treat it as a secret. Drafts are prepared for a site, so review them before the owner publishes, since publishing changes the public site.

Installation

In SourceWeft

  1. Open HRUM 바로 in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ai.hrum%2Fbaro/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": {
    "hrum": {
      "type": "http",
      "url": "https://api.hrum.ai/api/v1/partners/v1/baro/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 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.