Generic REST API Any REST API
Point Sauble at any REST API that publishes an OpenAPI or Swagger spec and get read-only MCP tools generated automatically — no custom connector needed.
Provide the URL of an OpenAPI or Swagger spec and optional auth headers. Sauble fetches the spec at startup and registers one tool per GET endpoint, with fully typed parameters. POST and QUERY endpoints can be allowlisted for APIs that use them for read queries. Important: large APIs (100+ endpoints) will exceed the AI context window. Use the Path Filter to limit which endpoints become tools.
What sauble.ai can do
3 capabilities, grouped by what you are trying to find out.
Auto-generated from your API spec
(dynamic)Every GET endpoint in the spec becomes a tool. Tool names come from the operationId in the spec (e.g. listDevices, getSite).pingCheck server connectivity — always available, even if the spec failed to load.connection_statusDiagnose why the spec could not be loaded — appears only when the server starts in degraded mode.Large API specs (like NetBox with 300+ endpoints) will exceed the AI model's context window if loaded in full. Always set a Path Filter to scope the tools to just the area you need.
Ask it things like
Natural language — sauble.ai picks the right tools for you.
How Generic REST API organizes your data
The 3 things sauble.ai reads — and how they connect.
Endpoints
Each path in the OpenAPI spec becomes a callable tool — the full read surface of your API.
Parameters
Path parameters become required tool arguments; query parameters become optional ones — all typed from the spec.
Responses
JSON responses are returned directly to the AI agent for interpretation.