Skip to main content
Glama
opensubtitles

OpenSubtitles MCP Server

Official
by opensubtitles
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

OpenSubtitles MCP Server

A TypeScript/Node.js-based MCP (Model Context Protocol) server for OpenSubtitles API integration. This server provides subtitle search and download functionality with a freemium model, using the Kong gateway at api.opensubtitles.com for all API management.

Features

  • Comprehensive Search: Search subtitles using all OpenSubtitles API parameters (title, IMDB ID, TMDB ID, file hash, etc.)

  • Multiple Download Formats: Support for SRT, ASS, and VTT subtitle formats

  • File Hash Calculation: Calculate OpenSubtitles hash for exact movie file matching

  • Rate Limiting: Integrated with Kong gateway for proper rate limiting

  • Freemium Model: Unlimited search, downloads limited by API key status

Related MCP server: Arr Suite MCP Server

Installation & Usage

The OpenSubtitles MCP Server supports three modes:

  • HTTP Mode: Web server for n8n workflows, browser access, and HTTP integrations

  • Stdio Mode (Local): Run locally for Claude Desktop integration

  • Stdio Mode (Remote): Connect to hosted server at mcp.opensubtitles.com

1. HTTP Mode (Recommended for Server Deployment)

Run as a web server on port 1620:

# Install dependencies
npm install
npm run build

# Start HTTP server
npm start
# or
PORT=1620 MCP_MODE=http node dist/index.js

Access points:

  • Health Check: http://localhost:1620/health

  • API Info: http://localhost:1620/

  • Web Interface: http://localhost:1620/web (Browser UI - No Node.js required!)

  • Direct API: http://localhost:1620/proxy (POST requests)

  • Tools List: http://localhost:1620/tools (Schema discovery)

  • MCP Endpoint: http://localhost:1620/sse (Server-Sent Events)

2. Stdio Mode (For Claude Desktop)

Quick Start with npx

npx @opensubtitles/mcp-server

Install via mcp-get

npx @michaellatman/mcp-get@latest install @opensubtitles/mcp-server

Claude Code Integration

For claude-code environments, you can add the server using the claude mcp add-json command:

claude mcp add-json "opensubtitles" '{"command":"npx","args":["-y","@opensubtitles/mcp-server@latest"],"env":{"MCP_MODE":"stdio","LOG_LEVEL":"info"},"disabled":false}'

Claude Desktop Integration - Local Mode

Add to your Claude Desktop configuration:

{
  "mcpServers": {
    "opensubtitles": {
      "command": "npx",
      "args": ["-y", "@opensubtitles/mcp-server"],
      "env": {
        "MCP_MODE": "stdio",
        "OPENSUBTITLES_USER_KEY": "your_api_key_here"
      }
    }
  }
}

Claude Desktop Integration - Remote Mode

Connect to the hosted server at mcp.opensubtitles.com:

{
  "mcpServers": {
    "opensubtitles": {
      "command": "npx",
      "args": ["-y", "@opensubtitles/mcp-server", "remote-proxy.js"]
    }
  }
}

Or using the dedicated remote command:

{
  "mcpServers": {
    "opensubtitles": {
      "command": "npx",
      "args": ["-y", "mcp-opensubtitles-remote"]
    }
  }
}

MCP Tools

1. search_subtitles

Search for subtitles with comprehensive parameter support:

Parameters:

  • query (string): Text search query

  • imdb_id (number): IMDB ID for exact matching

  • tmdb_id (number): TMDB ID for exact matching

  • parent_imdb_id (number): Parent IMDB ID for TV series

  • parent_tmdb_id (number): Parent TMDB ID for TV series

  • season_number (number): Season number for TV episodes

  • episode_number (number): Episode number for TV episodes

  • year (number): Release year

  • moviehash (string): OpenSubtitles file hash for exact matching

  • moviebytesize (number): File size in bytes for hash matching

  • languages (string): Comma-separated language codes (e.g., 'en,es,fr')

  • machine_translated (string): Include machine translated subtitles

  • ai_translated (string): Include AI translated subtitles

  • hearing_impaired (string): Include hearing impaired subtitles

  • foreign_parts_only (string): Include foreign parts only

  • trusted_sources (string): Only trusted sources

  • order_by (string): Sort order

  • order_direction (string): Sort direction (asc/desc)

Example:

await mcpClient.callTool("search_subtitles", {
  query: "The Matrix",
  year: 1999,
  languages: "en"
});

2. download_subtitle

Download subtitle content by ID:

Parameters:

  • subtitle_id (string, required): Subtitle ID from search results

  • format (string): Subtitle format (srt, ass, vtt) - defaults to 'srt'

  • user_api_key (string): Optional user API key for authenticated downloads

Example:

await mcpClient.callTool("download_subtitle", {
  subtitle_id: "123456",
  format: "srt",
  user_api_key: "your_api_key"
});

3. calculate_file_hash

Calculate OpenSubtitles hash for local movie files:

Parameters:

  • file_path (string, required): Path to the movie file

Example:

await mcpClient.callTool("calculate_file_hash", {
  file_path: "/path/to/movie.mkv"
});

Usage Examples

Search by Movie Title

await mcpClient.callTool("search_subtitles", {
  query: "Inception",
  year: 2010,
  languages: "en"
});

Search by File Hash

// First calculate the hash
const hashResult = await mcpClient.callTool("calculate_file_hash", {
  file_path: "/path/to/inception.mkv"
});

// Then search using the hash
await mcpClient.callTool("search_subtitles", {
  moviehash: "8e245d9679d31e12",
  moviebytesize: 12909756
});

Search TV Show Episodes

await mcpClient.callTool("search_subtitles", {
  parent_imdb_id: 944947, // Game of Thrones
  season_number: 1,
  episode_number: 5,
  languages: "en"
});

n8n Workflow Integration

The OpenSubtitles MCP Server has native n8n MCP client support for seamless workflow automation. Connect directly to the MCP server using n8n's built-in MCP client tools.

1. Start Server in HTTP Mode

First, start the MCP server in HTTP mode:

# Option 1: Use npm script (recommended)
npm start

# Option 2: Direct command with custom port
MCP_MODE=http PORT=1620 node dist/index.js

# Option 3: Using environment variables
export MCP_MODE=http
export PORT=1620
node dist/index.js

The server will be available at:

  • Base URL: http://localhost:1620

  • Health Check: http://localhost:1620/health

  • MCP Endpoint: http://localhost:1620/message (Streamable HTTP)

  • Force JSON: http://localhost:1620/json (Plain JSON for debugging)

  • Debug Info: http://localhost:1620/debug (Server diagnostics)

  • Legacy MCP: http://localhost:1620/sse (Server-Sent Events)

2. n8n MCP Client Configuration

Using n8n Native MCP Client

Configure the n8n MCP Client Tool node:

  • Server URL: http://localhost:1620/message (or your server URL)

  • Transport: HTTP Streamable

  • Protocol: Model Context Protocol (MCP)

Search Subtitles with MCP Client

Configure the MCP Client node with these parameters:

{
  "tool": "search_subtitles",
  "arguments": {
    "query": "The Matrix", 
    "year": 1999,
    "languages": "en"
  }
}

Alternative: Direct HTTP Request

For manual HTTP integration, use HTTP Request node:

{
  "method": "POST",
  "url": "http://localhost:1620/message",
  "headers": {
    "Content-Type": "application/json"
  },
  "body": {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "search_subtitles",
      "arguments": {
        "query": "The Matrix",
        "year": 1999,
        "languages": "en"
      }
    }
  }
}

Download Subtitle with MCP Client

{
  "tool": "download_subtitle",
  "arguments": {
    "file_id": 123456,
    "user_api_key": "{{ $env.OPENSUBTITLES_API_KEY }}"
  }
}

Calculate File Hash with MCP Client

{
  "tool": "calculate_file_hash",
  "arguments": {
    "file_path": "/path/to/movie.mkv"
  }
}

3. n8n Workflow Examples

Basic Search Workflow

  1. MCP Client Tool: Search for subtitles using movie title

  2. Code Node: Parse search results and extract file IDs

  3. MCP Client Tool: Download best matching subtitle

  4. File System Node: Save subtitle to disk

Automated Processing Workflow

  1. File Trigger: Monitor folder for new movie files

  2. MCP Client Tool: Calculate file hash

  3. MCP Client Tool: Search subtitles by hash for exact match

  4. Conditional Node: Check if subtitles found

  5. MCP Client Tool: Download subtitle if found

  6. File System Node: Save subtitle next to movie file

Benefits of Native MCP Integration

  • Auto-discovery: Tools are automatically discovered via MCP protocol

  • Type Safety: Full schema validation for tool arguments

  • Error Handling: Proper MCP error responses

  • Tool Documentation: Inline help and parameter descriptions

  • JSON Compatibility: Automatic plain JSON responses for n8n clients

  • Debug Support: Built-in debugging endpoints for troubleshooting

Troubleshooting n8n Integration

If you encounter JSON parsing errors:

  1. Try Force JSON Endpoint: Use http://localhost:1620/json instead of /message

  2. Check Debug Info: Visit http://localhost:1620/debug to verify server status

  3. Verify User-Agent: Server auto-detects n8n clients (node, n8n, langchain, mcpClientTool)

  4. Check Logs: Look for "Sending plain JSON response for n8n compatibility" messages

4. Environment Variables for n8n

Set these environment variables in your n8n instance:

# OpenSubtitles API Key (optional but recommended)
OPENSUBTITLES_API_KEY=your_api_key_here

# MCP Server URL (if running on different host/port)
MCP_SERVER_URL=http://localhost:1620

5. Response Format

All n8n HTTP requests will receive JSON-RPC 2.0 responses:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "Search results or download data..."
      }
    ]
  }
}

6. Error Handling in n8n

Add error handling nodes to catch common issues:

  • Rate Limit (429): Retry after delay or notify user to get API key

  • Invalid API Key (401): Alert administrator to check API key

  • Network Errors: Retry mechanism or alternative endpoint

  • File Not Found: Skip processing or log error

7. Production Deployment

For production n8n workflows:

# Run MCP server as background service
nohup MCP_MODE=http PORT=1620 node dist/index.js > mcp-server.log 2>&1 &

# Or use PM2 for process management
pm2 start dist/index.js --name "opensubtitles-mcp" -- --env MCP_MODE=http PORT=1620

# Or use Docker
docker run -d -p 1620:1620 -e MCP_MODE=http opensubtitles-mcp-server

This integration allows you to automate subtitle operations in n8n workflows, perfect for media processing pipelines, batch subtitle downloads, or automated movie library management.

Web Browser Interface

For users who don't want to install Node.js or configure MCP, we provide a full web interface:

Access

  • URL: http://mcp.opensubtitles.com/web

  • Requirements: Any modern web browser

  • No Installation: Works immediately without setup

Features

  • 🔍 Search Subtitles: Search by title, year, IMDB ID, languages

  • 💾 Download Subtitles: Download by file ID from search results

  • 🔢 Calculate Hash: Generate OpenSubtitles hash for movie files

  • 📊 Real-time Results: Instant feedback with formatted results

  • 🎯 User-friendly: Clean interface with loading states and error handling

Direct HTTP API

For developers and automation:

# Search subtitles
curl -X POST http://mcp.opensubtitles.com/proxy \
  -H "Content-Type: application/json" \
  -d '{"tool": "search_subtitles", "arguments": {"query": "Matrix", "year": 1999}}'

# Download subtitle
curl -X POST http://mcp.opensubtitles.com/proxy \
  -H "Content-Type: application/json" \
  -d '{"tool": "download_subtitle", "arguments": {"file_id": 123456}}'

# List available tools
curl http://mcp.opensubtitles.com/tools

Rate Limiting & API Keys

Anonymous Usage

  • Search: Unlimited

  • Downloads: 0 per day (Kong enforced)

With OpenSubtitles API Key

  • Search: Unlimited

  • Downloads: Based on your OpenSubtitles account quota

Getting an API Key

  1. Register at OpenSubtitles.com

  2. Get your free API key

  3. Set the OPENSUBTITLES_USER_KEY environment variable or pass it in tool calls

Development

Prerequisites

  • Node.js 18.0.0 or higher

  • TypeScript

Setup

git clone <repository>
cd mcp-opensubtitles
npm install

Building

npm run build

Development Commands

# HTTP Mode (Web Server)
npm run dev                # Build and run HTTP server on port 1620
npm start                  # Run built HTTP server

# Stdio Mode (Claude Desktop)
npm run dev:stdio          # Build and run stdio mode
npm start:stdio            # Run built stdio mode

# Development with Auto-rebuild
npm run watch

Testing

# For HTTP mode testing
curl http://localhost:1620/health        # Health check
curl http://localhost:1620/             # API info

# For Stdio mode testing
npm test                   # Run evaluation tests
npm run inspector          # Debug with MCP Inspector (stdio mode)

# MCP evaluation tests
npx mcp-eval evals/evals.ts dist/index.js

Environment Variables

OPENSUBTITLES_API_BASE=https://api.opensubtitles.com  # Default Kong gateway
NODE_ENV=production
PORT=1620
OPENSUBTITLES_USER_KEY=your_api_key_here  # Optional

Architecture

The server uses a clean architecture with the following components:

  • MCP Server Core (src/server.ts): Main MCP protocol implementation

  • Kong API Client (src/api-client.ts): HTTP client for Kong gateway communication

  • Tools (src/tools/): Individual tool implementations

  • Utilities (src/utils/): Helper functions for hash calculation

All API requests go through the Kong gateway at api.opensubtitles.com, which handles:

  • Rate limiting enforcement

  • API key validation

  • Request routing to OpenSubtitles API

  • Error handling and responses

Error Handling

The server provides helpful error messages for common scenarios:

  • Rate Limit Exceeded: "Download limit reached. Get your free API key at opensubtitles.com/api"

  • Invalid API Key: "Invalid API key. Please check your OpenSubtitles API key"

  • File Not Found: Clear file path validation messages

  • Network Errors: Descriptive network connectivity messages

Contributing

  1. Fork the repository

  2. Create a feature branch

  3. Make your changes

  4. Add tests for new functionality

  5. Submit a pull request

License

MIT License - see LICENSE file for details

Support

Available Tools

3 tools
calculate_file_hashC

Calculate OpenSubtitles hash for local movie files

ParametersJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the movie file

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'calculate' but doesn't specify if this is a read-only operation, what the output format is (e.g., hash string), or any performance considerations like processing time for large files. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a hash value), potential errors (e.g., file not found), or how the result might be used with sibling tools. For a tool with no structured behavioral data, this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with 'file_path' clearly documented as 'Path to the movie file'. The description adds no additional meaning beyond this, such as file format requirements or path syntax examples, but the schema adequately covers the parameter, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'calculate' and the resource 'OpenSubtitles hash for local movie files', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'download_subtitle' or 'search_subtitles', which are related but distinct operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as whether it's for verifying file integrity or preparing for subtitle searches. It lacks context on prerequisites, like needing a local file, or exclusions, such as not working with remote files.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

download_subtitleC

Download subtitle content by file ID. Downloads in original format with force_download=true by default for direct file download.

ParametersJSON Schema
NameRequiredDescriptionDefault
file_idYesFile ID from search results (found in files array of subtitle results)
file_nameNoDesired file name for the downloaded subtitle
in_fpsNoInput FPS for subtitle conversion (must use with out_fps)
out_fpsNoOutput FPS for subtitle conversion (must use with in_fps)
timeshiftNoTime shift in seconds to add/remove (e.g. 2.5 or -1)
force_downloadNoSet subtitle file headers to 'application/force-download' for direct file download (default: true)
user_api_keyNoYour OpenSubtitles API key for authenticated downloads
usernameNoOpenSubtitles.com username (alternative to API key)
passwordNoOpenSubtitles.com password (use with username)

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the default 'force_download=true' and that it downloads 'in original format', which adds some context. However, it fails to disclose critical behaviors: authentication requirements (implied by parameters but not stated), rate limits, error handling, or what the output looks like (e.g., file data vs. metadata). For a download tool with 9 parameters, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Download subtitle content by file ID') and adds a useful detail about defaults. There's no wasted verbiage, and it's appropriately sized for the tool's complexity. However, it could be slightly more structured by separating the default behavior into a second sentence for clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is incomplete. It lacks information on authentication (though parameters hint at it), output format (e.g., binary file vs. text), error cases, and how parameters interact. Without annotations or output schema, the description should compensate more to guide the agent effectively, but it falls short.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema: it implies 'file_id' is the primary identifier and mentions the default for 'force_download'. However, it doesn't explain relationships between parameters (e.g., 'in_fps' and 'out_fps' must be used together) or provide additional semantic context, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('download') and resource ('subtitle content by file ID'), making the purpose unambiguous. It distinguishes from sibling tools like 'calculate_file_hash' and 'search_subtitles' by focusing on downloading rather than hashing or searching. However, it doesn't explicitly mention what distinguishes it from potential non-sibling alternatives beyond the basic action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions a default behavior ('force_download=true by default') but doesn't explain when to override this or when to use other tools like 'search_subtitles' first. There's no context about prerequisites or typical workflows, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_subtitlesC

Search for subtitles using OpenSubtitles API with comprehensive parameter support

ParametersJSON Schema
NameRequiredDescriptionDefault
queryNoText search query
imdb_idNoIMDB ID for exact movie/series matching
tmdb_idNoTMDB ID for exact movie/series matching
parent_imdb_idNoParent IMDB ID for TV series
parent_tmdb_idNoParent TMDB ID for TV series
season_numberNoSeason number for TV episodes
episode_numberNoEpisode number for TV episodes
yearNoRelease year
moviehashNoOpenSubtitles file hash for exact matching
moviebytesizeNoFile size in bytes for hash matching
languagesNoComma-separated language codes (e.g., 'en,es,fr')
machine_translatedNoInclude machine translated subtitles (exclude, include, only)
ai_translatedNoInclude AI translated subtitles (exclude, include, only)
hearing_impairedNoInclude hearing impaired subtitles (exclude, include, only)
foreign_parts_onlyNoInclude foreign parts only subtitles (exclude, include, only)
trusted_sourcesNoOnly trusted sources (exclude, include, only)
order_byNoSort order (language, download_count, new, rating)
order_directionNoSort direction (asc, desc)
usernameNoOpenSubtitles.com username for authentication
passwordNoOpenSubtitles.com password for authentication

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'OpenSubtitles API' and 'comprehensive parameter support,' but fails to describe critical behaviors: authentication requirements (implied by username/password parameters), rate limits, pagination, error handling, or the nature of search results (e.g., list of subtitle entries). For a tool with 20 parameters and no annotations, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence: 'Search for subtitles using OpenSubtitles API with comprehensive parameter support.' It is front-loaded with the core action and API context, with no wasted words. Every part earns its place by conveying essential information concisely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (20 parameters, no annotations, no output schema), the description is incomplete. It lacks details on authentication, rate limits, result format, and usage scenarios. While the schema covers parameters well, the description does not compensate for missing behavioral and output context, making it inadequate for guiding an agent effectively in this rich environment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with each parameter well-documented (e.g., 'Text search query' for 'query', 'IMDB ID for exact movie/series matching' for 'imdb_id'). The description adds minimal value beyond this, only noting 'comprehensive parameter support' without explaining parameter interactions or usage patterns. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Search for subtitles using OpenSubtitles API with comprehensive parameter support.' It specifies the verb ('search'), resource ('subtitles'), and API source ('OpenSubtitles API'), making the action clear. However, it does not explicitly differentiate from sibling tools like 'download_subtitle' or 'calculate_file_hash,' which would require mentioning that this is for searching/filtering rather than downloading or hashing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'comprehensive parameter support' but does not specify scenarios, prerequisites (e.g., authentication needs), or comparisons to sibling tools like 'download_subtitle' for retrieval or 'calculate_file_hash' for matching. This leaves the agent without context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • Changeddownload_subtitle2 fields changed
      • changedInput schema / properties / force_download / description
        Previous value: -"Set subtitle file headers to force download"New value: +"Set subtitle file headers to 'application/force-download' for direct file download (default: true)"
      • removedInput schema / properties / sub_format
        Removed value: -{
-  "description": "Subtitle format (from /infos/formats endpoint, e.g. srt, ass, vtt)",
-  "type": "string"
-}
  2. 3 tool updates
    • First observedcalculate_file_hash
    • First observeddownload_subtitle
    • First observedsearch_subtitles
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: calculate_file_hash for local file processing, search_subtitles for finding subtitles via API, and download_subtitle for retrieving specific subtitle files. There is no overlap in functionality, making tool selection unambiguous for an agent.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case naming (calculate_file_hash, download_subtitle, search_subtitles). The naming is predictable and readable throughout the set.

Tool Count3/5

With only 3 tools, the server feels thin for the OpenSubtitles domain, which typically involves more operations like uploading subtitles, managing user accounts, or handling subtitle formats. While core functions are covered, the count is borderline minimal.

Completeness4/5

The tools cover the essential workflow: hash calculation for identification, searching for subtitles, and downloading them. However, there are minor gaps such as no upload or management tools, which agents might need for full subtitle lifecycle coverage but can work around.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/opensubtitles/mcp.opensubtitles.com'

If you have feedback or need assistance with the MCP directory API, please join our Discord server