How to connect Starshipit to Hermes Agent
Connect Starshipit to Hermes with ClawLink: paste your Starshipit key once and 15 tools work from chat. No MCP server to run, nothing stored on your machine.
StarshipitAPI KEYMCPStarshipit provides shipping, fulfilment, order, tracking, and warehouse management APIs for ecommerce operations.. Once connected, Hermes Agent can read and act on Starshipit from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Starshipit 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 Starshipit setup: pair once in the browser and your always-on Hermes agent can act on Starshipit 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 Starshipit.
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 Starshipit
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Starshipit?"
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 Starshipit in the ClawLink dashboard — paste your Starshipit API key once.
Verify the connection by asking Hermes:
Pull the relevant data from Starshipit, 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 Starshipit is connected in the dashboard, that agent calls the same 15 Starshipit tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Starshipit MCP for Hermes
Looking for a Starshipit MCP server for Hermes Agent? ClawLink connects Starshipit to Hermes Agent and exposes 15 Starshipit tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Starshipit integration works the same way.
What the Hermes Agent Starshipit integration can do
15 Starshipit tools are ready for Hermes Agent once the account is connected.
All 15 Starshipit tools for Hermes
| Tool | What it does |
|---|---|
Get order starshipit_get_order | Retrieve one order by its Starshipit numeric ID or source-platform order number |
Get shipping rates starshipit_get_shipping_rates | Quote available Starshipit shipping services and prices for a destination and one or more |
Get tracking starshipit_get_tracking | Get current shipment status and carrier tracking events by tracking number or order number |
Get wms performance starshipit_get_wms_performance | Return Starshipit WMS order-cycle and SLA performance metrics for the previous 1 to 90 days |
List manifests starshipit_list_manifests | Return one page of manifests in reverse chronological order |
List products starshipit_list_products | Search and page through the Starshipit product catalogue with optional sorting |
List tags starshipit_list_tags | Return one page of user-defined order tags, optionally filtered by tag name |
List unshipped orders starshipit_list_unshipped_orders | Return one page of unshipped orders, optionally limited to orders created or updated after a |
List wms inventory starshipit_list_wms_inventory | Return one page of Starshipit WMS inventory grouped by product or location, including stock |
Search orders starshipit_search_orders | Search orders by a phrase and optional field, status, or child-account inclusion filter |
Create order starshipit_create_order | Create one unshipped Starshipit order with destination, line items, packages, sender, and |
Update order starshipit_update_order | Update editable fields on one Starshipit order identified by order_id or order_number |
Create manifest starshipit_create_manifest | Create and finalize a Starshipit manifest PDF for only the explicitly listed shipments |
Create shipping label starshipit_create_shipping_label | Create shipping labels for one Starshipit order |
Create shipping labels starshipit_create_shipping_labels | Create shipping labels for multiple existing Starshipit orders in one irreversible batch |
Try it: find the Starshipit tool you need
Browse the 15 Starshipit 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 Starshipit, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Starshipit, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Starshipit, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Starshipit, summarize it in plain English, and point out anything that needs attention.
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 Starshipit working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Starshipit API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Starshipit 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 Starshipit. | 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 Starshipit actions to the runtime in a format your agent can reliably use. | 15 tools for Starshipit are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Starshipit 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 Starshipit in the browser, and the 15 tools above work from chat. There is no SDK and no config file, and the Starshipit 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 Starshipit
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 Starshipit 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 Starshipit tools
Starshipit 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 Starshipit 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.
Starshipit 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 Starshipit 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 Starshipit integration?
Yes. ClawLink is the fastest way to connect Hermes to Starshipit: link your Starshipit account once in the browser and Hermes Agent can call the Starshipit API through 15 ready-made tools — no custom code or token handling.
How do I connect Starshipit 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 Starshipit in the dashboard and Hermes can use it from the next message — no config files, and the Starshipit key you paste is stored server-side instead of in your environment.
How long does it take to connect Starshipit to Hermes Agent?
About two minutes. Sign in, click Connect next to Starshipit in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Starshipit 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 Starshipit working from chat.
Hermes paired but still can't use Starshipit
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.
Related
Cloudcart tools
CloudCart is an e-commerce platform that enables businesses to create and manage online stores efficiently.
Connect Wix
Manage sites, products, orders, and bookings
Connect Baselinker
BaseLinker is a comprehensive e-commerce management platform that integrates with various marketplaces, online stores, carriers, and accounting systems to streamline order processing, inventory management, and sales automation.