Hermai MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HERMAI_API_KEY | No | API key for authenticated Hermai APIs. Public schema lookup and schema-request intake work without a key. Setting a key also unlocks the fetch_schema execution tool. | |
| HERMAI_API_BASE | No | API base URL. Defaults to https://api.hermai.ai. | |
| HERMAI_PLATFORM_KEY | No | Alternative to HERMAI_API_KEY. API key for authenticated Hermai APIs. | |
| HERMAI_PLATFORM_URL | No | Alternative to HERMAI_API_BASE. API base URL. Defaults to https://api.hermai.ai. | |
| HERMAI_FETCH_TIMEOUT_MS | No | Request timeout for fetch_schema. Defaults to 120000. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_schemaB | Search Hermai for a schema by domain, task, category, or verification state. Read-only. |
| list_public_schemasA | List public schemas in the Hermai registry with optional filters. Read-only. |
| submit_schema_requestA | Submit the six-field intake for a missing or brittle browser workflow. Never include cookies, API keys, or private session data. |
| classify_browser_workflowA | Classify a prose workflow as direct API, hidden endpoint, browser-only, or needs owner/auth. Read-only and local. |
| check_schema_request_statusA | Check the status of a previously submitted Hermai schema request. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: searching schemas, listing public schemas, submitting requests, classifying workflows, and checking request status. No functional overlap.
All tool names follow a consistent verb_noun pattern with snake_case, making them predictable and easy to distinguish.
With 5 tools, the server covers the core operations for schema registry and workflow classification without being excessive or minimal.
The tool set provides search, list, submit, classify, and status-checking. A minor gap is the lack of a tool to view full details of a submitted request, but the core workflow is complete.