A production-ready **Model Context Protocol (MCP) server** for intelligent movie database management, built with Clean Architecture principles and
Movies MCP server exists for a simple reason — assistants are far more useful when they can act on Movies directly instead of describing what you should do. A production-ready Model Context Protocol (MCP) server for intelligent movie database management, built with Clean Architecture principles and optimized for.
Movies MCP Server is a sophisticated movie database management system that communicates via the Model Context Protocol—designed specifically for integration with AI assistants like Claude. Unlike traditional HTTP APIs, it uses JSON-RPC over stdin/stdout to provide seamless, intelligent movie and actor data operations.
Once Movies is connected, these are the calls the assistant has available:
get_movie — Retrieve movie by IDadd_movie — Create movie with title, director, year, rating, genres, posterupdate_movie — Update existing movie detailsdelete_movie — Delete movie by IDlist_top_movies — Get top-rated movies with configurable limitsearch_movies — Multi-criteria search (title, director, genre, year range, rating)search_by_decade — Find movies from specific decades (1990s, 2000s, etc.)search_by_rating_range — Filter movies by rating boundariesadd_actor — Create actor with name, birth year, biographyget_actor — Retrieve actor by IDupdate_actor — Update actor informationdelete_actor — Delete actorYou will need 7 environment variables: DB_HOST, DB_PORT, DB_USER, DB_PASSWORD, DB_NAME, DB_SSLMODE, DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Movies's toolset — get_movie, add_movie, update_movie and 11 more — is a fair guide to whether it matches your workflow. It is maintained by francknouama; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_movie | Retrieve movie by ID |
| add_movie | Create movie with title, director, year, rating, genres, poster |
| update_movie | Update existing movie details |
| delete_movie | Delete movie by ID |
| list_top_movies | Get top-rated movies with configurable limit |
| search_movies | Multi-criteria search (title, director, genre, year range, rating) |
| search_by_decade | Find movies from specific decades (1990s, 2000s, etc.) |
| search_by_rating_range | Filter movies by rating boundaries |
| add_actor | Create actor with name, birth year, biography |
| get_actor | Retrieve actor by ID |
| update_actor | Update actor information |
| delete_actor | Delete actor |
| link_actor_to_movie | Associate actor with movie |
| unlink_actor_from_movie | Remove actor-movie association |
{
"mcpServers": {
"movies": {
"command": "/absolute/path/to/movies-mcp-server-sdk",
"args": [],
"env": {
"DB_HOST": "localhost",
"DB_PORT": "5432",
"DB_USER": "movies_user",
"DB_PASSWORD": "movies_password",
"DB_NAME": "movies_mcp",
"DB_SSLMODE": "disable"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DB_HOST | Endpoint or connection string the server talks to. | Optional |
| DB_PORT | Configuration value read at startup. | Optional |
| DB_USER | Configuration value read at startup. | Optional |
| DB_PASSWORD | Configuration value read at startup. | Optional |
| DB_NAME | Configuration value read at startup. | Optional |
| DB_SSLMODE | Configuration value read at startup. | Optional |
| DATABASE_URL | Endpoint or connection string the server talks to. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.