The tool catalogue
230+ tools the agent can call directly — what is in there, how it decides to use one, and what each call costs.
Updated September 2, 2026
Beyond reading files and running commands, the agent can call any tool in the ToolsXpo catalogue — 230+ of them, reachable through the built-in MCP server.
What is in there
Broadly: format and validate (JSON, YAML, XML, SQL), convert between formats and units, encode and decode, generate (UUIDs, hashes, passwords, QR codes), extract from documents and images, and inspect (DNS, headers, certificates, image metadata).
Browse the full list at toolsxpo.com/tools.
How the agent decides
It picks a tool when one fits better than writing code. Asked to validate a large JSON file it calls the validator rather than writing a script — faster, and the result is authoritative rather than a program that might be wrong.
You do not need to name a tool. Describing the outcome is enough.
What they cost
Tool calls draw on general compute credits, not AI token credits. The two balances are separate, and a tool-heavy task can be cheap in AI terms while using compute.
Per-call cost is listed on each tool's page.
Turning it off
Disable the toolsxpo-mcp server under MCP if you would rather the agent solved everything with code. It cannot be deleted — it is provisioned with your account — but disabled is disabled.
Using them outside the editor
The same catalogue is available through the ToolsXpo API and the CLI, with the same key. Anything the agent can do here, a script of yours can do too.
See also
Related
Quickstart: your first task with ToolsXpo Code
Install the extension, sign in from your browser, and give the agent its first task — about five minutes end to end.
Choosing a model
What the model picker shows you, why some models are greyed out, and how to search a catalogue of hundreds with filters.
What an agent task costs
How a ToolsXpo Code request is priced, what makes one task cheaper than another, and where to see what you spent.
Agent and scout tiers
Two reserved names — toolsxpo-agent and toolsxpo-scout — that let your workspace decide which model runs, without pinning it into the extension.