genfeedai/genfeed.ai

**The open-source content agent.**
Create on-brand videos, images and posts, then review and publish to your
connected channels. Work in Genfeed or connect the AI agent you already use.
> [!WARNING]
> Genfeed is 0.x and under active development. Breaking changes ship with an
> **Upgrade note** in the release body; semver becomes strict at v1.0.0.
Self-host it (**Community**), run it on your Mac (**Desktop**), or use the
hosted product at genfeed.ai (**SaaS**). Same code, three
deployment modes.
Requirements (Community)
- Docker Engine with the Docker Compose v2 plugin (docker compose version), or
Docker Desktop. Both the 3-command block below and npx @genfeedai/create
need it.
- Node.js 24 (>=24 <25), only for npx @genfeedai/create.
- Free host ports 3000 (web), 3010 (API) and 3014 (MCP).
- About 10 GB of free disk (15 GB recommended); a fresh install measured about 9.5 GB.
- RAM: no minimum is published. Tested on 8 CPU / 15 GiB.
- Debian 13 provides Compose v2 in its
docker-compose package.
With Docker CE, install docker-compose-plugin from
Docker's apt repository.
See troubleshooting if the app logs
P1001: Can't reach database server at postgres:5432.
Quick start (Community)
| Surface | Local URL |
| ---------- | ----------------------- |
| Web UI | http://localhost:3000 |
| REST API | http://localhost:3010 |
| MCP server | http://localhost:3014 |
The bundle pins the image for its release, applies Prisma migrations, and seeds
one local workspace. No Genfeed Cloud account is required.
For a first generation, do these in order:
1. Set OPENROUTER_API_KEY in .env to a real key from
openrouter.ai/keys. Text generation and the
agent need it. Without it the install-readiness check reports text
generation as not ready. Then restart with the same docker compose up -d
command so the container reads the new value.
2. Open http://localhost:3000 and create your account. Sign-up is on by
default (BETTER_AUTH_ENABLED=true in .env), so the first visitor can
register. No email provider is needed for email/password.
3. Complete onboarding, then start a task or generation.
Keys are checked for real. **Settings → API Keys** validates each provider key
against the provider before saving, so placeholder text is rejected there.
Keys in .env are never accepted as placeholders either: an empty or
template value counts as not configured.
npx @genfeedai/create my-genfeed downloads, checksums, and starts the same
bundle. Checksums, auth, providers, and upgrades:
self-hosting guide.
Let your coding agent install it
Genfeed is driven by agents, so installing it is a task you can hand to one.
Paste this into Claude Code, Codex, Cursor, or any agent with shell access:
Already on the hosted product? Skip installation and authorize with browser OAuth.
Claude uses https://mcp.genfeed.ai/mcp/claude for brands, drafts, existing assets, scheduling and analytics; create media in Genfeed Playground. Other clients use https://mcp.genfeed.ai/mcp for the full toolset.
The standard MCP preset is approval-first: an agent can generate, draft, and schedule, but
publishing waits for a human. What each surface exposes and why is in
Agent Surface.
*Mocked Playwright capture of the agent conversation shell. Fixture data, not a live generation.*
*Mocked Playwright capture of the Publish desk.*
*Mocked Playwright capture of Automate workflow authoring.*
Capabilities
- Generate images, video, text, voice, and audio with local or bring-your-own-key
execution
- Visual workflow authoring; content library, brand, scheduling, and publishing
- Drive the same loop from the web app, the genfeed CLI, the
REST API, or any AI agent over MCP
- PostgreSQL via Prisma; Redis/BullMQ background work
- A Community Docker distribution built from the same AGPL source as the hosted