imdb-mcp-server
An MCP (Model Context Protocol) server exposing IMDb movie data (via the OMDb API) as tools an LLM can call.
Built as a learning project: two layers, deliberately separated.
Claude Code (MCP client)
│ stdio (JSON-RPC)
▼
server.py ← MCP layer: FastMCP server, 7 tools, formats results for an LLM
omdb.py ← data layer: async httpx client for OMDb (knows nothing of MCP)
store.py ← persistence: SQLite movie memory (knows nothing of MCP or OMDb)
movies.db ← your personal taste data, local only (gitignored)
Tools
IMDb data (via OMDb):
| Tool | Input | Returns |
|---|---|---|
search_movies |
query, optional year, type |
Matches with title, year, IMDb ID |
get_movie_details |
imdb_id |
Plot, director, cast, genre, ratings |
get_movie_ratings |
imdb_id |
IMDb / Rotten Tomatoes / Metacritic scores |
Personal memory (local SQLite):
| Tool | What it does |
|---|---|
log_movie |
Record watched/watchlist + liked/disliked + optional 1–10 rating |
get_my_movies |
List history or watchlist |
get_taste_profile |
Genre preferences, likes/dislikes, avg rating — feeds recommendations |
remove_movie |
Delete an entry |
Recommendations work as a collaboration: the LLM reads your taste profile,
generates candidates from its own movie knowledge, then verifies each with
get_movie_details before suggesting.
Quick start
- Get a free API key at https://www.omdbapi.com/apikey.aspx (activate via the email link).
- Add to your MCP client config (e.g.
.mcp.jsonfor Claude Code, orclaude_desktop_config.jsonfor Claude Desktop):
{
"mcpServers": {
"imdb": {
"command": "uvx",
"args": ["imdb-mcp-server"],
"env": { "OMDB_API_KEY": "your-key-here" }
}
}
}
No uv? Use pip install imdb-mcp-server and set "command": "imdb-mcp-server".
Your movie memory is stored at ~/.imdb-mcp-server/movies.db (override with
the IMDB_MCP_DB env var).
Development
python -m venv .venv
.venv/Scripts/pip install -e .
Debug with the MCP Inspector:
npx @modelcontextprotocol/inspector -e OMDB_API_KEY=<key> -- .venv/Scripts/python.exe -m imdb_mcp_server.server
Metadata
Release files for imdb-mcp-server 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| imdb_mcp_server-0.1.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imdb_mcp_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.8 kB
Release files / imdb_mcp_server-0.1.0.tar.gz
| Download URL | imdb_mcp_server-0.1.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7f5bd6f255cfafdead7ffcce60879474e901410036cf1d133a75630b4ed8c19
|
|
BLAKE2b-256 checksum How to use checksums |
0405617a5ccb32052131cf1ddbe265cd870c6d7ccc977dd2b0f41a152d0184fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Release files / imdb_mcp_server-0.1.0-py3-none-any.whl
| Download URL | imdb_mcp_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ce194d48771a25759ef8e7d848d5a3d5d8e559e0c8d6e9f9efa6dfa6c20098a
|
|
BLAKE2b-256 checksum How to use checksums |
a14b730e9c7dff0a136aae66bb02b812fdfa42377d8edc0f2cfa942a4673003a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.14
|
Security for imdb-mcp-server 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.