# Opml To Csv — REST API endpoint `opml-to-csv`
Flatten an OPML subscription export (Feedly, Inoreader, NetNewsWire, podcast apps) into CSV with one row per feed: title, xml_url, html_url, folder_path, description and type. Nested folders become a folder_path joined with " / ". An outline carrying xmlUrl or url is a feed; an outline without one is a folder, and include_folders adds a row for each folder too. OPML 1.0 and 2.0 are read without a DOM, attribute names are matched case-insensitively and entities are decoded. Feed URLs are never fetched or checked.
- 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/opml-to-csv/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/opml-to-csv/
- Same tool on the other surface: https://findutils.com/mcp/opml-to-csv/
## Call the endpoint (verified example)
```bash
curl -X POST https://api.findutils.com/api/tools/opml-to-csv/execute \
-H "Content-Type: application/json" \
-d '{
"input": "\nFeeds\n"
}'
# Parameter schema
curl https://api.findutils.com/api/tools/opml-to-csv
```
## Input schema
| Argument | Type | Required | Description |
|---|---|---|---|
| `input` | string | yes | OPML (XML) text. |
| `include_folders` | boolean | no | Also write a row for each folder outline, with type "folder". Default false. Default: `false`. |
| `delimiter` | string | no | Field separator: "," (default), ";" or a tab. Default: `","`. |
Example arguments (verified):
```json
{
"input": "\nFeeds\n"
}
```
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:opml_to_csv`. Full MCP reference: https://findutils.com/mcp/opml-to-csv/
---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt