DramaSub runs a Model Context Protocol (MCP) server so AI agents can answer subtitle questions with sourced data: search our drama pages, read drama summaries and subtitle guides, and convert subtitle files between SRT, VTT and ASS. Free, no key, no signup.
https://www.dramasub.asia/mcp Protocol version: 2026-07-28 Transport: Streamable HTTP, POST only (stateless — no session) Auth: none
Every request carries the protocol version in the MCP-Protocol-Version header and the mirrored Mcp-Method header, plus the per-request _meta envelope. Unsupported versions get a UnsupportedProtocolVersionError (code -32022) listing the versions this server speaks. There is no translation tool — subtitle translation (Japanese, Korean, Chinese → English) is a paid feature on the site.
curl -X POST https://www.dramasub.asia/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2026-07-28' \
-H 'Mcp-Method: server/discover' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "server/discover",
"params": {
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28",
"io.modelcontextprotocol/clientInfo": { "name": "my-agent", "version": "1.0.0" },
"io.modelcontextprotocol/clientCapabilities": {}
}
}
}'The response lists supportedVersions, the server identity (dramasub), and its capabilities. Real MCP clients do this handshake for you — you normally only paste a URL (see setup below).
| Tool | Input | Returns |
|---|---|---|
| search_dramas | query (2–80 chars) | At most 10 drama pages: title, original title, country, language, page URL |
| get_drama | slug (e.g. "crash-landing-on-you") | Title, country, language, first air date, synopsis (≤600 chars), page URL |
| get_subtitle_guide | topic: language-pairs | subtitle-formats | converting-formats | how-translation-works | Guide title, summary (≤600 chars), page URL |
| convert_subtitle | from, to (srt | vtt | ass), content (≤100 KB) | Converted file text, cue count, character count |
Schemas are strict: unknown fields, wrong types, and over-length values return a clear tool error. Every result ends with a source line — keep the attribution when you share the data.
curl -X POST https://www.dramasub.asia/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2026-07-28' \
-H 'Mcp-Method: tools/call' \
-H 'Mcp-Name: convert_subtitle' \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28",
"io.modelcontextprotocol/clientInfo": { "name": "my-agent", "version": "1.0.0" },
"io.modelcontextprotocol/clientCapabilities": {}
},
"name": "convert_subtitle",
"arguments": {
"from": "srt",
"to": "vtt",
"content": "1\n00:00:01,000 --> 00:00:03,500\nAnyong!\n"
}
}
}'Retry-After and X-RateLimit-* headers.Results are free for personal and agent use with attribution: every tool result ends with a Source: dramasub.asia … line — keep it when you share the data. Bulk copying or resale of the data is not allowed (see the terms).
No account or key is involved, so nothing identifies you. For abuse prevention we log hashed IPs (never raw IPs) and send one mcp_call analytics event per call with the tool name, request inputs trimmed to 80 characters (search terms, slugs, topics; for conversions only the formats and file size — never the subtitle content), a response summary, and status. Inputs are logged and kept for 30 days. Subtitle content sent to convert_subtitle is never stored or logged.
Settings → Customize > Connectors → add a custom connector with the URL https://www.dramasub.asia/mcp (no key needed). Free plans are limited to one custom connector. Official docs.
Add to mcp.json (official docs):
{
"mcpServers": {
"dramasub": {
"url": "https://www.dramasub.asia/mcp"
}
}
}claude mcp add --transport http dramasub https://www.dramasub.asia/mcp
Custom MCP apps live in developer mode; as of 24 Oct 2026, full MCP support is limited to Business, Enterprise, and Edu workspaces and needs an admin to enable developer mode. Official docs.
The subtitle conversion is also available as a keyless REST endpoint — see the Subtitle Conversion API docs, or use the web converter.