# Query String Parse — REST API endpoint `query-string-parse`

Parse a URL query string into an object. Leading "?" is optional. Repeat keys collapse into string arrays.

- 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/query-string-parse/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/query-string-parse/
- Same tool on the other surface: https://findutils.com/mcp/query-string-parse/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/query-string-parse/execute \
  -H "Content-Type: application/json" \
  -d '{
    "query": "a=1&b=2"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/query-string-parse
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Query string (with or without leading "?"). |

Example arguments (verified):

```json
{
  "query": "a=1&b=2"
}
```

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:query_string_parse`. Full MCP reference: https://findutils.com/mcp/query-string-parse/

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