echosaw（echosaw 分析）

Echosaw Media Intelligence

Overview

Echosaw is a media intelligence platform — not just a transcription tool. It analyzes video, audio, and image files using AI (Amazon Rekognition, Transcribe, Comprehend, and Bedrock/Claude) and produces structured intelligence reports. Each report can include:

• Transcripts — Full speech-to-text output with timestamps
• Content moderation signals — Flagged content categories and confidence scores
• Sentiment analysis — Emotional tone detected across the media
• Visual object labels — Recognized objects, scenes, and activities in video/image frames
• Geographic metadata — Reverse-geocoded location data (Growth tier and above)
• LLM-generated summaries — AI-authored narrative summaries powered by Bedrock/Claude

The analysis pipeline: upload → malware scan (GuardDuty) → media probe (validation, metadata) → AI analysis (transcription, visual recognition, content moderation, sentiment) → LLM report generation (Bedrock/Claude) → packaging and delivery.

Available Tools

Workflow

Follow these steps to analyze media with Echosaw:

1. Submit media — Use echosaw_analyze_media (local file) or echosaw_analyze_media_url (remote URL) to submit media for analysis. The tool returns a mediaId and jobId.
2. Poll status — Call echosaw_check_job_status with the mediaId to monitor progress. The job progresses through states: PENDING → PROCESSING → COMPLETE. If still processing, wait a minute or two and check again.
3. Get results — Once the status is COMPLETE, call echosaw_get_analysis_results to retrieve the full intelligence report including summaries, transcripts, detected entities, and other outputs.
4. Download source media — Optionally call echosaw_download_media to get a presigned download URL for the source media file (valid for 1 hour).
5. Search your library — Use echosaw_search_media to find previously analyzed media by topic, content, or keyword.
6. Browse your library — Use echosaw_list_media to see all media items in your library.
7. Check your account — Use echosaw_get_profile to see your subscription tier, trial status, and account details.

Example Conversation

• "Analyze the video at /Users/me/Downloads/interview.mp4" → calls echosaw_analyze_media, returns a mediaId
• "What's the status of that analysis?" → calls echosaw_check_job_status
• "Show me the results" → calls echosaw_get_analysis_results for the full intelligence report
• "Get me a download link" → calls echosaw_download_media for a presigned URL
• "Search my media for anything about product launches" → calls echosaw_search_media
• "What media do I have in my library?" → calls echosaw_list_media
• "What plan am I on?" → calls echosaw_get_profile

Supported Formats

Additional supported formats via the MCP server: MOV, AVI, WebM, MKV (video); WAV, FLAC, AAC, OGG, M4A (audio); PNG, GIF, WebP, BMP, TIFF (image).

Pricing

Echosaw offers a free trial of the web UI — no payment required:

• 5 analysis uploads included
• 14-day trial window
• Full Premium-tier feature access during trial
• Start a trial at echosaw.com by entering your email
• Note: The free trial applies to the web interface only. MCP server access requires a paid plan (Developer, Growth, Pro, or Agency) with an API key.

Subscription tiers (monthly billing plus per-minute usage):

For full pricing details and plan comparison, visit echosaw.com/pricing.

Deprecated local install: npm install -g @echosaw/mcp-server (stdio, API key auth). Use the remote server instead.

Authentication (Remote Server — Recommended)

The remote MCP server at https://mcp.echosaw.com uses OAuth 2.0 for authentication. MCP clients that support OAuth (such as Claude Desktop, claude.ai, and Claude Code) will handle the authentication flow automatically.

No API key configuration is needed — the OAuth flow connects to your Echosaw account directly.

Authentication (Local Server — Deprecated)

1. Get an API key — Subscribe to a Developer, Growth, Pro, or Agency plan at echosaw.com/pricing. Your API key is provided in the welcome email and shown once (it is not recoverable after that).
2. Set the environment variable — Configure ECHOSAW_API_KEY in your MCP client:

{
  "mcpServers": {
    "echosaw": {
      "command": "echosaw-mcp",
      "env": {
        "ECHOSAW_API_KEY": "your-api-key"
      }
    }
  }
}

The same API key works for both the MCP server and the REST API. Authentication uses the API key only — no additional Cognito/JWT tokens are required.

Response Format

All tools return a standardized JSON response envelope:

Links

• Homepage: echosaw.com
• MCP Integration Guide: echosaw.com/developers/mcp-integration
• API Reference: echosaw.com/developers/api-reference
• Pricing: echosaw.com/pricing