# Json To Xml — REST API endpoint `json-to-xml`

Convert a JSON value to XML. Object keys become element names; arrays produce repeated sibling elements. Invalid XML names fall back to <item>. Adds an XML declaration and wraps everything in a configurable root element.

- Category: data
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/json-to-xml/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/json-to-xml/
- Same tool on the other surface: https://findutils.com/mcp/json-to-xml/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/json-to-xml/execute \
  -H "Content-Type: application/json" \
  -d '{
    "json": "{\"a\":1}"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/json-to-xml
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `json` | string | yes | JSON string to convert. |
| `root_name` | string | no | Root element name. Default: "root". |
| `indent` | integer | no | Indent width. 0 emits single-line XML. Default: 2. |

Example arguments (verified):

```json
{
  "json": "{\"a\":1}"
}
```

Decoded `json` argument (readability only — send it as a string):

```json
{
  "a": 1
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:json_to_xml`. Full MCP reference: https://findutils.com/mcp/json-to-xml/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt