# How to connect Classmarker to Hermes Agent (paste one key, 28 tools) > Connect Classmarker to Hermes with ClawLink: paste your Classmarker key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/hermes/classmarker Most guides for giving Hermes Agent Classmarker 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 Classmarker setup: pair once in the browser and your always-on Hermes agent can act on Classmarker 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 Classmarker. 1. **Install ClawLink** — add the plugin to Hermes Agent once. 2. **Connect Classmarker** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask Hermes Agent in plain English. **Paste this into Hermes to set up ClawLink:** > Set up ClawLink for Hermes and tell me when it's ready. > 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable` > 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait. > 3. I'll approve it in my browser, then reply "approved". > 4. When I say approved, finish setup: `hermes clawlink finish` > 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready. **Alternative for any agent (no plugin needed):** if the Hermes Agent plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect classmarker # connect Classmarker (browser OAuth) npx -y @useclawlink/cli actions classmarker # list available actions npx -y @useclawlink/cli run classmarker --input '' # execute (add --confirm for writes) ``` ### Install by command The prompt above walks Hermes through this. By hand, it is four commands and a browser approval: ```bash 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 test ``` Then connect Classmarker in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Classmarker API key once. Verify the connection by asking Hermes: > Pull the relevant data from Classmarker, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Classmarker is connected in the dashboard, that agent calls the same 28 Classmarker tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Classmarker MCP for Hermes Looking for a Classmarker MCP server for Hermes Agent? ClawLink connects Classmarker to Hermes Agent and exposes 28 Classmarker tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using OpenClaw instead? The [OpenClaw Classmarker integration](https://claw-link.dev/openclaw/classmarker) works the same way. ## What the Hermes Agent Classmarker integration can do 28 Classmarker tools are ready for Hermes Agent once the account is connected. The 22 below are the ones people reach for most; your agent can call all 28. ### 22 of 28 Classmarker tools for Hermes | Tool | What it does | |---|---| | **Get group details** `classmarker_get_group_details` | Retrieve detailed information about a specific group by ID | | **Get initial finished after timestamp** `classmarker_get_initial_finished_after_timestamp` | Compute the initial finishedAfterTimestamp for paginating ClassMarker test results | | **Get question** `classmarker_get_question` | Retrieve a specific question by its ID | | **Get recent results group exam** `classmarker_get_recent_results_group_exam` | Fetch recent test results for a specific group and exam | | **Get recent results link exam** `classmarker_get_recent_results_link_exam` | Fetch recent exam results for a specific link and test combination | | **Get test details** `classmarker_get_test_details` | Retrieves detailed information for a specific test (exam) including its name and all assignment | | **Get user details** `classmarker_get_user_details` | Retrieve detailed information about a specific user | | **List categories** `classmarker_list_categories` | Retrieves all question categories organized in a hierarchical structure | | **List certificates** `classmarker_list_certificates` | List all certificates | | **List questions** `classmarker_list_questions` | Retrieve a paginated list of questions from your question bank | | **List recent results for groups** `classmarker_list_recent_results_for_groups` | Retrieve recent exam results for all groups in your ClassMarker account | | **List recent results for links** `classmarker_list_recent_results_for_links` | Retrieves recent test results from ALL links accessible to your API key | | **List users** `classmarker_list_users` | List all users | | **List webhooks** `classmarker_list_webhooks` | Retrieve all configured webhooks | | **Create access list item** `classmarker_create_access_list_item` | Add one or more access codes to an access list | | **Create category** `classmarker_create_category` | Create a new question category | | **Create group** `classmarker_create_group` | Create a new group | | **Create question** `classmarker_create_question` | Create a new question with specified text, type, and category in ClassMarker | | **Create user** `classmarker_create_user` | Create a new user in ClassMarker | | **Put category** `classmarker_put_category` | Update an existing sub-category | | **Put parent category** `classmarker_put_parent_category` | Update an existing parent category | | **Put question** `classmarker_put_question` | Updates an existing question in the ClassMarker question bank | ## Example prompts **Get Group Details** > Pull the relevant data from Classmarker, summarize it in plain English, and point out anything that needs attention. **Get Initial Finished After Timestamp** > Pull the relevant data from Classmarker, summarize it in plain English, and point out anything that needs attention. **Get Question** > Pull the relevant data from Classmarker, summarize it in plain English, and point out anything that needs attention. **Get Recent Results Group Exam** > Pull the relevant data from Classmarker, 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 Classmarker working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Classmarker API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Classmarker 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 Classmarker. | 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 Classmarker actions to the runtime in a format your agent can reliably use. | 28 tools for Classmarker are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Classmarker 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 Classmarker in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the Classmarker key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### Hermes paired but still can't use Classmarker 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 Classmarker 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 Classmarker tools Classmarker 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 Classmarker 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. ### Classmarker 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 Classmarker has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a Hermes Agent Classmarker integration? Yes. ClawLink is the fastest way to connect Hermes to Classmarker: link your Classmarker account once in the browser and Hermes Agent can call the Classmarker API through 28 ready-made tools — no custom code or token handling. ### How do I connect Classmarker 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 Classmarker in the dashboard and Hermes can use it from the next message — no config files, and the Classmarker key you paste is stored server-side instead of in your environment. ### How long does it take to connect Classmarker to Hermes Agent? About two minutes. Sign in, click Connect next to Classmarker in the dashboard, authenticate, and Hermes Agent can use it from the next chat message. ### Why use ClawLink instead of wiring Classmarker 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 Classmarker working from chat. ### Hermes paired but still can't use Classmarker 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 - [Hermes GitHub integration](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows - [Hermes PagerDuty integration](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/hermes/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.