Expose selected APIs as authenticated MCP tools
Hookway is a self-hosted API-to-MCP gateway. Import selected OpenAPI operations or build native tool branches, review the YAML, and run the endpoint in your infrastructure.
Choose the operations an agent can call
Import an OpenAPI 3.0 or 3.1 document locally. Select supported operations, review input and output schemas, and grant each caller only the tools it needs. Writes require an explicit mutation grant. Importing does not deploy or merge a configuration.
Keep caller and API credentials separate
Authenticate MCP callers with API keys or an external OAuth provider. Configure upstream credentials independently. Caller tokens are not forwarded to the API, and the builder does not resolve secret references.
Run one reviewed tool branch per call
Each tool selects a branch that calls an HTTP API or runs native processing, then returns an MCP result. You can expose several endpoints with separate paths, catalogues and permissions. Hookway hosts your configured tools; it is not a proxy that aggregates arbitrary existing MCP servers.
Deliver business events to compatible clients
MCP Events subscriptions receive matching named events through signed callbacks. Clients must support the event extension. Callback acceptance confirms receipt, not completion of an agent task. Delivery is at least once and unordered, without historical catch-up.
Read MCP Events compatibility and delivery boundariesReview before you connect
The importer supports selected JSON operations, not every OpenAPI feature. Browser connections also need a reachable endpoint and an allowed origin. Connect & test runs live tools against your deployment, including permitted mutations.
Run Hookway locally
Clone the repo and start the example stack. No hosted account required.
$ git clone --branch main https://github.com/jaysongiroux/hook_way.git && cd hook_way && make dev-up