Installation
The MCP server is included in thenode-csfd-api package. No separate installation is required.
Prerequisites
- Node.js 18 or higher
- npm, yarn, or pnpm package manager
- An MCP-compatible client (e.g., Claude Desktop)
Option 1: NPX (Recommended)
No installation needed - use npx to run the server directly:Option 2: Global Installation
Install the package globally:Option 3: Homebrew (macOS/Linux)
For macOS and Linux users:Running the MCP Server
Configure your MCP client
Add the configuration to your MCP client. For Claude Desktop, see the Claude Desktop Integration guide.
Configuration
The MCP server runs via stdio transport and doesn’t require additional configuration. It automatically:- Initializes with package name and version
- Registers all available tools
- Handles requests/responses via standard input/output
Server Information
The server exposes:- Name:
node-csfd-api - Version: Auto-detected from package.json
- Transport: Stdio (Standard Input/Output)
- Tools: 6 tools (search, get_movie, get_creator, get_user_ratings, get_user_reviews, get_cinemas)
- Prompts: 1 prompt (actor-top-rated)
Testing the Server
Manual Testing
You can test the server directly from the command line:Testing with an MCP Client
The easiest way to test is through an MCP-compatible client like Claude Desktop:- Configure the client (see Claude Desktop Integration)
- Ask the AI to search for a movie:
- The AI should use the
searchtool and return results
Common Test Queries
Troubleshooting
Server Won’t Start
Problem: Server fails to start or crashes immediately Solutions:- Ensure Node.js 18+ is installed:
node --version - Try clearing npm cache:
npm cache clean --force - Use the npx command with
-yflag:npx -y node-csfd-api mcp
Client Can’t Connect
Problem: MCP client doesn’t recognize the server Solutions:- Verify the configuration file path is correct
- Check that JSON syntax in config is valid
- Restart the MCP client after configuration changes
- Check client logs for error messages
Tools Not Working
Problem: Tools are registered but return errors Solutions:- Check your internet connection (server scrapes live ČSFD data)
- ČSFD might be temporarily unavailable - try again later
- Some IDs might not exist - verify IDs using the search tool first
Rate Limiting Issues
Problem: Getting blocked or slow responses Solutions:- Use
allPagesDelayparameter when fetching multiple pages - Recommended delay: 2000ms (2 seconds) between requests
- Avoid using
allPages: truefor large datasets - Consider caching results on your client side
stdio Transport Errors
Problem: “Transport error” or “broken pipe” messages Solutions:- Ensure no other process is using the same stdio stream
- Don’t run the server interactively - let the MCP client manage it
- Check that the command path in client config is correct
The MCP server communicates via stdio (standard input/output), so it should be launched by your MCP client, not run directly in an interactive terminal.
Advanced Configuration
Development Mode
For developers working on the MCP server:Using with Docker
While the MCP server is designed for stdio transport, you can also run the REST API server via Docker and access the same data:Security Considerations
Privacy
- The server does not collect or store any data
- All requests go directly to ČSFD.cz
- No intermediary servers or logging
- No telemetry or analytics
Next Steps
Claude Desktop Integration
Set up the MCP server with Claude Desktop
Available Tools
Explore all available MCP tools
API Reference
View the full API documentation
GitHub Repository
View source code and contribute