Which integrations are available for this server?

Allows searching and retrieving movie, series, and episode data using the OMDb API, which provides information from the IMDb database.

How do I use omdb-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@omdb-mcp search for movies about time travel" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

omdb-mcp

by Dworf

Overview Schema Source Related Servers Score Discussions Admin

Python

Remote

omdb-mcp

An MCP (Model Context Protocol) server for the OMDb API — search movies, series, and episodes from any MCP-compatible client.

Built with FastMCP. Supports both STDIO and Streamable HTTP transports, with optional bearer-token auth for HTTP mode.

Features

Five tools: search_movies, get_by_title, get_by_imdb_id, get_episode, get_season
Dual transport: STDIO (for MetaMCP / Claude Desktop / Hermes) and Streamable HTTP (for standalone agents)
Optional bearer-token authentication for HTTP mode
Configuration via .env or environment variables
Minimal dependencies: fastmcp, httpx, python-dotenv

Related MCP server: moviefinder-mcp

Install

# Recommended: run directly with uvx (no install needed)
uvx omdb-mcp

# Or install into your environment
pip install omdb-mcp

Get a free OMDb API key at https://www.omdbapi.com/apikey.aspx (1,000 requests/day on the free tier).

Configuration

All settings come from environment variables (a .env file in the working directory is auto-loaded).

Variable	Default	Description
`OMDB_API_KEY`	(required)	Your OMDb API key
`OMDB_MCP_TRANSPORT`	`stdio`	`stdio` or `http`
`OMDB_MCP_HOST`	`127.0.0.1`	HTTP bind address (`0.0.0.0` for LAN/Docker)
`OMDB_MCP_PORT`	`8087`	HTTP port
`OMDB_MCP_PATH`	`/mcp`	HTTP mount path
`OMDB_MCP_AUTH_TOKEN`	(unset)	If set, HTTP clients must send `Authorization: Bearer ...`
`OMDB_MCP_LOG_LEVEL`	`INFO`	`DEBUG`, `INFO`, `WARNING`, `ERROR`
`OMDB_REQUEST_TIMEOUT`	`10`	OMDb HTTP timeout (seconds)
`OMDB_BASE_URL`	`https://www.omdbapi.com/`	Override only if proxying/mirroring OMDb

See .env.example for a copy-paste template.

Running

STDIO mode (for MCP clients that spawn the process)

omdb-mcp
# or with uv:
uvx omdb-mcp

Streamable HTTP mode (for standalone, long-lived service)

omdb-mcp-http
# or override port/host:
omdb-mcp-http --port 8087 --host 0.0.0.0

CLI flags --transport, --host, --port, --path override env vars.

Client setup

MetaMCP

Option A — STDIO (simplest, no service to manage):

Type: STDIO
Command: uvx
Args: omdb-mcp
Env: OMDB_API_KEY=your_key_here

Option B — Streamable HTTP (standalone service):

Run the server on the host:

OMDB_API_KEY=your_key OMDB_MCP_AUTH_TOKEN=mysecret omdb-mcp-http

In MetaMCP:

Type: Streamable HTTP
URL: http://host.docker.internal:8087/mcp
Header: Authorization: Bearer mysecret (if OMDB_MCP_AUTH_TOKEN is set)

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "omdb": {
      "command": "uvx",
      "args": ["omdb-mcp"],
      "env": {
        "OMDB_API_KEY": "your_key_here"
      }
    }
  }
}

Cursor / Windsurf / Cline

Same JSON shape, different config path. Cursor reads ~/.cursor/mcp.json:

{
  "mcpServers": {
    "omdb": {
      "command": "uvx",
      "args": ["omdb-mcp"],
      "env": { "OMDB_API_KEY": "your_key_here" }
    }
  }
}

Generic Streamable HTTP client

{
  "mcpServers": {
    "omdb": {
      "url": "http://127.0.0.1:8087/mcp",
      "headers": {
        "Authorization": "Bearer your_token_here"
      }
    }
  }
}

Tools

Tool	OMDb param(s)	Description
`search_movies`	`s`, `y`, `type`, `page`	Free-text search (paginated, 10 per page)
`get_by_title`	`t`, `y`, `type`, `plot`	Lookup by exact title
`get_by_imdb_id`	`i`, `plot`	Lookup by IMDb ID (`tt...`)
`get_episode`	`i`/`t`, `Season`, `Episode`, `plot`	Single TV episode
`get_season`	`i`/`t`, `Season`	All episodes in a season

Running as a service (HTTP mode)

macOS — launchd

Create ~/Library/LaunchAgents/com.dworf.omdb-mcp.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key><string>com.dworf.omdb-mcp</string>
    <key>ProgramArguments</key>
    <array>
        <string>/Users/YOU/.local/bin/uvx</string>
        <string>omdb-mcp-http</string>
    </array>
    <key>EnvironmentVariables</key>
    <dict>
        <key>OMDB_API_KEY</key><string>your_key_here</string>
        <key>OMDB_MCP_AUTH_TOKEN</key><string>your_token_here</string>
        <key>OMDB_MCP_HOST</key><string>127.0.0.1</string>
        <key>OMDB_MCP_PORT</key><string>8087</string>
    </dict>
    <key>RunAtLoad</key><true/>
    <key>KeepAlive</key><true/>
    <key>StandardOutPath</key><string>/tmp/omdb-mcp.log</string>
    <key>StandardErrorPath</key><string>/tmp/omdb-mcp.err</string>
</dict>
</plist>

Load it:

launchctl load ~/Library/LaunchAgents/com.dworf.omdb-mcp.plist
# stop / unload:
launchctl unload ~/Library/LaunchAgents/com.dworf.omdb-mcp.plist

Linux — systemd

Create ~/.config/systemd/user/omdb-mcp.service:

[Unit]
Description=OMDb MCP server (Streamable HTTP)
After=network.target

[Service]
ExecStart=%h/.local/bin/uvx omdb-mcp-http
Environment=OMDB_API_KEY=your_key_here
Environment=OMDB_MCP_AUTH_TOKEN=your_token_here
Environment=OMDB_MCP_HOST=127.0.0.1
Environment=OMDB_MCP_PORT=8087
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target

systemctl --user daemon-reload
systemctl --user enable --now omdb-mcp
systemctl --user status omdb-mcp
journalctl --user -u omdb-mcp -f

Docker

FROM python:3.12-slim
RUN pip install --no-cache-dir omdb-mcp
EXPOSE 8087
ENV OMDB_MCP_HOST=0.0.0.0 OMDB_MCP_PORT=8087
CMD ["omdb-mcp-http"]

docker build -t omdb-mcp .
docker run -d --name omdb-mcp -p 8087:8087 \
  -e OMDB_API_KEY=your_key \
  -e OMDB_MCP_AUTH_TOKEN=your_token \
  --restart unless-stopped omdb-mcp

Development

git clone https://github.com/Dworf/omdb-mcp
cd omdb-mcp
uv venv && source .venv/bin/activate
uv pip install -e ".[dev]"
pytest

Security note

If you bind to 0.0.0.0 without setting OMDB_MCP_AUTH_TOKEN, anyone on the network can use your OMDb API key. The server logs a warning at startup in that case — set a token in any non-localhost deployment.

Changelog

v0.1.0 — 2026-05-14

Initial release.
Five tools: search_movies, get_by_title, get_by_imdb_id, get_episode, get_season.
Dual transport: STDIO (default) and Streamable HTTP.
Optional bearer-token auth for HTTP mode.
.env loading via python-dotenv.
20 unit tests; smoke-tested against the live OMDb API.

Acknowledgements

OMDb API — Brian Fritz's free movie/series database. If you use this MCP server in production, please consider donating to OMDb or upgrading to a Patreon-tier key.
FastMCP — the Python MCP framework this server is built on.
Model Context Protocol — the open protocol that makes this possible.

License

MIT

Available Tools

5 tools

get_by_imdb_idA

Look up a title by its IMDb ID (e.g. "tt0111161"). OMDb i parameter.

ParametersJSON Schema

Name	Required	Description	Default
`imdb_id`	Yes	IMDb ID, including the "tt" prefix.
`plot`	No	"short" (default) or "full".	short

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the burden. It only says 'look up' without disclosing read-only nature, auth requirements, or API limitations. Minimal behavioral disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, front-loaded with the core purpose. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 params, output schema exists), the description is adequate but minimal. It could mention that it returns details for a single title, but the output schema covers that.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds an example for imdb_id but does not add meaning beyond the schema. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: look up a title by IMDb ID, with an example provided. It distinguishes implicitly from siblings which use different identifiers (title, episode, season, search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have an IMDb ID, but does not explicitly state when to use this tool versus alternatives (e.g., get_by_title). No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_by_titleA

Look up a single title by exact name (OMDb t parameter).

ParametersJSON Schema

Name	Required	Description	Default
`title`	Yes	Exact title to look up.
`year`	No	Optional release year disambiguator.
`type`	No	Optional filter: "movie", "series", or "episode".
`plot`	No	"short" (default) or "full".	short

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions the OMDb `t` parameter but does not disclose behavior like rate limits, what happens if the title is not found, or authentication needs. It is adequate but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is front-loaded with the main action. Every word earns its place, making it highly concise and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to explain return values. It covers the main purpose and parameter usage adequately. The sibling tools are clear, and the tool is simple, so completeness is good.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The tool description adds no extra meaning beyond what the schema provides, justifying the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Look up a single title by exact name', specifying the verb (look up), resource (single title), and method (exact name). It distinguishes from siblings like 'get_by_imdb_id' (different lookup method) and 'search_movies' (broad search).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when you have the exact title. Although it does not explicitly state exclusions or alternatives, the sibling list provides context (e.g., use 'get_by_imdb_id' for IMDB ID). The description could be more explicit but is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_episodeA

Look up a specific TV episode.

Provide either imdb_id (preferred) or title to identify the series, plus season and episode numbers.

ParametersJSON Schema

Name	Required	Description	Default
`season`	Yes	Season number (1-indexed).
`episode`	Yes	Episode number within the season.
`imdb_id`	No	IMDb ID of the series (preferred).
`title`	No	Series title (used if imdb_id is not provided).
`plot`	No	"short" (default) or "full".	short

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. Description implies a read operation but does not confirm safety, auth needs, or other behavioral traits. For a lookup tool, minimal disclosure, but full burden on description is partially met.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no waste. First sentence states purpose, second provides key usage guidance. Well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, return values need not be explained. However, description lacks guidance on the optional plot parameter and the case when both imdb_id and title are omitted (schema allows this, but description seemingly requires one). Adequate but with notable gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters. Description adds value by grouping imdb_id and title as alternative identifiers with preference for imdb_id, and clarifies they are used together with season/episode. Slight conflict: schema marks imdb_id and title as optional (default null), but description implies one must be provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool looks up a specific TV episode. It distinguishes from siblings like get_season (whole season) and search_movies (search) by specifying exact episode retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It instructs to provide either imdb_id (preferred) or title plus season and episode, giving clear context. However, it does not explicitly exclude cases for siblings like get_by_imdb_id or get_by_title, though the episode focus differentiates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_seasonA

List all episodes in a given season of a series.

Provide either imdb_id (preferred) or title.

ParametersJSON Schema

Name	Required	Description
`season`	Yes	Season number (1-indexed).
`imdb_id`	No	IMDb ID of the series (preferred).
`title`	No	Series title (used if imdb_id is not provided).

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility for behavioral cues. It discloses the primary action (listing episodes) and preference for 'imdb_id', but fails to specify behavior when neither 'imdb_id' nor 'title' is provided (both are optional in schema), or potential side effects like rate limiting or authentication requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at two sentences, front-loading the core purpose. Every word is purposeful with no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and the output schema exists (confirmed by context signals), so return details are covered. The description specifies the input requirements and preference. It doesn't mention pagination or error handling, but for a basic listing tool, this seems adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, with clear descriptions for each parameter. The description adds that 'imdb_id' is preferred and season is 1-indexed, but these are already in the schema. No additional semantic value beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists all episodes in a given season of a series, with a specific verb ('list') and resource ('episodes in a given season'). It also mentions using either 'imdb_id' or 'title', distinguishing it from sibling tools like 'get_by_imdb_id' and 'get_by_title', which search for series metadata.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides usage guidance by stating 'Provide either `imdb_id` (preferred) or `title`', indicating when to use each parameter. However, it does not explicitly exclude this tool over alternatives like 'get_episode' for individual episodes, or mention prerequisites, but the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_moviesA

Search OMDb for movies/series/episodes by free-text title.

ParametersJSON Schema

Name	Required	Description
`query`	Yes	Search text (OMDb's `s` parameter). Required.
`year`	No	Optional release year filter.
`type`	No	Optional filter: "movie", "series", or "episode".
`page`	No	Page number (10 results per page).

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It only states the purpose and omits behavioral traits such as pagination, rate limits, authentication, or data freshness. The parameter 'page' suggests pagination but is not elaborated in the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, well-structured sentence that front-loads the core purpose. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 4 parameters, the description is minimal. It provides the essential purpose but lacks details on result format, pagination, or filtering capabilities beyond what the schema already conveys.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions; it merely repeats the free-text nature.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search'), the resource ('OMDb'), and the kinds of items ('movies/series/episodes'), and the method ('by free-text title'). This distinguishes it from sibling tools that fetch by exact IMDB ID or exact title.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for free-text search versus exact match siblings, but it does not explicitly state when to prefer this tool over alternatives like get_by_imdb_id or get_by_title. No when-not or prerequisite information is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

5 tool updatesv0.1.0May 29, 2026
- First observedget_by_imdb_id
- First observedget_by_title
- First observedget_episode
- First observedget_season
- First observedsearch_movies

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored 2026-05-29 14:45 across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: lookup by IMDb ID, by title, episode details, season listing, and free-text search. There is no overlap in functionality, and the descriptions clearly differentiate the use cases.

Naming Consistency4/5

Most tools follow a 'get_X' pattern, but 'search_movies' uses 'search' instead of 'get', and 'get_by_imdb_id' and 'get_by_title' use 'get_by' rather than 'get'. This minor inconsistency does not hinder readability.

Tool Count5/5

With 5 tools, the server covers the core OMDb operations—title lookup, ID lookup, season and episode retrieval, and text search—without unnecessary bloat. The count is well-scoped for a movie database API.

Completeness4/5

The tool surface covers the primary OMDb functionality (search, details by ID/title, season/episode). Missing are explicit tools for ratings or poster retrieval, but these are likely included in the results of existing tools, so gaps are minor.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Omdb A
io.github.pipeworx-io
OMDb MCP — IMDB-derived movie / TV / episode data (BYO key)
Entertainment & Media Search
342
Tv Maze Mcp
io.github.varvararatta
Unlock a world of television with the TV Maze MCP server. Effortlessly search for shows by name or
Search Entertainment & Media
2
Star Wars MCP A
build.swapi
Star Wars API (SWAPI) as a remote MCP server: films, people, planets, species, starships, vehicles.
Entertainment & Media Open Data
13
Imdb
io.github.pipeworx-io
IMDB MCP — title metadata, ratings, episodes, and crew from IMDB's
Entertainment & Media Search
2

Related MCP Servers

Movie Search MCP Server
tonderflash
A
license
D
quality
D
maintenance
An MCP server that allows users to search for movies, get detailed information, receive genre-based recommendations, and discover popular/trending films using OMDb and TMDb APIs.
Updated a year ago (2025-07-20 23:12 UTC)
5
13
MIT
moviefinder-mcp
Entertainment & Media Search
AmeliaMiddleton
F
license
A
quality
D
maintenance
An MCP server that wraps The Movie Database (TMDB) API, enabling search for movies and TV shows, retrieval of movie details, recommendations, similar movies, trending content, streaming providers, and movie discovery.
Updated 4 months ago (2026-05-05 01:50 UTC)
8
-
moviefinder-mcp
Entertainment & Media Search
AmeliaMiddleton
F
license
A
quality
D
maintenance
An MCP server that wraps the TMDB API, enabling search of movies and TV shows, retrieval of details, trending titles, recommendations, and streaming provider information.
Updated 4 months ago (2026-05-05 01:25 UTC)
8
-
TMDB MCP Server
Entertainment & Media Search
Amruth2507
F
license
Not graded
quality
D
maintenance
A robust MCP server that wraps The Movie Database API, enabling LLMs to search movies, get details, popular movies, and recommendations.
Updated 5 months ago (2026-04-06 17:28 UTC)
-

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dworf/omdb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server