A Model Context Protocol (MCP) server for Amazon Nova Reel 1.1 video generation using AWS Bedrock. This server provides tools for asynchronous video
Connect Novareel MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for Amazon Nova Reel 1.1 video generation using AWS Bedrock. This server provides tools for asynchronous video generation with comprehensive prompting guidelines and both stdio and SSE transport. The novareel mcp mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Prerequisites — The Prerequisites tool exposed by this serverContributing — 1. Fork the repository 2. Create a feature branch 3. Make your changes 4. Test with all transport versions (stdio, SSE, HTTP streaming) 5. Submit aConfiguration is passed through the environment: PYTHONUNBUFFERED, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, YOUR_AWS_ACCESS_KEY_ID, YOUR_AWS_SECRET_ACCESS_KEY, YOUR_KEY, YOUR_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on PyPI as build, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Novareel MCP's toolset — Prerequisites, Contributing — is a fair guide to whether it matches your workflow. It is maintained by mirecekd; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| Contributing | 1. Fork the repository 2. Create a feature branch 3. Make your changes 4. Test with all transport versions (stdio, SSE, HTTP streaming) 5. Submit a pull request |
{
"mcpServers": {
"novareel": {
"command": "uvx",
"args": ["build"],
"env": {
"PYTHONUNBUFFERED": "your-value",
"AWS_ACCESS_KEY_ID": "your-value",
"AWS_SECRET_ACCESS_KEY": "your-value",
"YOUR_AWS_ACCESS_KEY_ID": "your-value",
"YOUR_AWS_SECRET_ACCESS_KEY": "your-value",
"YOUR_KEY": "your-value",
"YOUR_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PYTHONUNBUFFERED | Configuration value read at startup. | Optional |
| AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_AWS_ACCESS_KEY_ID | Credential the server authenticates with. | Yes |
| YOUR_AWS_SECRET_ACCESS_KEY | Credential the server authenticates with. | Yes |
| YOUR_KEY | Credential the server authenticates with. | Yes |
| YOUR_SECRET | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.