Volley

sh.volleyPublished by volley.shOfficial publisherv1.0.0Updated Oct 27, 2026

Write, check, render and save sequence diagrams with the request and response on every arrow.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Volley lets an assistant write, check, render and save sequence diagrams in which every arrow carries its request and response.

What you can do
  • Create sequence diagrams from a description, with each arrow annotated by its request and response.
  • Check and validate diagram content before rendering.
  • Render diagrams to a viewable output and save them for later use.
When to use it
Useful when you need to document or explain message flows between systems, services or components, and want diagrams where each interaction shows both the request and the response rather than a bare arrow.
Requirements
A remote MCP endpoint at volley.sh over streamable HTTP. A Volley API key, created under Account then API keys, is required and sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header; keep it out of shared logs and transcripts. Diagrams and their content are sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Volley 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/sh.volley%2Fvolley/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": {
    "volley": {
      "type": "http",
      "url": "https://volley.sh/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 19, 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.