When should I configure sfeed MCP for Codex?

Configure MCP when you want Codex to use structured tools such as sfeed_status, sfeed_pages, and sfeed_post instead of shell commands.

Does pointing Codex at sfeed.dev install the MCP server?

No. The site gives Codex instructions and docs. Codex still needs sfeed installed, Facebook authentication completed, and sfeed added to its MCP configuration before MCP tools appear.

Using sfeed with Codex

Q: Can Codex use sfeed without MCP?

Yes. If Codex has terminal access, it can run sfeed CLI commands after you install sfeed and authenticate with sfeed auth facebook.

Codex can use sfeed two ways. For a guided setup or one-off post, Codex can run normal terminal commands. For structured agent workflows, add sfeed as an MCP server so Codex gets named tools for status, Pages, posting, and scheduling.

If you want Codex to walk through setup in the terminal, start with the agent setup prompt.

1. Install sfeed

curl -fsSL https://sfeed.dev/install.sh | sh
sfeed auth facebook

This is enough for Codex to use the plain CLI, as long as Codex has permission to run shell commands in the folder where your posts and media live.

2. Optional: add MCP tools

codex mcp add sfeed -- sfeed mcp

Start 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. Otherwise run sfeed status in the terminal. If I have more than one connected Page, list them before drafting anything.

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 on page_id "112233445566778" after I confirm.

MCP prompts

Call sfeed_status. If more than one Page is connected, call sfeed_pages and ask which Page to use.

Use sfeed_post to post ./assets/launch-card.jpg to Instagram with the caption "Launch day. v0.1.2 is live." Ask me to confirm before posting.

Use sfeed_post to schedule "Standup starts in 30 minutes" for 2026-04-06T13:00:00Z on page_id "112233445566778".

Demo script you can record

1. Open Codex in a repo
2. Ask it to inspect sfeed status
3. Ask it to list Pages if needed
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 URL

FAQ

Can Codex use sfeed without MCP?

Yes. If Codex can run shell commands, it can use sfeed status, sfeed pages, 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 safer page 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.

Open the Cookbook

Back to Docs