Overview

The Echosaw remote MCP server at https://mcp.echosaw.com allows AI assistants and developer tools to interact with Echosaw’s media intelligence capabilities directly. It uses Streamable HTTP transport with OAuth 2.0 authentication — no local installation or API keys required. Submit media URLs for analysis, retrieve results, and download source files — all from within your AI-powered development environment.

What is MCP?

The Model Context Protocol is an open standard that enables AI models and developer tools to securely connect to external data sources and services. Echosaw’s remote MCP server exposes the same capabilities as the REST API in a format optimized for AI assistant consumption.

Quick Start (Remote Server)

No installation required. Add the Echosaw MCP server URL to your MCP client configuration:

{
  "mcpServers": {
    "echosaw": {
      "url": "https://mcp.echosaw.com"
    }
  }
}

OAuth 2.0 authentication is handled automatically by your MCP client. When you first connect, your client will open a browser window for you to sign in with your Echosaw account.

Claude Desktop Configuration

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "echosaw": {
      "url": "https://mcp.echosaw.com"
    }
  }
}

Claude Desktop supports OAuth 2.0 natively — it will prompt you to sign in when you first use an Echosaw tool.

Cursor Configuration

Add to your Cursor MCP settings:

{
  "mcpServers": {
    "echosaw": {
      "url": "https://mcp.echosaw.com"
    }
  }
}

Compatibility: mcp-remote Bridge

The configurations above use the native Streamable HTTP transport ("url" key), which requires your MCP client to support Streamable HTTP and OAuth 2.0 natively. If your client does not yet support these features, you can use the mcp-remote npm package as a bridge. It proxies the remote server through a local stdio transport and handles the OAuth flow for you.

{
  "mcpServers": {
    "echosaw": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.echosaw.com",
        "3334",
        "--host",
        "127.0.0.1"
      ]
    }
  }
}

The 3334 argument specifies the local port for the OAuth callback, and --host 127.0.0.1 binds the callback listener to localhost. On first connection, mcp-remote will open your browser for sign-in and cache the token for subsequent sessions.

You can add "--debug" to the args array for verbose logging while troubleshooting connection issues.

Available Tools

Example Workflow

1. Submit a URL: “Analyze the video at https://example.com/interview.mp4” — calls echosaw_analyze_media_url, returns a mediaId.
2. Check status: “What’s the status of that analysis?” — calls echosaw_check_job_status.
3. Get results: “Show me the results” — calls echosaw_get_analysis_results for the full intelligence report.
4. Download source media: “Get me a download link” — calls echosaw_download_media for a presigned URL.
5. Search your library: “Find all media about product launches” — calls echosaw_search_media.
6. Browse your library: “What media do I have?” — calls echosaw_list_media.
7. Check your account: “What plan am I on?” — calls echosaw_get_profile.
8. Check your organization: “Show me my team” — calls echosaw_get_organization.
9. List your folders: “Show me my folders” — calls echosaw_list_folders.
10. Create a folder: “Create a folder called Marketing” — calls echosaw_create_folder.
11. Move media to a folder: “Move that video to the Marketing folder” — calls echosaw_move_media.

Response Format

All tools return a standardized JSON response envelope: