Post to LinkedIn and Bluesky from Hermes Agent

2. Add OpenTweet to config.yaml

Hermes reads MCP servers from the mcp_servers block of ~/.hermes/config.yaml. A server with a url connects over Streamable HTTP, and headers carries the key. Hermes fills in ${OPENTWEET_API_KEY} from the environment, or you can paste the key in directly.

# ~/.hermes/config.yaml
mcp_servers:
  opentweet:
    url: "https://mcp.opentweet.io/mcp"
    headers:
      Authorization: "Bearer ${OPENTWEET_API_KEY}"

Then run /reload-mcp in your Hermes session. The messaging gateway (Telegram, Discord, Slack) picks up the change by itself within about a minute. The header is required: the hosted server has no OAuth flow, and the URL alone returns 401.

Prefer a local process? The npm package runs over stdio with the key in env. It exposes the same tools.

# ~/.hermes/config.yaml
mcp_servers:
  opentweet:
    command: "npx"
    args: ["-y", "@opentweet/mcp-server"]
    env:
      OPENTWEET_API_KEY: "ot_your_key_here"

Config keys as described in the Hermes MCP config reference, checked September 2026.

4. Schedule a week of posts

The safe pattern is draft, review, then schedule. Hermes creates each post as a draft pinned to LinkedIn and Bluesky, you read them in the dashboard or in chat, and one opentweet_batch_schedule call sets the times.

> Draft five LinkedIn and Bluesky posts for next week from the
  changelog below, one per weekday. Keep each Bluesky-safe (under 300
  characters). Save them as drafts and show me the ids.

> Looks good. Schedule them Monday to Friday at 14:00 UTC.

// Step 1, once per post: create a draft pinned to both networks
opentweet_create_tweet({
  text: "Monday: CSV export now includes custom fields.",
  platforms: ["linkedin", "bluesky"]
})

// Step 2, one call for the week (up to 50 entries)
opentweet_batch_schedule({
  schedules: [
    { post_id: "66f1a0c2e4b0a1b2c3d4e5f1", scheduled_date: "2026-09-28T14:00:00Z" },
    { post_id: "66f1a0c2e4b0a1b2c3d4e5f2", scheduled_date: "2026-09-29T14:00:00Z" },
    { post_id: "66f1a0c2e4b0a1b2c3d4e5f3", scheduled_date: "2026-09-30T14:00:00Z" },
    { post_id: "66f1a0c2e4b0a1b2c3d4e5f4", scheduled_date: "2026-10-01T14:00:00Z" },
    { post_id: "66f1a0c2e4b0a1b2c3d4e5f5", scheduled_date: "2026-10-02T14:00:00Z" }
  ]
})

opentweet_batch_schedule takes a schedules array of post_id and scheduled_date pairs, up to 50, with dates in the future. It only sets times: each post keeps the networks it was drafted with. Your plan's daily post limit still applies. For a single post, passing scheduled_date straight to opentweet_create_tweet does the same job.

OpenTweet vs calling the LinkedIn API yourself

You can give Hermes LinkedIn access without OpenTweet. It is more work, and Bluesky is a second integration on top.

If you only need LinkedIn, never schedule, and are happy to maintain the OAuth flow, going direct is reasonable. If you want LinkedIn, Bluesky and X from one Hermes config with a queue you can review, OpenTweet is less to build.