​
Overview

The Probe.dev MCP (Model Context Protocol) server enables AI assistants to directly interact with the Probe.dev API and documentation. Our hosted MCP server uses the modern Streamable HTTP transport layer, providing a seamless integration experience.

​
Key Benefits

✅ No local installation - Fully hosted service
✅ Modern transport - Uses Streamable HTTP (SSE deprecated)
✅ Simple configuration - Just URL and API token
✅ Always up-to-date - Automatically reflects latest API changes
✅ Zero maintenance - No dependencies to manage

​
What You Can Do

  • Search documentation - Find information across all Probe.dev docs
  • Analyze media files - Run comprehensive analysis with FFprobe, MediaInfo, Probe Report, C2PA, and MediaStreamValidator
  • Manage usage - Check statistics and request logs
  • Authenticate requests - Automatically handle API authentication
You’ll need a Probe.dev API key to use the MCP server. Get yours at probe.dev/dashboard.

​
Supported Clients

The Probe.dev hosted MCP server works with any MCP-compatible client:

Cursor

Popular AI-powered code editor with MCP support

Claude Desktop

Official Anthropic desktop application

Continue

VS Code extension for AI coding assistance

Custom Clients

Any application supporting the MCP protocol

​
Quick Setup

​
Authentication

The hosted server supports two authentication methods:

​
Client Configuration

​
Cursor Setup

  1. Create MCP Configuration File Create or edit the file ~/.cursor/mcp.json: 
    mkdir -p ~/.cursor
touch ~/.cursor/mcp.json
  2. Add Probe.dev Server Configuration 
    {
  "mcpServers": {
    "probe-dev": {
      "url": "https://mcp.probe.dev/",
      "headers": {
        "Authorization": "Bearer your-api-token-here"
      }
    }
  }
}
  3. Restart Cursor to activate the MCP server
Replace your-api-token-here with your actual API key from probe.dev/dashboard.

​
Claude Desktop Setup

  1. Locate Configuration File
    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Edit Configuration 
    {
  "mcpServers": {
    "probe-dev": {
      "url": "https://mcp.probe.dev/",
      "headers": {
        "Authorization": "Bearer your-api-token-here"
      }
    }
  }
}
  3. Restart Claude Desktop

​
Continue (VS Code) Setup

  1. Install Continue Extension from the VS Code marketplace
  2. Configure MCP Server in Continue’s settings: 
    {
  "mcpServers": [
    {
      "name": "probe-dev",
      "url": "https://mcp.probe.dev/",
      "headers": {
        "Authorization": "Bearer your-api-token-here"
      }
    }
  ]
}

​
Available Tools

Once configured, your AI assistant will have access to these tools: 
Tool: search
Description: Search across all Probe.dev documentation
Example: "How do I authenticate with the API?"

​
Media Analysis

Tool: analyze_media_file
Description: Analyze media files using FFprobe, MediaInfo, Probe Report, C2PA, or MediaStreamValidator
Example: "Analyze this video file: https://example.com/video.mp4"

​
Usage Statistics

Tool: get_usage_stats
Description: Retrieve API usage statistics and metrics
Example: "Show my current API usage this month"

​
Request Logs

Tool: get_request_logs
Description: Access your API request history and logs
Example: "Show my recent failed requests"

​
Testing Your Setup

​
Basic Connectivity Test

Ask your AI assistant: 
"Can you search the Probe.dev documentation for authentication information?"

​
Expected Responses

✅ Working correctly - The assistant should:
  • Return specific documentation excerpts for searches
  • Provide detailed media analysis results
  • Show your actual usage statistics
❌ Not working - You might see:
  • “I don’t have access to that information”
  • “Tool not available” errors
  • Authentication failures

​
Troubleshooting

​
Usage Examples

"Find information about rate limits in the Probe.dev API"
→ Returns: Rate limit documentation with specific limits and headers

​
Media Analysis

"Analyze this video and tell me its codec, resolution, and duration:
https://example.com/sample.mp4"
→ Returns: Complete FFprobe analysis with video/audio stream details

​
Batch Operations

"Compare the codecs used in these three video files:
- https://example.com/video1.mp4
- https://example.com/video2.mkv  
- https://example.com/video3.avi"
→ Returns: Analysis of all three files with codec comparison

​
API Management

"Show me my API usage for the last week and identify any failed requests"
→ Returns: Usage statistics and error log analysis

​
Security Best Practices

API Key Security

  • Store API keys securely in configuration files
  • Never commit keys to version control
  • Rotate keys regularly
  • Use separate keys for different environments

Access Control

  • Limit key permissions to necessary scopes
  • Monitor usage in your dashboard
  • Set up usage alerts
  • Review access logs regularly

​
Advanced Configuration

​
Environment Variable Support

For enhanced security, some clients support environment variables: 
{
  "mcpServers": {
    "probe-dev": {
      "url": "https://mcp.probe.dev/",
      "headers": {
        "Authorization": "Bearer ${PROBE_API_TOKEN}"
      }
    }
  }
}

​
Query Parameter Alternative

If your client doesn’t support headers, use query parameters: 
{
  "mcpServers": {
    "probe-dev": {
      "url": "https://mcp.probe.dev/?token=your-api-token-here"
    }
  }
}

​
Getting Help

Documentation

Complete API reference and guides

Dashboard

Monitor usage and manage API keys

Discord Community

Get help from the community

API Status

Check current API status

​
Next Steps

Once your MCP server is working:
  1. Explore the API - Try different analysis tools and parameters
  2. Automate workflows - Use the assistant to streamline media processing
  3. Monitor usage - Set up alerts for quota limits
  4. Share feedback - Help us improve the MCP integration
The hosted MCP server automatically stays up-to-date with the latest Probe.dev API features and documentation changes.