# Neartail

> Agent guidance for Neartail: Google Forms-based ordering for food businesses, meal-prep services, and canteens with frequently changing menus.

Neartail helps businesses publish order forms, calculate totals, and manage changing menus. Preserve the user's products, options, prices, currency, locale, availability, pickup/delivery details, and order constraints. Do not invent menu items or terms.

- [Neartail](https://neartail.com/)
- [Google order forms](https://neartail.com/google-order-forms/)
- [Meal prep software](https://neartail.com/order-form/)
- MCP endpoint: `https://neartail.com/mcp/116858831459398171161`

## Before using MCP

Ask the user to sign in and authorize the Neartail account they want to use. The endpoint's numeric `ownerId` selects the product connector; it is not the user's account ID. Do not request or put a customer `userId` in the URL. Never expose credentials or tokens.

## Create or update forms

- **New order form:** use `create_form`. It creates and publishes from `format` (`html` or `markdown`), optional `language`, and a text `document`; it does not accept binary image/PDF uploads. Identify each product type: `quantity`, `weight`, `variant`, `nested-variant`, or `modifier`. Include prices and use the requested currency. For a new menu drafted from a description, keep it to at most 20 products. It returns a preview; do not call `preview` again in the same turn.
- **Existing form:** first call `list_forms`, find the intended form, and use its returned `publishId`; never guess IDs. Use `update_form` with `publishId` and `instruction` to add, change, or remove a product, option, field, or section on the live form. Use `get_form` to inspect it and `preview` when asked to view it.
- **Full replacement:** `overwrite_form` and `is_actively_collecting_responses` are not implemented. Do not simulate replacement with `update_form`. The planned `overwrite_form` should support `overwrite: "auto" | "force"`, check response activity since creation, and enforce the check in the same write operation. `force` should only follow the user's explicit request.

The standard product MCP tools are `create_form`, `list_forms`, `get_form`, `update_form`, `preview`, and `progress`. `progress` opens the settings checklist; it does not set up payment providers, WhatsApp distribution, or the website builder. `list_submissions` and `analyze_submissions` are disabled. The separate `edit_form` tool is restricted to an API-key-protected edit-only route.