genfeed

Installation
SKILL.md

Genfeed

The MCP server is hosted. This skill is the playbook. Tool names, arguments, and approval flags are in references/tools.md. Do not invent a tool.

Hard rules

  1. Authenticate first. If a call returns 401, stop. Do not search the filesystem, the environment, or the chat for a credential. Do not put a key, token, or secret in the URL. OAuth is the default. An API key is sent only as an Authorization: Bearer header, after the user creates one with genfeed login and genfeed keys create -n "<label>" -p mcp (gf is the same CLI).
  2. Never guess a brand or a channel. Call get_brands and pass the selected brand's returned id as brandId. Take credentialId from list_brand_publishing_readiness for a brand that is already connected, and from get_connection_status while polling a connection you just started. get_connection_status and connect_social_account belong to onboarding, included in this package’s profile. If a connected client still lacks them, check its profile and permissions and report the limitation. The user can connect the channel at app.genfeed.ai and re-run list_brand_publishing_readiness. Do not invent either id.
  3. Before scheduling, call get_scheduler_capabilities for the platform and validate_scheduler_target for the proposed target. Do not schedule a target that comes back with errors.
  4. Headless publishing goes through create_scheduled_release, get_scheduled_release, and control_scheduled_release. create_post is a draft tool. Never set its confirmed flag. An MCP client does not render the publish card that flag expects.
  5. Media comes from generate with type set to image, video, voice, or music, or from a URL the user already has. Inspect get_generation_options before choosing models, settings or a credit budget. Local-file uploads use request_media_upload, upload the file to its returned presigned URL, then complete_media_upload; never invent an asset ID or URL.
  6. A pending approval is the user's decision. Call resolve_approval only after they choose. First inspect its availability and required role with find_tools. If it is unavailable to this account, or a call is rejected, stop and ask an authorized Genfeed reviewer to handle the approval. Never claim that a pending action has completed.
  7. Call get_account with include: ["credits"] before batch generation or batch scheduling.
  8. Connect with ?toolsets=core,scheduler,content,generation,analytics,brand,knowledge,onboarding on https://mcp.genfeed.ai/mcp. An unknown toolset name is rejected before login; inspect the public server card and report a deployment mismatch instead of silently widening access. Use find_tools without arguments to list toolsets, with query or toolset to search, and with name to inspect a full schema and permissions for tools outside that set. Do not guess a tool name.

Connect

Streamable HTTP. Preferred URL:

Installs
1
Repository
genfeedai/agent
First Seen
7 days ago
Security Audits