Skip to main content
Glama

resemble-ai-connector

Agent Plugin + MCP server for Resemble AI media authenticity. Works with Grok Bot (Cursor Agent Plugins) and Muse (stdio MCP).

Use case

Give an assistant a complete authenticity workflow:

  1. List managed Detect Agents (social, news, documents, evidence, ID, web).

  2. Run an investigation against a public URL (SSE stream → verdict + run_id).

  3. Optionally submit a deepfake Detect job for audio/image/video scores, watermark, source tracing, or intelligence.

  4. Ask follow-up questions on a Detect report.

Docs: docs.resemble.ai · Auth: Authorization: Bearer <API_KEY> against https://app.resemble.ai/api/v2.

Related MCP server: SongCheck MCP

Tools

Tool

Purpose

resemble_list_detect_agents

List Detect Agents

resemble_run_investigation

Run agent on url or file_path

resemble_list_investigation_runs

Recent runs for an agent

resemble_get_investigation_run

Persisted run detail

resemble_create_detection

Deepfake Detect job

resemble_get_detection

Poll Detect result

resemble_ask_detection_question

Detect Intelligence Q&A

resemble_get_detection_answer

Poll Intelligence answer

resemble_account

API key sanity check

One-line install (Grok Bot)

Ask any Grok Bot:

Add Resemble MCP so that you can investigate media authenticity by following https://github.com/obaid/resemble-ai-connector/blob/main/instructions.md

That file is written for the bot: it adds MCP via uvx from this repo, smoke-checks, then does the job you named. Full steps: instructions.md.

Install (local)

python3 -m venv .venv
source .venv/bin/activate
pip install -e .
export RESEMBLE_API_KEY=...
resemble-mcp   # stdio MCP

Smoke test (no MCP host required):

python scripts/smoke_test.py

MCP transports

Host

Recommended config

Grok Bot

mcp.json → official Streamable HTTP https://mcp.resemble.ai/mcp with Authorization: Bearer ${RESEMBLE_API_KEY}

Muse / local

Install this package and use mcp.stdio.json (resemble-mcp) for Trust extras including resemble_secure_upload

This repo’s stdio server implements the Trust authenticity workflow (Detect Agents + Detect + secure upload) against the public REST API. Grok Bot can also use Resemble’s hosted action MCP at the same API key.

Grok Bot

This repo is an Agent Plugins package (plugin.json + mcp.json + skills/).

  1. Set RESEMBLE_API_KEY under Plugins → Configure (or pass env when adding a custom server).

  2. Install from marketplace after publish, or ask Grok Bot to add a custom stdio server using mcp.json.

  3. Submit path for marketplace: https://cursor.com/marketplace/publish

localhost URLs on your laptop are not reachable from Grok Bot. Prefer uvx --from git+… resemble-mcp or install on the bot computer.

Muse

  1. pip install -e . into Muse’s environment.

  2. Wire stdio MCP from muse/mcp.stdio.example.json.

  3. Append muse/AGENTS.md.snippet to agent instructions.

  4. Restart Muse / host and call resemble_list_detect_agents.

Security

  • Never commit .env or real keys.

  • Prefer public HTTPS media URLs; use zero_retention_mode when Detect must not retain uploads.

License

MIT

Available Tools

10 tools
resemble_accountA

Sanity-check the API key by fetching the Resemble account profile.

Inputs: no named parameters. Returns: result

resemble_ask_detection_questionC

Ask a natural-language question about a completed Detect report (Detect Intelligence).

Inputs: question (required), detect_uuid (required). Returns: result

resemble_create_detectionA

Submit a deepfake detection job for audio, image, or video.

Provide exactly one of url (public HTTPS) or file_path. wait=True sends Prefer: wait so the response includes a completed verdict when possible. Optional intelligence / watermark / source-tracing / reverse-search flags map to the Detect API.

Inputs: url, wait, signal, modality, +8 more. Returns: result

resemble_get_detectionA

Get a deepfake detection result by UUID. Set experts=true for all completed Intelligence results.

Inputs: uuid (required), experts. Returns: result

resemble_get_detection_answerC

Poll the answer for a Detect Intelligence question.

Inputs: detect_uuid (required), question_uuid (required). Returns: result

resemble_get_investigation_runB

Fetch a persisted Detect Agent investigation run by run_id.

Inputs: run_id (required), agent_uuid (required). Returns: result

resemble_list_detect_agentsA

List Resemble Detect Agents available to this API key (managed authenticity investigators).

Inputs: no named parameters. Returns: result

resemble_list_investigation_runsB

List recent investigation runs for a Detect Agent.

Inputs: agent_uuid (required). Returns: result

resemble_run_investigationB

Run a Detect Agent investigation on a public media/page URL or local file.

Prefer url. agent_uuid comes from resemble_list_detect_agents (e.g. investigate_social_content, verify_breaking_news, verify_document, website_check). Optional query is the investigation objective. Consumes the SSE stream and returns run_id, final verdict/intelligence, and a transcript excerpt.

Inputs: agent_uuid (required), url, query, file_path, +1 more. Returns: result

resemble_secure_uploadB

Upload private media to Resemble and return a short-lived media_token (1 hour) for Detect.

Inputs: file_path (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool maps to a distinct phase of the Detect workflow: account check, upload, detection submission/retrieval, intelligence Q&A, and agent investigations. Even the paired ask/get answer tools are clearly separated by their roles. No two tools appear to do the same thing.

    Naming Consistency4/5

    Most tools follow a clear resemble_verb_noun pattern, such as resemble_list_detect_agents and resemble_get_investigation_run. A few exceptions like resemble_account and resemble_secure_upload break the verb-first convention, but overall the naming remains predictable and readable.

    Tool Count5/5

    Ten tools is a well-scoped size for a deepfake detection server. Each tool covers a necessary capability without redundancy, and the count fits comfortably within the ideal range for a focused MCP server.

    Completeness4/5

    The surface covers account verification, secure uploads, detection submission and retrieval, intelligence Q&A, and the full investigation run lifecycle. The only notable gap is the lack of a way to list all detection jobs, which agents can work around by tracking UUIDs themselves.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers