Echosaw

io.github.matthew-b-simpsonPublished by GitHub account matthew-b-simpsonv1.1.0Updated Oct 24, 2026

Media intelligence analysis for audio, video, and images via the Echosaw MCP server.

The publisher's own server: Echosaw

VerifiedSTDIODesktop onlyMedia & Design

Overview

AI-generated overview

Echosaw's local MCP server gives an assistant media intelligence analysis of audio, video and images through the Echosaw API.

What you can do
  • Analyze audio, video and image media through the Echosaw service.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
  • The server runs locally over stdio and forwards requests to the Echosaw API.
When to use it
Worth adding when you want an assistant to run media intelligence analysis on audio, video or image files and you already use or are willing to sign up for Echosaw.
Requirements
Runs as a local process over stdio, installed from the npm package @echosaw/mcp-server, so a Node.js runtime is needed. Requires an Echosaw API key supplied in the ECHOSAW_API_KEY environment variable, and network access to the Echosaw API. ECHOSAW_API_URL can override the API base URL, for example for staging.
Before you install
The Echosaw API key in ECHOSAW_API_KEY is a secret; keep it out of shared configuration. Media you submit is sent to the Echosaw service for analysis, so consider whether the content is sensitive. Desktop only; no web executable.

Installation

In SourceWeft

  1. Open Echosaw in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Echosaw integrations