EveryFeed

Operate EveryFeed through its MCP tools when they are available. Use the EveryFeed CLI for terminal workflows and public API operations that MCP does not expose, such as connection lifecycle, analytics, post state changes, deletion, and local-file upload.

Choose the interface

1. Prefer MCP for conversational drafting, provider discovery, validation, media generation, and confirmed post creation.
2. Use the CLI when the user explicitly asks for terminal automation or needs a CLI-only operation. See references/cli.md.
3. Do not silently switch organizations, profiles, channels, or interfaces. Resolve identifiers again after switching context.
4. If MCP tools are unavailable, direct the user to EveryFeed → Settings → Developers → Access. Never ask the user to paste a token into chat.
5. If a requested feature is unavailable through MCP but is supported by the CLI, explain the switch before running the command.