Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Create, review and schedule social content from your AI agent. Approval-first.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://mcp.genfeed.ai/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http genfeed https://mcp.genfeed.ai/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"genfeed": {
"url": "https://mcp.genfeed.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"genfeed": {
"type": "http",
"url": "https://mcp.genfeed.ai/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://mcp.genfeed.ai/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 genfeed.ai 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.13-icons.1)은 16일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
The open-source content engine your agent can run. Self-host it free or use Cloud.
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.
If Genfeed is useful, [star it on GitHub](https://github.com/genfeedai/genfeed.ai) ⭐ so others can find it.
_One real generation on a self-hosted instance: prompt, generate, approve. About 20 seconds, unedited apart from trimming._
npx @genfeedai/create my-genfeed
Needs Docker Compose v2 and Node.js 24 or newer. The wizard verifies the release bundle, asks for your OpenRouter API key, then starts it. Install guide: genfeed.ai/self-hosted · docs.genfeed.ai.
[!WARNING]
Genfeed is
0.xand 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.
docker compose version), or Docker Desktop. Both npx @genfeedai/create and the release bundle below need it.>=24), only for npx @genfeedai/create.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.
One command (recommended):
npx @genfeedai/create my-genfeed
It downloads and verifies the release bundle, prompts for your OpenRouter key, then starts the stack. Checksums, auth, providers, and upgrades: self-hosting guide.
Release bundle (no Node.js): set OPENROUTER_API_KEY in .env to a real key from openrouter.ai/keys before starting. The container exits at start without it.
curl -fLO https://github.com/genfeedai/genfeed.ai/releases/latest/download/genfeed-selfhosted.tar.gz
curl -fLO https://github.com/genfeedai/genfeed.ai/releases/latest/download/genfeed-selfhosted.tar.gz.sha256 sha256sum -c genfeed-selfhosted.tar.gz.sha256 tar -xzf genfeed-selfhosted.tar.gz && cd genfeed-selfhosted-v* cp .env.example .env
docker compose --env-file .env -f compose.yml up -d
On macOS, use shasum -a 256 -c genfeed-selfhosted.tar.gz.sha256 for the checksum step. The API and WebSocket ports bind to 127.0.0.1; a remote browser needs a reverse proxy configured as described in the self-hosting guide.
| Surface | Local URL |
|---|---|
| Web UI | http://localhost:3000 |
| REST API | http://localhost:3010 |
| MCP server | http://localhost:3014 |
| WebSocket | ws://localhost:3011 (live agent replies; keep it reachable) |
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:
OPENROUTER_API_KEY in .env is a real key (the npx wizard sets it for you). Text generation and the agent need it, and the container refuses to start with an empty or placeholder value. If you change .env later, recreate with the same docker compose up -d command so the container reads the new value.http://localhost:3000/sign-up and create your account with Email & password. Sign-up is on by default (BETTER_AUTH_ENABLED=true in .env), and no email provider is needed. The new account gets its own organization and brand.Startup checks the OpenRouter key's format and rejects empty or placeholder values. A successful boot does not prove provider balance or model access. Settings → API Keys validates each provider key against the provider before saving 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:
Install Genfeed — the open-source content agent — on this machine, then connect
it to yourself over MCP.
.env as OPENROUTER_API_KEY (a real key; the container exits at start without it). Then start the stack: docker compose --env-file .env -f compose.yml up -d Wait for http://localhost:3000 to answer. Sign-up is open by default; the seed also creates one organization (slug default) and brand.Reference: https://github.com/genfeedai/genfeed.ai/blob/master/docs/self-hosting.md Docs index for agents: https://docs.genfeed.ai/llms.txt
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.
Captured from the real self-hosted app, v0.2.17, 1440×900 dark theme. The posts and the agent conversation are seeded demo content, not a live generation. Regenerate with bun run readme:capture.
_Agent: a brief in, drafts out. Both posts wait in Publishing for approval._
_Publish: scheduled, draft and published posts in one list._
_Automate: the Research to Content workflow template in the visual editor._
genfeed CLI, the REST API, or any AI agent over MCPAvailability differs by deployment mode and configured provider. Read Deployment Modes and Execution Boundaries before relying on a feature for a specific distribution.
| Mode | Who it is for | How you get it |
|---|---|---|
| SaaS | Hosted multi-tenant product | app.genfeed.ai |
| Community | Self-hosters, one organization | Checksummed GitHub release bundle (quick start above) |
| Desktop | Solo creators on their own Mac | Signed macOS artifacts from desktop-v* tags |
Organization billing ships in every image and is gated at runtime (a *.genfeed.ai host / self-host licence) — see the billing section. Managed inference infrastructure and Fleet/LoRA operations live outside this public repository.
Desktop is macOS-first. Mobile and browser/IDE extension sources live in the tree; this repository does not claim a public store listing for them.
This repository is agent-native: most of its code is written by AI agents under human direction, and the tree is laid out so an agent can be productive from a cold clone.
architecture/ADR-*.md, specs) plus build/dev skills for working _on_ the app. MEMORY.md is the index. `skills/` at the repo root is different: those are product/content skills the app _ships_.WHEN … THE SYSTEM SHALL …) so an agent can pick one up and know what "done" means. Triage rewrites weak criteria; it never bounces.shipcode:* labels are internal automation.** They are visible on issues and PRs; contributors never apply them.앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요