How to connect Upload-Post to Hermes Agent
Connect Upload-Post to Hermes with ClawLink: paste your Upload-Post key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.
Upload-PostAPI KEYMCPUpload-Post publishes, schedules, and manages content across social networks through one API.. Once connected, Hermes Agent can read and act on Upload-Post from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Upload-Post access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Upload-Post setup: pair once in the browser and your always-on Hermes agent can act on Upload-Post for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to Upload-Post.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Upload-Post
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Upload-Post?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Upload-Post in the ClawLink dashboard — paste your Upload-Post API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Upload-Post, summarize it in plain English, and point out anything that needs attention.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Upload-Post is connected in the dashboard, that agent calls the same 12 Upload-Post tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Upload-Post MCP for Hermes
Looking for a Upload-Post MCP server for Hermes Agent? ClawLink connects Upload-Post to Hermes Agent and exposes 12 Upload-Post tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Upload-Post integration works the same way.
What the Hermes Agent Upload-Post integration can do
12 Upload-Post tools are ready for Hermes Agent once the account is connected.
All 12 Upload-Post tools for Hermes
| Tool | What it does |
|---|---|
Get upload status upload_post_get_upload_status | Get the processing status and per-platform results for an asynchronous or scheduled upload |
List cached post analytics upload_post_list_cached_post_analytics | Return one page of cached per-post analytics for a profile without consuming the live |
List platform destinations upload_post_list_platform_destinations | List selectable Facebook Pages, LinkedIn organizations, Pinterest boards, or Google Business |
List profiles upload_post_list_profiles | List Upload-Post profiles and their connected social accounts |
List scheduled posts upload_post_list_scheduled_posts | Return one page of pending scheduled posts and the job IDs needed to edit or cancel them |
List upload history upload_post_list_upload_history | Return one page of past and in-progress Upload-Post uploads, including platform post IDs, URLs |
Create profile upload_post_create_profile | Create an Upload-Post profile for a unique caller-owned username; this does not connect any |
Update scheduled post upload_post_update_scheduled_post | Change the future publication time, title, or caption of an existing scheduled post |
Cancel scheduled post upload_post_cancel_scheduled_post | Permanently cancel a scheduled post before publication and delete its staged assets |
Enqueue post upload_post_enqueue_post | Insert one video, photo carousel, or text post into a profile's external publication queue |
Publish post upload_post_publish_post | Immediately publish one video, photo carousel, or text post to external connected platforms |
Schedule post upload_post_schedule_post | Schedule one video, photo carousel, or text post for future external publication to connected |
Try it: find the Upload-Post tool you need
Browse the 12 Upload-Post tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Pull the relevant data from Upload-Post, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Upload-Post, group them by priority, and recommend what Hermes should do next.
List the relevant items in Upload-Post, group them by priority, and recommend what Hermes should do next.
List the relevant items in Upload-Post, group them by priority, and recommend what Hermes should do next.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Upload-Post working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Upload-Post API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Upload-Post account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Upload-Post. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Upload-Post actions to the runtime in a format your agent can reliably use. | 12 tools for Upload-Post are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Upload-Post to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Upload-Post in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Upload-Post key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Upload-Post
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Upload-Post from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Upload-Post tools
Upload-Post tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Upload-Post call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Upload-Post returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Upload-Post has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Upload-Post integration?
Yes. ClawLink is the fastest way to connect Hermes to Upload-Post: link your Upload-Post account once in the browser and Hermes Agent can call the Upload-Post API through 12 ready-made tools — no custom code or token handling.
How do I connect Upload-Post to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Upload-Post in the dashboard and Hermes can use it from the next message — no config files, and the Upload-Post key you paste is stored server-side instead of in your environment.
How long does it take to connect Upload-Post to Hermes Agent?
About two minutes. Sign in, click Connect next to Upload-Post in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Upload-Post up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Upload-Post working from chat.
Hermes paired but still can't use Upload-Post
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
