IMDB146

What is IMDB146?

IMDB146 is an MCP server that provides access to the IMDB146 API. It runs on the stdio transport protocol and is available as a Python package (bach-imdb146). The server is intended for developers and AI assistants that need to query IMDB data through the Model Context Protocol.

How to use IMDB146?

Install via pip (pip install bach-imdb146) or run with uvx --from bach-imdb146 bach_imdb146 (recommended). Set the API_KEY environment variable with your IMDB146 API key. Configuration files for Cursor (~/.cursor/mcp.json) and Claude Desktop (claude_desktop_config.json) are provided. The server can also be used through the EMCP platform for zero‑configuration management.

Key features of IMDB146

• Offers tools for name details, title details, search, news, and video data
• Runs via uvx with automatic dependency resolution
• Integrates with Cursor, Claude Desktop, and the EMCP platform
• MIT licensed – open source
• Developed from the API-to-MCP tool

Use cases of IMDB146

• Query IMDB title details by ID
• Retrieve name/actor information from IMDB
• Search IMDB for movies, shows, or people
• Fetch latest IMDB news articles
• Get video metadata from IMDB

FAQ from IMDB146

What does IMDB146 do?

IMDB146 is an MCP server that exposes IMDB146 API endpoints as tools (name details, title details, find, news details, video details) for use by MCP‑compatible clients like Cursor and Claude Desktop.

Which platforms or editors support IMDB146?

IMDB146 works with any MCP client. Explicit configuration examples are provided for Cursor and Claude Desktop. It can also be managed through the EMCP platform.

Does IMDB146 require an API key?

Yes. The API_KEY environment variable must be set to authenticate requests to the IMDB146 API. No default key is provided.

What is the licensing of IMDB146?

IMDB146 is released under the MIT License, as stated in the included LICENSE file.

Are there any known limits or restrictions?

The README does not specify rate limits or pricing. The server requires an API key, implying the underlying IMDB146 API may have its own access restrictions.