mcp-hermes
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HERMESFORGE_API_KEY | No | Your Hermesforge API key (optional for free tier; get one at https://hermesforge.dev/api/keys) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| screenshot_urlA | Capture a screenshot of any web page and return it as a base64-encoded image. Use this when you need to:
Args: url: The URL to screenshot (must be publicly accessible) width: Viewport width in pixels (default: 1280) height: Viewport height in pixels (default: 800) format: Image format - 'png' or 'jpeg' (default: 'png') full_page: Capture the full page height, not just the viewport (default: False) Returns: Base64-encoded image data with data URI prefix, ready to display. Example: "data:image/png;base64,iVBORw0KGgo..." Rate limits: 10/day free tier. Get a free API key at https://hermesforge.dev/api/keys for 100/day. Paid plans available for higher volume. |
| render_chartA | Render a Chart.js configuration as a chart image. Use this when you need to:
Args: chart_config: A JSON string containing a valid Chart.js configuration object. Example: '{"type":"bar","data":{"labels":["A","B","C"],"datasets":[{"label":"Values","data":[1,2,3]}]}}' width: Chart width in pixels (default: 800) height: Chart height in pixels (default: 600) format: Image format - 'png' or 'jpeg' (default: 'png') Returns: Base64-encoded chart image with data URI prefix. Rate limits: Shared with screenshot API. Get a free API key at https://hermesforge.dev/api/keys |
| get_api_usageA | Check your current API usage and rate limit status. Returns your current usage counts and remaining quota for:
Requires HERMESFORGE_API_KEY environment variable to be set. Without an API key, shows anonymous tier limits. |
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 3 tools
Each tool targets a distinct function: capturing a webpage, rendering a chart, and checking usage. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: screenshot_url, render_chart, get_api_usage. The conventions are uniform.
Three tools is a well-scoped count for a specialized image/rendering utility server. Each tool earns its place without unnecessary bloat.
The server covers its core domain well: screenshot capture, chart rendering, and usage tracking. Minor extras like PDF export or image metadata could be added, but no critical workflow is missing.