Post to Facebook with Hermes

Hermes Doesn't Post to Facebook on Its Own

Hermes Agent, the open-source, self-hosted agent from Nous Research, is genuinely good at what it's built for - running on your own server, remembering context across sessions, and posting to X natively out of the box. Facebook publishing is a separate system it doesn't ship with, and that's by design. Hermes is built around messaging channels like Telegram, Discord, Slack, and WhatsApp plus the X integration, and a full Facebook publishing stack is a genuinely different ball game.

Here is why you cannot just post on Facebook anytime you like here. Firstly, the graph API is Pages-only, so will not acknowledge anything until it receives a Page ID and does not permit publishing a personal profile post at all via API. You then need required page access token resolution which is a separate credential from your own personal one. It handles image, video and Reels through entirely separate upload flows (an API call for posting video and images are in no way the same) and requires that you have an actual account, not just test one, before the Meta app review process kicks in, which takes a while and cannot be guaranteed to be approved on first time try. If you want the full technical breakdown of what that involves, our Facebook API Alternative guide covers the Graph API side in depth.

And none of that is the real desired outcome. What you want is "this Hermes feature should connect to Facebook and say 'post to my Page' and just works without becoming a part-time Graph API integration project on top of what Hermes is already doing for you.

WoopSocial Gives Hermes Facebook Publishing

WoopSocial is a unified social media API with an MCP server built for exactly this. One connection, and Hermes can publish and schedule to your Facebook Page, plus Instagram, LinkedIn, X, Pinterest, TikTok, YouTube, BlueSky and Threads, all through the same MCP, so this isn't a Facebook-only bridge you'll need to replace the moment you want to post somewhere else.

This is where the trust bit comes in and is important to be clear about. At no point does your Hermes agent store your Facebook credentials - only your WoopSocial API key. The WoopSocial service looks up the Page ID, refreshes the Page access token and deals with the differences in media types for you without you (or Hermes) having to worry about it. It makes a bit more of a difference than you might realize as all that means is a compromised WoopSocial key exposes your posting access, not your actual Facebook login, and it means you're not storing a long-lived Facebook token anywhere inside your Hermes config.

When something occurs (a post succeeding, failing, etc) it feeds that back to you in English, not a Graph API error that you then have to look up yourself. If a post fails due to the video file being too large, or needing a token refresh, you get that information in sentence form, not a JSON blob with an error code you have to cross-reference against Meta's documentation. That's what Hermes' social media Facebook publishing looks like when you set it up correctly, a simple and straightforward conversation, not a dashboard full of error logs.

Functionally, this MCP connection acts as a Hermes agent social media skill, although delivered as an MCP server and not a regular Hermes skill file. This answer is the answer to the Nous Research Hermes Facebook posting question - there isn't a native path, WoopSocial's connection is the path.

Connect Hermes to Facebook in 3 Steps

Step 1: Get your WoopSocial API key

Free, takes about 70 seconds. Connect your Facebook Page inside the WoopSocial dashboard.

Step 2: Add the WoopSocial MCP server to Hermes

Open your Hermes config file (~/.hermes/config.yaml) and add WoopSocial as a remote MCP server under mcp_servers:

mcp_servers:
  woopsocial:
    url: "https://api.woopsocial.com/mcp?api_key=YOUR_WOOPSOCIAL_API_KEY"

Restart Hermes (hermes chat), and it will automatically discover WoopSocial's tools at startup.

Step 3: Tell Hermes to post

That's it, talk to it normally: "Post this update to my Facebook page and schedule the next three for weekday mornings."

No Graph API app to register, no Page token to manage by hand, and no code to write. The MCP handles Facebook's requirements underneath the conversation. And because Hermes runs scheduled work via cron and WoopSocial handles scheduling natively, Hermes can publish to Facebook while you're asleep, queue a week of posts on a Sunday night and let the cron jobs carry it through to Friday without you checking in once.

Facebook Posts, in Plain Language

Once it's connected, this is genuinely how you'll talk to it:

• "Post this image and caption to my Facebook page now"
• "Schedule this Facebook post for Thursday at 9am"
• "Draft a week of Facebook posts from my latest blog and queue them"
• "Post this video to Facebook" (the MCP handles the media type on its own)

One Skill, Nine Platforms

The bonus: the same MCP connection that gives Hermes Facebook also gives it Instagram, LinkedIn, X, Pinterest, TikTok, BlueSky, Threads and YouTube - so you set it up once, and Hermes posts everywhere.

Pricing is flat and predictable, the API and MCP access come on every plan, no separate charge for connecting Hermes specifically. And because WoopSocial maintains the actual platform integrations, when Facebook changes its Graph API, or when any of the other eight platforms change theirs, that's WoopSocial's maintenance work, not your agent's.

Give Your Hermes Agent Facebook Publishing

You already have Hermes running. Adding Facebook publishing is a config file edit and an API key, not a new developer app, not an app review queue, not code.

Get your free WoopSocial API key

FAQ