Using sfeed with Codex
Codex can use sfeed through the sfeed plugin, direct terminal commands, or a manually configured MCP server. For most repeatable workflows, use the plugin because it gives Codex the sfeed skill and MCP server entry together.
If you want Codex to walk through setup in the terminal, start with the agent setup prompt.
Recommended setup
curl -fsSL https://sfeed.dev/install.sh | sh
sfeed auth facebook connect
sfeed auth instagram connect
codex plugin marketplace add nem035/sfeed --sparse .agents/plugins --sparse plugins
codex plugin add sfeed@sfeedThe second command installs the plugin from the marketplace snapshot. You can also browse it in /plugins. Start a new Codex session after installing so the skill and MCP tools load. The plugin does not replace the CLI or Meta auth. It gives Codex the skill and MCP server entry for your local sfeed mcp command.
Local plugin development
From a local checkout of the public repo or this repo, add the marketplace root instead:
codex plugin marketplace add ./Manual MCP fallback
If you do not want to install the plugin, add only the MCP server:
codex mcp add sfeed -- sfeed mcpStart a new Codex session after adding the server. Codex loads MCP servers when the session starts.
Config form
The command above writes this kind of entry to Codex config:
[mcp_servers.sfeed]
command = "sfeed"
args = ["mcp"]First prompt to try
Use sfeed to check my status. If sfeed MCP tools are available, call sfeed_status and sfeed_destinations. Otherwise run sfeed status and sfeed destinations in the terminal. Ask which destination to use when the choice is ambiguous.Codex desktop app
Codex desktop uses the same idea: sfeed must be installed on the local machine, and the app needs an MCP server entry for sfeed mcp if you want structured tools. If the desktop app shows an MCP servers settings screen, add sfeed there. If it reads your Codex config, the CLI command above is the shortest setup. Restart the desktop session after changing MCP config.
CLI-only prompts
Run sfeed status and summarize which Facebook Pages and Instagram accounts are connected.
Run a dry run for this post: "Shipping v0.1.2 today." Do not publish it.
Post "Release notes are live" to Facebook using the Facebook destination returned by sfeed destinations after I confirm.MCP prompts
Call sfeed_status and sfeed_destinations. Ask which destination account to use when the choice is ambiguous.
Use sfeed_post with dry_run set to true for ./assets/launch-card.jpg on Instagram with the caption "Launch day. v0.2.1 is live." Show me the result before posting.
Use sfeed_post to schedule "Standup starts in 30 minutes" for 2026-04-06T13:00:00Z using the canonical Facebook destination ID from sfeed_destinations.Demo script you can record
1. Open Codex in a repo
2. Ask it to inspect sfeed status
3. Ask it to list publishing destinations
4. Give it a short post request
5. Approve the draft
6. Let it call sfeed_post or run sfeed post
7. Show the returned URLFAQ
Can I install sfeed as a Codex plugin?
Yes. Add the marketplace, then run codex plugin add sfeed@sfeed or install sfeed from /plugins. You still need sfeed installed locally and authenticated for the platforms you want.
Can Codex use sfeed without MCP?
Yes. If Codex can run shell commands, it can use sfeed status, sfeed destinations, and sfeed post directly after auth.
When should I configure MCP?
Use MCP when you want Codex to see typed tools instead of relying on command-line syntax. MCP is better for repeatable agent workflows, queue inspection, previews, and canonical destination selection.
Does pointing Codex at sfeed.dev install anything?
No. The site gives Codex context. The local machine still needs sfeed installed, Meta auth completed, and MCP configured if you want MCP tools.