Hebline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEEPL_API_KEY | No | API key for DeepL translation service. If not provided, Hebline will route to free alternatives like MyMemory. | |
| GOOGLE_MAPS_API_KEY | No | API key for Google Maps geocoding service. If not provided, Hebline will route to free alternatives like Nominatim. | |
| LIBRETRANSLATE_API_KEY | No | API key for LibreTranslate translation service. If not provided, Hebline will route to free alternatives like MyMemory. |
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 |
|---|---|
| executeB | Route to the best service and execute the API call. Returns result with metadata (service used, cost, latency). |
| compareB | Compare all available services for a capability. Shows scores, costs, and Hebline's recommendation. |
| categoriesB | List all capabilities Hebline supports and which services are available for each. |
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 has a clearly distinct purpose with no overlap: 'categories' lists capabilities and services, 'compare' analyzes service options with recommendations, and 'execute' routes and runs API calls. The separation between listing, comparing, and executing is unambiguous.
All tool names follow a consistent verb-only pattern in lowercase, with no mixing of conventions. The naming is straightforward and predictable across the set.
Three tools is well-scoped for the server's purpose of managing and executing API services through Hebline. Each tool earns its place by covering a distinct phase: discovery, comparison, and execution.
The tool set provides complete coverage for the domain: it allows agents to discover capabilities, compare service options, and execute calls with metadata. There are no obvious gaps in the workflow from start to finish.