ClipSense

Model Context Protocol server for ClipSense - AI-powered mobile debugging through video analysis.
  • typescript

0

GitHub Stars

typescript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "clipsense--mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@gburanda/clipsense-mcp-server"
      ],
      "env": {
        "CLIPSENSE_API_KEY": "cs_sk_YOUR_API_KEY_HERE"
      }
    }
  }
}

ClipSense MCP Server enables you to run AI-powered video bug analysis directly inside your IDE workflow. By connecting an MCP client, you can upload screen recordings, have AI inspect crashes and UI issues, and receive actionable code fixes without leaving your development environment.

How to use

You use ClipSense by connecting your MCP client to the ClipSense MCP server. Once connected, you can analyze a bug video by instructing your editor or IDE assistant to process the video. The assistant will upload the video to ClipSense, run AI-based analysis, and present the root cause, timeline, visual evidence, and recommended fixes. You can then ask follow-up questions to focus on specific aspects such as network requests or a particular UI flow. Each analysis is treated independently, so re-analyze with a clearly defined focus if you want to explore a different angle.

How to install

Prerequisites: Node.js (v18+) and npm must be installed on your system. You will also need an API key from ClipSense to enable the MCP server.

curl -X POST "https://api.clipsense.app/api/v1/keys/request" \
  -H "Content-Type: application/json" \
  -d '{"email":"your-email@example.com"}'

# This installs the ClipSense MCP server globally
npm install -g @gburanda/clipsense-mcp-server

# Start using the server in your MCP configuration (example shown in the next sections) with your API key
# Ensure you replace YOUR_API_KEY with your actual key

npx -y @gburanda/clipsense-mcp-server --help

Configuration examples

Use the following MCP server configuration in your IDE by placing it in the appropriate MCP settings file for your editor. The server runs locally via npx and uses your API key for authentication.

{
  "mcpServers": {
    "clipsense": {
      "command": "npx",
      "args": ["-y", "@gburanda/clipsense-mcp-server"],
      "env": {
        "CLIPSENSE_API_KEY": "cs_sk_YOUR_API_KEY_HERE"
      }
    }
  }
}
{
  "mcpServers": {
    "clipsense": {
      "command": "npx",
      "args": ["-y", "@gburanda/clipsense-mcp-server"],
      "env": {
        "CLIPSENSE_API_KEY": "cs_sk_YOUR_API_KEY_HERE"
      }
    }
  }
}

Security and data handling

All video uploads and analysis are performed through the MCP server connection you establish in your IDE. Your API key controls access to the service, and data handling follows the standard security practices of the platform. Ensure you store your API key securely and rotate it if you suspect it may be compromised.

Troubleshooting

If you encounter issues, verify that the MCP settings file points to the ClipSense server configuration and that the API key is correctly set in the env block. Restart your IDE after updating the MCP settings.

Notes

The ClipSense MCP server supports multiple MCP clients and provides a consistent interface for video analysis across IDEs. Ensure your videos comply with size limits and formatting supported by the service.

Available tools

Video Bug Analysis

Analyzes local screen recordings of mobile app bugs to identify crashes, UI issues, and unexpected behavior.

AI-Powered Debugging

Uses AI to inspect video frames and produce actionable insights and root cause analysis.

Code Fix Suggestions

Provides concrete code changes to resolve the detected bugs.

Timeline breakdown

Generates a frame-accurate timeline of events leading to the bug.

Root cause analysis

Automatically identifies the underlying cause of the bug based on video evidence.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
ClipSense MCP Server - clipsense/-mcp-server | VeilStrat