javinfo

MCP server

Give an AI assistant live javinfo access with @javinfo/mcp — a stdio MCP server exposing search and movie lookup as tools.

@javinfo/mcp is a Model Context Protocol server (stdio) that wraps the javinfo API. Point any MCP client — Claude Desktop, Claude Code, Cursor, VS Code — at it and the assistant can search titles and pull full records itself. Same data as the REST API, no glue code.

Setup

The server needs your jvi_ key in the JAVINFO_API_KEY environment variable. Get one from your dashboard — see Authentication.

Add it to your client's MCP config. This is the standard mcpServers shape (Claude Desktop, Cursor, VS Code, Claude Code all use it):

mcp.json
{
  "mcpServers": {
    "javinfo": {
      "command": "npx",
      "args": ["-y", "@javinfo/mcp"],
      "env": { "JAVINFO_API_KEY": "jvi_your_key_here" }
    }
  }
}

npx -y fetches and runs the latest published version — no global install. Restart the client and the javinfo-search / javinfo-movie tools appear.

The key lives in plaintext in the client config. Keep that file private — it bills per successful lookup, same as the REST API. See Rate limits & billing.

Tools

Two tools, meant to chain: search to find the exact DVD code, then fetch the full record for it.

Search by DVD code, title, or actress. Returns a compact list of matches.

ArgumentTypeNotes
qstring, requiredCode, title, or actress name — e.g. AVSA-210.
providersstring or array, optionalRestrict sources. r18, missav, javdatabase. Defaults to all.

javdb is not available here (it's code-only) — use javinfo-movie for download links.

javinfo-movie

Fetch one full record by its exact DVD id (the one you got from search).

ArgumentTypeNotes
qstring, requiredExact DVD id — e.g. AVSA-210.
providersstring or array, optionalr18, javdb, missav, javdatabase. Defaults to all.
includeImagesboolean, optionalAppend jacket, sample, and gallery URLs. Default false.

Image URLs are omitted by default to keep responses token-lean — set includeImages: true when you actually need them. Every result also carries the raw record as structuredContent for clients that read structured tool output.

Providers

providers pins where the data comes from. Omit it to race all of them and take the first hit.

ProviderGives youWhere
r18Metadata (also does free-text search)search + movie
javdbDownload links and magnetsmovie only
missav.m3u8 stream URLssearch + movie
javdatabaseDescription and sample imagessearch + movie

Workflow

Search first, then detail — the resolve → fetch pattern:

  1. javinfo-search with q: "AVSA" (or an actress name) → list of matches with their DVD ids.
  2. javinfo-movie with q: "AVSA-210" → full record. Pin providers: "javdb" for magnets, "missav" for streams.

Local development

Run the server from source against the MCP Inspector:

npm install
npm run build
JAVINFO_API_KEY=jvi_your_key_here npx @modelcontextprotocol/inspector node dist/index.js

Prefer calling the API directly? Skip the server and hit the REST endpoints.

On this page