Skip to main content
Copy .env.example to .env before starting the server. CinePro Core requires a valid TMDB_API_KEY to resolve metadata and start correctly.

Required vs optional

Required

  • TMDB_API_KEY — required for metadata lookups and startup

Optional

  • PORT, HOST, PUBLIC_URL, NODE_ENV — server runtime settings
  • CACHE_TYPE, REDIS_* — only needed for Redis-backed caching
  • STREMIO_ADDON, MCP_ENABLED, CORS_ORIGIN, TMDB_CACHE_TTL — optional integrations and tuning

Server configuration

number
default:"3000"
The port CinePro Core listens on.
.env
.env
string
default:"localhost"
The hostname or IP address the server binds to.Use localhost during development to keep the API limited to your machine.
Use 0.0.0.0 in Docker or production if the API should be reachable from other devices.
.env
.env
string
The public base URL of your CinePro Core instance. Use this when your server is exposed through a public hostname, reverse proxy, or domain.
.env
Include the protocol and do not add a trailing slash. A wrong PUBLIC_URL can produce broken absolute URLs in responses.
string
default:"development"
Controls the runtime mode.
.env
.env
string
Optional. Restricts which browser origins may call the CinePro API.Leave unset to keep the default behavior, or set it to a specific origin if you expose the API publicly.
.env

Optional integrations

boolean
default:"false"
Enables CinePro’s Stremio addon support.When enabled, CinePro exposes a Stremio manifest endpoint at /stremio/manifest.json so your instance can be added as a Stremio source.
.env

Adding custom Stremio addons as sources

CinePro Core can also pull streams from existing Stremio addons and surface them as additional sources. This list is configured in src/server.ts rather than via an environment variable.As of the May 7, 2026 release, the default stremioAddons array is empty — you must explicitly add the addons you want to use:
src/server.ts
Earlier versions of CinePro Core shipped two community addons (WebStreamerMBG and Streamify) pre-wired in this list. They have been removed so you can curate your own list from a clean slate.
boolean
default:"false"
Returns every source the providers find — including non-playable ones — and attaches detailed per-provider diagnostics to the response. Use this when developing or debugging providers; leave it off in normal use.
.env
Keep INTERNAL_DEBUG=false for regular usage. With it enabled, the API surfaces broken or unplayable sources alongside working ones, which clients are not expected to filter.
boolean
default:"false"
Enables Model Context Protocol support for MCP-compatible clients and AI agents.
.env
Enable this only if you actually plan to connect CinePro to MCP clients. Regular API users do not need it.

TMDB configuration

string
required
Your TMDB (The Movie Database) API key. CinePro Core uses TMDB for metadata such as titles, IDs, and artwork.
1

Create a TMDB account

Sign up at themoviedb.org.
2

Request an API key

Open Settings → API in TMDB and request a developer key.
3

Add the key to your .env

.env
Keep this key private and never commit your .env file to version control.
number
default:"86400"
Defines how long TMDB metadata responses are cached, in seconds.The default 86400 equals 24 hours.
.env

Cache configuration

string
default:"memory"
Selects the cache backend used by CinePro Core.
.env
.env
If you use redis, configure the Redis connection variables below as well.

Redis configuration

These variables are only needed when CACHE_TYPE=redis.
string
default:"localhost"
Hostname or IP address of your Redis server.
.env
.env
number
default:"6379"
Port of your Redis instance.
.env
string
Optional password for Redis authentication.
.env
.env
Never commit Redis credentials to source control. Use environment injection or a secrets manager in production.

Full .env examples

Development

.env

Production

.env

Docker Compose

.env
In Docker Compose, REDIS_HOST should usually be the Redis service name from compose.yml, not localhost.