> ## Documentation Index
> Fetch the complete documentation index at: https://docs.probe.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Integration Guide

> Connect to the Probe.dev hosted MCP server with Cursor, Claude Desktop, and other MCP clients

## 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

<Note>
  You'll need a Probe.dev API key to use the MCP server. Get yours at [probe.dev/dashboard](https://www.probe.dev/dashboard).
</Note>

## Supported Clients

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

<CardGroup cols={2}>
  <Card title="Cursor" icon="cursor">
    Popular AI-powered code editor with MCP support
  </Card>

  <Card title="Claude Desktop" icon="anthropic">
    Official Anthropic desktop application
  </Card>

  <Card title="Continue" icon="code">
    VS Code extension for AI coding assistance
  </Card>

  <Card title="Custom Clients" icon="gear">
    Any application supporting the MCP protocol
  </Card>
</CardGroup>

## Quick Setup

### Authentication

The hosted server supports two authentication methods:

<Tabs>
  <Tab title="Authorization Header (Recommended)">
    ```json theme={null}
    "headers": {
      "Authorization": "Bearer your-api-token"
    }
    ```
  </Tab>

  <Tab title="Query Parameter">
    ```
    https://mcp.probe.dev/?token=your-api-token
    ```
  </Tab>
</Tabs>

## Client Configuration

### Cursor Setup

1. **Create MCP Configuration File**
   Create or edit the file `~/.cursor/mcp.json`:

   ```bash theme={null}
   mkdir -p ~/.cursor
   touch ~/.cursor/mcp.json
   ```

2. **Add Probe.dev Server Configuration**
   ```json theme={null}
   {
     "mcpServers": {
       "probe-dev": {
         "url": "https://mcp.probe.dev/",
         "headers": {
           "Authorization": "Bearer your-api-token-here"
         }
       }
     }
   }
   ```

3. **Restart Cursor** to activate the MCP server

<Note>
  Replace `your-api-token-here` with your actual API key from [probe.dev/dashboard](https://www.probe.dev/dashboard).
</Note>

### 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**
   ```json theme={null}
   {
     "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:
   ```json theme={null}
   {
     "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:

### Documentation Search

```
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:

<CodeGroup>
  ```text Basic Test theme={null}
  "Can you search the Probe.dev documentation for authentication information?"
  ```

  ```text API Test theme={null}
  "Analyze this sample video file using FFprobe: https://probelibrary.s3.amazonaws.com/sample-source.mp4"
  ```

  ```text Usage Test theme={null}
  "What's my current API usage statistics?"
  ```
</CodeGroup>

### 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

<AccordionGroup>
  <Accordion icon="exclamation-triangle" title="Authentication Issues">
    **Symptoms**: "401 Unauthorized" responses, authentication errors

    **Solutions**:

    * Verify your API key is correct at [probe.dev/dashboard](https://www.probe.dev/dashboard)
    * Ensure the Authorization header format is: `Bearer your-api-token`
    * Check for extra spaces or quotes around the token
    * Confirm your API key has the necessary permissions
  </Accordion>

  <Accordion icon="plug" title="Connection Problems">
    **Symptoms**: "MCP server not responding", connection timeouts

    **Solutions**:

    * Check your internet connection
    * Verify the URL is correct: `https://mcp.probe.dev/`
    * Check for firewall/proxy issues blocking HTTPS connections
    * Try accessing the URL directly in your browser (should show MCP status)
  </Accordion>

  <Accordion icon="gear" title="Configuration Issues">
    **Symptoms**: Tools not appearing, "0 tools enabled"

    **Solutions**:

    * Validate your JSON configuration syntax
    * Ensure the `url` field is correctly formatted
    * Check that headers are properly structured
    * Restart your MCP client completely after configuration changes
  </Accordion>

  <Accordion icon="circle-question" title="Tool Not Working">
    **Symptoms**: Specific tools fail or return errors

    **Solutions**:

    * Check the [API status page](https://status.probe.dev)
    * Verify your account has sufficient quota
    * Test the API directly with cURL to isolate issues
    * Check request logs in your [dashboard](https://www.probe.dev/dashboard)
  </Accordion>
</AccordionGroup>

## Usage Examples

### Document Search

```text theme={null}
"Find information about rate limits in the Probe.dev API"
→ Returns: Rate limit documentation with specific limits and headers
```

### Media Analysis

```text theme={null}
"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

```text theme={null}
"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

```text theme={null}
"Show me my API usage for the last week and identify any failed requests"
→ Returns: Usage statistics and error log analysis
```

## Security Best Practices

<CardGroup cols={2}>
  <Card title="API Key Security" icon="key">
    * Store API keys securely in configuration files
    * Never commit keys to version control
    * Rotate keys regularly
    * Use separate keys for different environments
  </Card>

  <Card title="Access Control" icon="shield-check">
    * Limit key permissions to necessary scopes
    * Monitor usage in your dashboard
    * Set up usage alerts
    * Review access logs regularly
  </Card>
</CardGroup>

## Advanced Configuration

### Environment Variable Support

For enhanced security, some clients support environment variables:

```json theme={null}
{
  "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:

```json theme={null}
{
  "mcpServers": {
    "probe-dev": {
      "url": "https://mcp.probe.dev/?token=your-api-token-here"
    }
  }
}
```

## Getting Help

<CardGroup cols={2}>
  <Card title="Documentation" icon="book" href="/api-reference/introduction">
    Complete API reference and guides
  </Card>

  <Card title="Dashboard" icon="gauge" href="https://www.probe.dev/dashboard">
    Monitor usage and manage API keys
  </Card>

  <Card title="Discord Community" icon="discord" href="https://discord.gg/kYvSfywhru">
    Get help from the community
  </Card>

  <Card title="API Status" icon="chart-line" href="https://status.probe.dev">
    Check current API status
  </Card>
</CardGroup>

## 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

<Tip>
  The hosted MCP server automatically stays up-to-date with the latest Probe.dev API features and documentation changes.
</Tip>