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):
{
"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.
javinfo-search
Search by DVD code, title, or actress. Returns a compact list of matches.
| Argument | Type | Notes |
|---|---|---|
q | string, required | Code, title, or actress name — e.g. AVSA-210. |
providers | string or array, optional | Restrict 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).
| Argument | Type | Notes |
|---|---|---|
q | string, required | Exact DVD id — e.g. AVSA-210. |
providers | string or array, optional | r18, javdb, missav, javdatabase. Defaults to all. |
includeImages | boolean, optional | Append 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.
| Provider | Gives you | Where |
|---|---|---|
r18 | Metadata (also does free-text search) | search + movie |
javdb | Download links and magnets | movie only |
missav | .m3u8 stream URLs | search + movie |
javdatabase | Description and sample images | search + movie |
Workflow
Search first, then detail — the resolve → fetch pattern:
javinfo-searchwithq: "AVSA"(or an actress name) → list of matches with their DVD ids.javinfo-moviewithq: "AVSA-210"→ full record. Pinproviders: "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.jsPrefer calling the API directly? Skip the server and hit the REST endpoints.