REST API Sources

Beyond MCP, XClaw also supports connecting arbitrary REST APIs as Agent data sources.

Many services don't have MCP implementations yet, but almost all have REST APIs. XClaw's REST API source lets you import all endpoints from an OpenAPI spec (Swagger), or manually define individual endpoints.

Once imported, each API endpoint becomes a tool available to the Agent. The Agent uses endpoint descriptions and parameter definitions to decide when to invoke it. Authentication supports API keys, Bearer tokens, and OAuth.

The value of REST API sources is coverage. While the MCP ecosystem is growing, your existing internal tools likely already have REST APIs. This feature lets you immediately give the Agent access to those tools without waiting for MCP adapters.

How to

Open Settings > REST API Sources and click "Add Data Source." You have two options:

The easiest is "Import OpenAPI Spec" — if your service has Swagger/OpenAPI documentation (typically a JSON or YAML file, or a URL), paste it in and XClaw auto-parses all endpoints into corresponding tools.

No OpenAPI doc? No problem — choose "Add Manually," fill in the endpoint URL, HTTP method, parameter descriptions, and a brief description. Write the description clearly — the Agent relies on it to decide when to use the tool.

Authentication is configured during setup. Pick API Key, Bearer Token, or OAuth, and enter the credentials. They're encrypted and stored securely.

Once added, these endpoints immediately appear as tools in the Agent's tool list. You can use them naturally in any session — for example, "Look up this user's order history in our internal system."