BaseLinker + Hermes Agent
How to connect BaseLinker to Hermes Agent
Connect BaseLinker to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
On this page
Overview
This guide connects BaseLinker to Hermes Agent through Agent200's MCP server. When you finish, Hermes Agent can search, read and act in BaseLinker with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Hermes Agent with your Agent200 API key. Your BaseLinker account is connected through managed OAuth: you approve access once on BaseLinker's own page, and Agent200 keeps the connection working.
- Connector
- BaseLinker
- Works with
- Hermes Agent ยท Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- You need
- An Agent200 API key
- Tools
- 6 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- BaseLinker enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a BaseLinker account. They approve access once, on BaseLinker's own page.
- Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.
Connect BaseLinker to Hermes Agent
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers BaseLinker and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Store your key in ~/.hermes/.env
Keep the key out of
config.yaml: Hermes reads it from~/.hermes/.env.~/.hermes/.envMCP: Hermes Agent key in ~/.hermes/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Add the server to ~/.hermes/config.yaml
Add an entry under
mcp_serverswith the URL and the Authorization header. Do not settransport: sse: Agent200 serves streamable HTTP.~/.hermes/config.yamlMCP: Hermes Agent config.yaml entry mcp_servers: agent200: url: "https://api.agent200.com/mcp/" headers: Authorization: "Bearer ${AGENT200_API_KEY}" -
4
Step 4: Reload and test
In a running session, run
/reload-mcp, or restart Hermes. Then check what the server returned from a terminal.TerminalMCP: Hermes Agent reload and test # In a running Hermes session: /reload-mcp hermes mcp test agent200 hermes mcp list -
5
Step 5: Connect your BaseLinker account
The first time you ask Hermes Agent for something in BaseLinker, Agent200 returns an authorization link. Open it and approve access on BaseLinker's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Show me today's new orders in BaseLinker
What should come back
- A result from that user's own BaseLinker account.
-
Behind the scenes, Hermes Agent calls
baselinker_list_orders.
If you get an authorization link instead, the user has not connected BaseLinker yet. Show them the link, then run the request again.
Get your API key
Create a key in the Agent200 dashboard. It reaches BaseLinker and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect BaseLinker to Hermes Agent.
Goal: connect BaseLinker to Hermes Agent with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/baselinker/framework/hermes-agent/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure BaseLinker is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands. 4. The first BaseLinker request returns an authorization link if the user has not connected BaseLinker yet: show it to them and continue once they have approved access on BaseLinker's own page. 5. Check it works with this request: "Show me today's new orders in BaseLinker" What should come back: - A result from that user's own BaseLinker account. - Behind the scenes, Hermes Agent calls `baselinker_list_orders`. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in BaseLinker, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/baselinker/framework/hermes-agent.md
BaseLinker tools Hermes Agent can call
-
List orders
Readbaselinker_list_ordersList orders and their details.
-
List order statuses
Readbaselinker_list_order_statusesList the order statuses set up in the account.
-
Add an order
Writebaselinker_add_orderAdd a new order.
-
Set order status
Writebaselinker_set_order_statusMove an order to another status.
-
List products
Readbaselinker_list_productsList the products in an inventory.
-
Update product stock
Writebaselinker_update_stockChange the stock level of products.
No tool matches that search.
How it works
-
01
You ask Hermes Agent
In your own words, for something in BaseLinker.
-
02
Hermes Agent picks a tool
It sees the BaseLinker tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own BaseLinker connection, within the tools and scopes your project allows.
-
04
Hermes Agent answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's BaseLinker account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and BaseLinker enforces what its API grants.
Troubleshooting
The connection fails and names a missing variable
Add AGENT200_API_KEY to ~/.hermes/.env and run /reload-mcp.
The server answers 401 or 403
Check the key in ~/.hermes/.env and that the header reads exactly Bearer ${AGENT200_API_KEY}.
The initialize request fails with 400 or 405
That points to an SSE setting. Remove any transport: sse line from the entry and check the URL is exactly the Agent200 MCP server address.
The BaseLinker tools do not appear
Run hermes mcp test agent200, check the entry is not disabled and no tools filter hides them, then /reload-mcp. Hermes names them mcp_agent200_....
Hermes Agent shows a BaseLinker authorization link
You have not connected BaseLinker yet, or the connection needs to be approved again. Open the link, approve access on BaseLinker's own page, then ask Hermes Agent again.
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that BaseLinker and the tools you need are enabled in the dashboard's Connectors settings, and that you granted BaseLinker the access the task needs.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Hermes Agent's MCP settings, and stop using the old one. Paste the key only into Hermes Agent's settings, never into a chat.

