Summary
An API nobody has written a server for becomes callable for the length of the session.
Registration is the whole product: hand it a configuration and the endpoints described in it become callable, either as generated tools or through call_api with an endpoint name. That puts the burden of describing the API on you, and it is worth being clear about what get_api_schema returns — the configuration you registered, not the API's own contract, so a wrong parameter shows up at call time. test_api_connection exists for exactly that gap.
What it is
A server that builds MCP tools from API configurations registered while it runs, with a generic call path and a schema lookup beside them.
What you get
- An API registered from one configuration object, its endpoints becoming callable tools, and removed again when it should no longer be exposed
- call_api as a generic path — any registered API, any endpoint name, parameters passed through — for ad-hoc calls that do not warrant their own tool
- get_api_schema to read an API's or a single endpoint's parameters and requirements before making the call
- list_apis for what is registered right now, and test_api_connection to check one responds before you build on it
Requirements
An HTTP API you can describe in a configuration, and whatever credentials that API itself requires. MIT.
Setup effort
One command — uvx apiweaver run