> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Available tools
> Every tool the Scanova MCP server exposes to a connected AI assistant.
**Source of truth for this page.** This list is transcribed directly from `list_mcp_tools()` in [`src/mcp_http/registry.py`](https://github.com/trycon/scanova-mcp/blob/main/src/mcp_http/registry.py) of the public `trycon/scanova-mcp` repository — the exact code that answers a real MCP client's `tools/list` call against `https://mcp.scanova.io/mcp`. It is **not** sourced from that repository's README, which is stale: the README advertises only 7 QR-management tools, while the deployed server actually registers 42 across 8 categories. Each tool's **Type** below reflects its real MCP annotation (`readOnlyHint`/`destructiveHint`) from the same file.
A connected AI assistant calls `initialize` first (the server reports `protocolVersion: "2025-03-26"`, `serverInfo: { name: "scanova-mcp", version: "1.0.0" }`), then `tools/list` to discover everything below, then `tools/call` per tool. All 42 tools operate against your own Scanova account, using whichever credential your client authenticated with (see [Setup](/mcp/setup)).
## Scanova docs bridge
Lets the assistant consult this documentation site live, mid-conversation.
| Tool | Type | Description |
| :--------------- | :-------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `probe_docs_mcp` | Read-only | Checks connectivity to Scanova's docs MCP server and lists its available tools. |
| `query_docs` | Read-only | Searches Scanova's API documentation (`mode="search"`), or runs a read-only filesystem-style command — `cat`, `head`, `rg`, `tree`, `jq` — against the docs (`mode="filesystem"`), e.g. to read a specific reference page directly. |
## QR code design
| Tool | Type | Description |
| :---------------------- | :-------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_qr_design_options` | Read-only | Returns the full catalog of design options — data patterns, gradient styles, eye shapes, frames, error-correction levels, and fonts — so the assistant can offer real choices before calling `set_qr_design`. |
| `set_qr_design` | Write | Applies a visual design to an existing QR code from friendly named parameters (pattern, colors, eye shape, frame, logo, etc.). Only the fields you specify change — everything else is preserved by merging onto the QR code's current design. |
## QR code management
| Tool | Type | Description |
| :------------------------- | :---------- | :------------------------------------------------------------------------------------------------------------- |
| `create_qr_code` | Write | Creates a new QR code. |
| `list_qr_codes` | Read-only | Lists QR codes and/or pages in the account, with paging and search; can filter to just QR codes or just pages. |
| `update_qr_code` | Write | Updates an existing QR code. |
| `retrieve_qr_code` | Read-only | Gets details of a specific QR code. |
| `download_qr_code` | Read-only | Downloads a QR code image as PNG, JPG, PDF, SVG, or EPS. |
| `activate_qr_code` | Write | Activates a QR code. |
| `deactivate_qr_code` | Write | Deactivates a QR code. |
| `delete_qr_code` | Destructive | Permanently deletes a QR code. |
| `get_qr_categories` | Read-only | Lists available QR code categories (URL, vCard, WiFi, Document, Social Media, etc.). |
| `download_qr_printable` | Read-only | Generates a print-optimized PDF version of a QR code. |
| `attach_form_to_qr` | Write | Attaches a lead-capture form to a QR code. |
| `detach_form_from_qr` | Write | Removes the lead-capture form from a QR code. |
| `attach_lead_list_to_qr` | Write | Attaches a lead list to a QR code for lead capture. |
| `detach_lead_list_from_qr` | Write | Removes the lead list from a QR code. |
## Analytics
| Tool | Type | Description |
| :------------------ | :-------- | :-------------------------------------------------------------------------------------------------- |
| `get_account_stats` | Read-only | Retrieves account-level usage counters — total QR codes, scans, users, etc. |
| `get_qr_analytics` | Read-only | Retrieves QR code performance metrics broken down by device, geography, date, and other dimensions. |
| `export_analytics` | Read-only | Exports QR code analytics as an Excel or PDF report. |
| `export_raw_scans` | Read-only | Exports row-level scan logs as CSV or Excel, for custom BI pipelines. |
## Folder management
| Tool | Type | Description |
| :------------------------------ | :---------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `create_folder` | Write | Creates a new folder to organize QR codes or pages. |
| `list_folders` | Read-only | Lists all folders of a given type (`qr` or `page`). |
| `update_folder` | Write | Renames an existing folder. |
| `delete_folder` | Destructive | Deletes a folder. The tool's own description instructs the assistant to confirm with you first whether contained QR codes should move to Uncategorized or be deleted along with the folder. |
| `move_qr_codes_to_folder` | Write | Moves multiple QR codes into a folder. |
| `unassign_qr_codes_from_folder` | Write | Removes multiple QR codes from a folder (they become Uncategorized). |
## Forms
| Tool | Type | Description |
| :-------------- | :---------- | :---------------------------------------------------------------------------- |
| `list_forms` | Read-only | Lists all lead-capture forms, optionally filtered by active status. |
| `retrieve_form` | Read-only | Gets detailed information about a specific form, including its configuration. |
| `update_form` | Write | Updates a form's name or active status. |
| `delete_form` | Destructive | Permanently deletes a form. |
## Lead lists
| Tool | Type | Description |
| :------------------- | :---------- | :----------------------------------------------------------------------------------------- |
| `list_lead_lists` | Read-only | Lists all lead lists, optionally filtered by active status. |
| `retrieve_lead_list` | Read-only | Gets detailed information about a specific lead list, including its webhook configuration. |
| `update_lead_list` | Write | Updates a lead list's name or active status. |
| `delete_lead_list` | Destructive | Permanently deletes a lead list. |
## User management
| Tool | Type | Description |
| :----------------- | :---------- | :--------------------------------------------------- |
| `list_users` | Read-only | Lists all users in the account. |
| `get_user` | Read-only | Gets details of a specific user. |
| `add_user` | Write | Invites a new user to the account by email. |
| `remove_user` | Destructive | Removes a user from the account. |
| `list_user_roles` | Read-only | Lists all available user roles that can be assigned. |
| `update_user_role` | Write | Changes the role of an existing user. |
**Destructive tools skip a confirmation dialog by design** — the MCP protocol has no built-in "are you sure?" step; whatever confirmation happens is up to your AI client's own UI conventions. Review what a `delete_*` or `remove_user` tool call is about to do before approving it, the same way you would for any other write action you delegate to an assistant.
## Related
* [MCP overview](/mcp/overview) — what the server is, what it can do at a glance, and its access requirements.
* [MCP setup](/mcp/setup) — connect an AI client to the server that exposes these tools.
* [Management API overview](/api-reference/management-api/overview) — the underlying API these tools call on your behalf.