Server facts
hal MCP Server
Project
- Author
- DeanWard
- Repository
- github.com/DeanWard/HAL
- License
- Not specified
- Category
- MCP Gateways & Proxies
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 38
- Last commit
- Data as of
Tags
- hal
- http api
- mcp
Overview
For API workflows in clients such as Claude Desktop, HAL exposes GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS operations. Models can retrieve data, send request bodies, inspect response headers, or check which methods an endpoint supports. Requests accept headers, and the body-capable tools support secret placeholders in their payloads. The list-secrets tool reports available key names rather than credential values, so a model can discover which placeholders are available.
Credentials are supplied through environment variables and substituted when requests run, with placeholders usable in URLs, headers, and bodies. Namespaced secrets can have URL allow patterns to limit where they are sent. For specification-driven work, HAL reads JSON or YAML OpenAPI/Swagger files and creates endpoint tools named from operation identifiers. Those tools handle schema-based parameter validation, path and query parameters, and request bodies. A configurable base URL can override the specification’s servers, and built-in documentation includes generated tools.
hal setup notes
- hal records stdio only; confirm a network transport upstream before planning remote access.
- hal has no recorded license; confirm reuse terms in its repository.