← Registry

Content Tools

reqo.me

An MCP server for the REQO service that manages videos, captions, and editing projects.

WebMCP3 endpoints12 known toolsFirst detected September 11, 2026Last detected September 11, 2026

ENDPOINT 1

https://reqo.me/mcp

No auth detected

MCP server metadata

Name
reqo
Version
1.0.0
Capabilities
toolsresourcesexperimental.mcp-apps.uiResources
Server instructions

REQO is a browser-based screen recorder and video editor. Authentication is a NextAuth session cookie from an interactive human sign-in; there are no API keys and no client-credentials flow, so tools that touch a workspace fail with a sign-in message until the user has signed in. health_check needs no auth.

Known tools 8

health_check

Liveness probe for the REQO service.

Inferred read-only
list_videos

List videos in the caller's active workspace.

Inferred read-only
get_video

Fetch one video by id, including its metadata and playback URLs.

Inferred read-only
get_captions

Caption status for a video, or the subtitle file itself.

Inferred read-only
list_projects

List the editing projects the caller can see, most recently updated first.

Inferred read-only
create_project

Create a video editing project.

Potential side effects
transcribe_video

Transcribe media stored in REQO with Whisper large-v3 and return timed segments.

Inferred read-only
show_plans

Return the Free and Pro plan comparison as a renderable panel plus text.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.reqo]
url = "https://reqo.me/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "reqo": {
      "type": "http",
      "url": "https://reqo.me/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: reqo
Remote MCP URL: https://reqo.me/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "reqo": {
      "url": "https://reqo.me/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "reqo": {
      "type": "http",
      "url": "https://reqo.me/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "reqo",
  "transport": "streamable-http",
  "url": "https://reqo.me/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://reqo.me

No auth detected

MCP server metadata

Name
WebMCP
Capabilities
declarative

Known tools 1

reqo_generate_video

Generate a video from a text prompt with REQO's AI Studio. Submit the description; the editor opens with the generation queued.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.webmcp]
url = "https://reqo.me"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://reqo.me"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://reqo.me

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "webmcp": {
      "url": "https://reqo.me"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://reqo.me"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://reqo.me"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 3

https://reqo.me/mcp/docs

No auth detected

MCP server metadata

Name
reqo-docs
Version
1.0.0
Capabilities
toolsresourcesexperimental.mcp-apps.uiResources
Server instructions

Answers questions about REQO from its published documentation: guides, tool pages, pricing and the authentication reference. Start with search_docs, then get_doc for the full text of a match. Nothing here needs authentication and nothing here can change state - to take actions in a user's workspace, use the product server at /mcp instead.

Known tools 3

search_docs

Search REQO's guides, tool pages and reference documents.

Inferred read-only
get_doc

Fetch the full text of a document returned by search_docs, by its id.

Inferred read-only
list_docs

List every indexed document with its id, title and kind.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.reqo-docs]
url = "https://reqo.me/mcp/docs"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "reqo-docs": {
      "type": "http",
      "url": "https://reqo.me/mcp/docs"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: reqo-docs
Remote MCP URL: https://reqo.me/mcp/docs

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "reqo-docs": {
      "url": "https://reqo.me/mcp/docs"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "reqo-docs": {
      "type": "http",
      "url": "https://reqo.me/mcp/docs"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "reqo-docs",
  "transport": "streamable-http",
  "url": "https://reqo.me/mcp/docs"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.