How to connect Ordinal to Hermes Agent
Connect Ordinal to Hermes with ClawLink: paste your Ordinal key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.
OrdinalAPI KEYMCPOrdinal is a collaborative social media planning platform for creating, reviewing, scheduling, and analyzing content across connected channels.. Once connected, Hermes Agent can read and act on Ordinal from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Ordinal 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 Ordinal setup: pair once in the browser and your always-on Hermes agent can act on Ordinal 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 Ordinal.
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 Ordinal
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Ordinal?"
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 Ordinal in the ClawLink dashboard — paste your Ordinal API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Ordinal, 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 Ordinal is connected in the dashboard, that agent calls the same 13 Ordinal tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Ordinal MCP for Hermes
Looking for a Ordinal MCP server for Hermes Agent? ClawLink connects Ordinal to Hermes Agent and exposes 13 Ordinal tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Ordinal integration works the same way.
What the Hermes Agent Ordinal integration can do
13 Ordinal tools are ready for Hermes Agent once the account is connected.
All 13 Ordinal tools for Hermes
| Tool | What it does |
|---|---|
Get post ordinal_get_post | Return one Ordinal post by ID with its full channel content, attached assets, labels, profiles |
Get profile analytics ordinal_get_profile_analytics | Return follower history or post performance for one connected LinkedIn or X scheduling profile |
Get workspace ordinal_get_workspace | Return the workspace bound to the connected Ordinal API key, including its ID, name, slug |
List ideas ordinal_list_ideas | List non-archived content ideas with filters and one cursor-controlled page of results |
List labels ordinal_list_labels | Return workspace labels and their IDs for filtering or labeling posts and ideas |
List posts ordinal_list_posts | List non-archived workspace posts with filters and one cursor-controlled page of results |
List profiles ordinal_list_profiles | List connected social profiles by capability so their IDs can be used for scheduling |
Add idea to calendar ordinal_add_idea_to_calendar | Convert an existing Ordinal idea into a regular calendar post on a chosen date |
Create idea ordinal_create_idea | Create reusable Ordinal content for one or more supported social channels without adding it to |
Create post ordinal_create_post | Create an Ordinal calendar post with content for one or more social channels |
Unschedule post ordinal_unschedule_post | Cancel a pending scheduled publication and change the Ordinal post status to Finalized |
Update post ordinal_update_post | Update selected fields or channel content on a non-archived Ordinal post |
Schedule post ordinal_schedule_post | Schedule or reschedule an Ordinal post for external publication to its configured social |
Try it: find the Ordinal tool you need
Browse the 13 Ordinal 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 Ordinal, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ordinal, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Ordinal, summarize it in plain English, and point out anything that needs attention.
List the relevant items in Ordinal, 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 Ordinal working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Ordinal API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Ordinal 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 Ordinal. | 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 Ordinal actions to the runtime in a format your agent can reliably use. | 13 tools for Ordinal are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Ordinal 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 Ordinal in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Ordinal 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 Ordinal
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 Ordinal 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 Ordinal tools
Ordinal 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 Ordinal 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.
Ordinal 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 Ordinal 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 Ordinal integration?
Yes. ClawLink is the fastest way to connect Hermes to Ordinal: link your Ordinal account once in the browser and Hermes Agent can call the Ordinal API through 13 ready-made tools — no custom code or token handling.
How do I connect Ordinal 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 Ordinal in the dashboard and Hermes can use it from the next message — no config files, and the Ordinal key you paste is stored server-side instead of in your environment.
How long does it take to connect Ordinal to Hermes Agent?
About two minutes. Sign in, click Connect next to Ordinal in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Ordinal 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 Ordinal working from chat.
Hermes paired but still can't use Ordinal
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.
