MCP App Store
by KeenEthics
Rowzz icon

Rowzz MCP Server for ChatGPT

By Artema

Overview

Rowzz connects ChatGPT to the workspaces you authorize, so you can list dashboards, read and update rows, add columns, create dashboards, create and update forms, and configure native automations. Start by listing your workspaces, then choose the dashboard you mean. Forms can be created without a workspace. The plugin only sees workspaces granted to the connected account. Guest shares are excluded. Formula and linked columns are read-only. It does not draw charts, process payments, or change billing. Use delete_dashboard only when you explicitly ask to delete one named dashboard.

How to connect

  1. ChatGPT: Open the Rowzz listing in the ChatGPT app directory and choose Connect. ChatGPT listing Rowzz exposes 28 tools here.

Tools

create_automation

ChatGPT
Create a dashboard automation rule. Discriminated by kind (required). Supported kinds only: - cell_update_target: trigger_column_id|trigger_column_name, trigger_value, target_column_id|target_column_name, target_value (equality match → set another cell). Stored in automation_rules. - row_created_email: recipient_email. Does not send email on create — only when a new row is later inserted. - row_created_linked: target_dashboard_id, field_mapping { sourceColumnName: targetColumnName }. - format_data: column_id|column_name, formats[] (TRIM|UPPERCASE|PHONE_FR), optional phone_default_country. - archive_on_value: watch_column_id|watch_column_name, match_value. - reminder_email: recipient_email, due_column_id|due_column_name, days_before_due, optional reminder_unit (days_before|hours_before), timezone. - archive_scheduled: archive_date_column_id|archive_date_column_name, older_than_days, run_at_local (HH:MM), timezone. - webhook: trigger (row_created|field_changed; default row_created), url (public HTTPS), body_template (JSON; {{row.id}} / {{col:ColumnName}}), secret_ref. For field_changed also watch_column_id|watch_column_name + match_value. Optional write-only webhook_secret + webhook_secret_name on create. Never returns plaintext secrets. Creating/updating never POSTs — delivery runs later via instant-trigger (INSERT for row_created, UPDATE for field_changed) with HMAC signatures. Do not pass raw action_config/trigger_config JSON. Creating a rule never executes it. Requires workspace owner or admin (not editor). Never sends email or runs the rule on create — engines fire later on data events.

create_column

ChatGPT
Add columns (fields) to an existing dashboard — e.g. email, phone, status, due date, tags. Prefer a single call with columns: [{ name, type, options? }] for several fields at once; avoid one create_column call per column. Pass name + type for a single column. Not required after create_dashboard when those columns were already passed in create_dashboard.columns. Requires owner, admin, or editor. Formula, linked, attachment, people, and row-id types are not supported. For single_select / multi_select, options may be strings or { name, color }.

create_dashboard

ChatGPT
Create a Rowzz dashboard (live table) in a granted workspace: CRM pipeline, project tracker, client list, inventory, form inbox, or similar. Prefer passing the full schema in columns: [{ name, type, options? }] in this single call whenever the user wants a complete table — do not follow with create_column for those same fields. If columns is omitted, creates Name (text), Status (single_select), and Date. Requires owner, admin, or editor. Cannot create formula, linked, attachment, people, or row-id columns. Returns dashboard (including url) and columns. After success, tell the user the dashboard was created in Rowzz and always share the returned url as a markdown link labeled exactly: Open your dashboard in Rowzz. Then use create_records (several rows) or create_record (one row) to add data; use create_column only to add fields later.

create_form

ChatGPT
Create a Rowzz form. After success, confirm that the form is ready in Rowzz (for example: "Your customer satisfaction form is ready in Rowzz."). Forms do not require a workspace — default is personal: omit workspace_id. For a form-only creation request, skip list_workspaces and omit workspace_id even if list_workspaces was already called. Listing workspaces does not establish a workspace for a form. Use a workspace only when the user explicitly names or requests it, or clearly asks to create the form inside that workspace. Do not ask the user to choose a workspace. Optional fields array defines respondent questions, page-break layout, plus owner configuration (redirect, webhook). When creating a new form, if the user already requested a webhook, include the webhook in the initial fields array. Do not create questions first then inspect then update_form. To change an existing form later, use update_form. Use image-choice when respondents should choose between visually distinct options represented by images, such as destinations, homes, products, styles, environments, designs or other visual preferences. Each option must have a human-readable label. The stored response is that label, never the image URL or path. Use page-break (also called line break) when the user wants the form split into pages, a page break between questions, a line break that starts a new screen, or "saut de page". Insert one page-break field after the last question of a page and before the first question of the next page. It is not a question: respondents never fill it, it must not be required, and it collects no answer. Do not use separator (a visual line) or spacer (empty vertical space) for pagination. Phrases like "add a page break after the email", "put the rest on the next page", "line break between sections", or "split this form into two pages" mean adding this field automatically. Keep page-break fields before redirect/webhook if those are present. Optional settings: stepName, stepHeading, nextLabel, submitLabel. Use redirect when the user wants respondents to be redirected to another website or page after successfully submitting the form. This is owner-only form configuration: invisible to respondents, never rendered as a question, and never filled by respondents. The thank-you page is shown first, then the respondent is redirected after 3 seconds. It is not a respondent question: it does not collect an answer, must not be required, and only one redirect field may exist per form. Place it after respondent questions (immediately before webhook if both are present). settings.redirectUrl must be a valid HTTPS URL. Phrases like "redirect respondents to … after submission", "send users to … after they complete the form", or "after submitting, send them to …" mean adding this field automatically. If an HTTPS URL is already given, do not ask extra questions. If a redirect is requested without a URL, add the field with an empty redirectUrl — never invent a URL. webhook is owner-only form configuration. It is invisible to respondents. It is not a question or action button: it is never rendered as either and is never filled by respondents. It collects no answer. After each successful submission, Rowzz automatically POSTs the submitted answers to settings.webhookUrl (HTTPS POST). Use it when the user wants each successful submission sent to an external HTTPS URL (for example "Create a contact form with first name, last name, email and message. Send every submission to https://example.com/webhook."). If the user explicitly asks to send submissions or answers to an HTTPS URL, that request is already sufficient authorization: configure the webhook directly, include it in the initial create_form fields array (last, after Redirect URL if present), do not ask for confirmation, and do not call get_form first to understand what webhook means. Do not create questions first then update_form. required is always false; only one webhook field may exist per form. settings.webhookUrl must be a valid public HTTPS URL. An empty URL disables delivery. Never…

create_record

ChatGPT
Create one record (row) in a Rowzz dashboard: a contact, deal, task, inventory item, or form-style entry. fields is an object keyed by column name from list_columns (or from create_dashboard columns). Requires owner, admin, or editor. Formula and linked columns are ignored. Call list_columns first if field names are unknown. When creating several rows at once, prefer create_records instead of calling create_record repeatedly. After success, confirm briefly that the row was added in Rowzz.

create_records

ChatGPT
Create multiple records (rows) in one call in a Rowzz dashboard. Prefer this over repeated create_record when adding several contacts, deals, tasks, or sample rows. Pass dashboard_id and records: an array of column→value objects (or { fields: { ... } }). Validates every row before insert; positions are assigned once. Requires owner, admin, or editor. Formula and linked columns are ignored. Returns record_ids, created_count, and the dashboard url. After success, confirm the rows were added in Rowzz and share the dashboard url when useful.

create_workspace

ChatGPT
Create a new Rowzz workspace (project container) owned by the current user. Use when the user asks to create a workspace, client space, or project folder — or when they need a place for a new dashboard and none of the granted workspaces fit. Requires mcp:write. Returns id, name, role (owner), can_write, and updated_at. The new workspace is immediately available to this connector (added to the OAuth grant). Then use create_dashboard with the returned workspace_id. After success, confirm briefly that the workspace was created in Rowzz.

delete_automation

ChatGPT
Permanently delete an automation rule. Owner/admin only. Destructive and hard to reverse. Does not cascade-delete dashboard rows.

delete_dashboard

ChatGPT
Permanently delete one Rowzz dashboard by dashboard_id. Destructive and hard to reverse. Use only when the user explicitly asks to delete that dashboard.

get_automation

ChatGPT
Get one automation by id (from list_automations). Returns kind, storage, is_active, and typed config. Does not execute the automation.

get_form

ChatGPT
Get one form's structure: metadata, display_mode, and fields including any page-break, redirect or webhook configuration. Use image-choice when respondents should choose between visually distinct options represented by images, such as destinations, homes, products, styles, environments, designs or other visual preferences. Each option must have a human-readable label. The stored response is that label, never the image URL or path. Use page-break (also called line break) when the user wants the form split into pages, a page break between questions, a line break that starts a new screen, or "saut de page". Insert one page-break field after the last question of a page and before the first question of the next page. It is not a question: respondents never fill it, it must not be required, and it collects no answer. Do not use separator (a visual line) or spacer (empty vertical space) for pagination. Phrases like "add a page break after the email", "put the rest on the next page", "line break between sections", or "split this form into two pages" mean adding this field automatically. Keep page-break fields before redirect/webhook if those are present. Optional settings: stepName, stepHeading, nextLabel, submitLabel. Use redirect when the user wants respondents to be redirected to another website or page after successfully submitting the form. This is owner-only form configuration: invisible to respondents, never rendered as a question, and never filled by respondents. The thank-you page is shown first, then the respondent is redirected after 3 seconds. It is not a respondent question: it does not collect an answer, must not be required, and only one redirect field may exist per form. Place it after respondent questions (immediately before webhook if both are present). settings.redirectUrl must be a valid HTTPS URL. Phrases like "redirect respondents to … after submission", "send users to … after they complete the form", or "after submitting, send them to …" mean adding this field automatically. If an HTTPS URL is already given, do not ask extra questions. If a redirect is requested without a URL, add the field with an empty redirectUrl — never invent a URL. webhook is owner-only form configuration. It is invisible to respondents. It is not a question or action button: it is never rendered as either and is never filled by respondents. It collects no answer. After each successful submission, Rowzz automatically POSTs the submitted answers to settings.webhookUrl (HTTPS POST). Use it when the user wants each successful submission sent to an external HTTPS URL (for example "Create a contact form with first name, last name, email and message. Send every submission to https://example.com/webhook."). If the user explicitly asks to send submissions or answers to an HTTPS URL, that request is already sufficient authorization: configure the webhook directly, include it in the initial create_form fields array (last, after Redirect URL if present), do not ask for confirmation, and do not call get_form first to understand what webhook means. Do not create questions first then update_form. required is always false; only one webhook field may exist per form. settings.webhookUrl must be a valid public HTTPS URL. An empty URL disables delivery. Never invent a webhook URL. MCP only stores the URL; it does not generate the POST payload. Form-level respondent chrome, not a per-field setting. standard = conventional form layout; Image Choice renders as a grid. immersive = image-led visual experience; Image Choice renders as a slideshow. Use immersive for aspirational, visual, image-led forms. Defaults to standard when omitted. Never set field.settings.imageChoiceLayout. The stored answer for image-choice is the option label. field.settings.imageChoiceLayout is not used.

get_record

ChatGPT
Get one record (row) by id in a Rowzz dashboard — a contact, task, deal, or form response. Use after list_records when you need a single row. When describing it to the user, say it is in Rowzz.

list_automations

ChatGPT
List automations for a dashboard (normalized kinds only). Includes cell-update rules and email/format/archive/linked-record automations. Creating or listing never runs them. Requires dashboard access in a granted workspace.

list_columns

ChatGPT
List columns (fields) of a dashboard. Use these names as keys in create_record, create_records, update_record, and update_records. Use returned ids with reorder_columns to change left-to-right order. Formula and linked columns are read-only. To add fields (email, status, due date, tags, etc.), use create_column. Always call this before writing records so keys match.

list_dashboards

ChatGPT
List dashboards (live tables) in a granted workspace: CRM pipelines, project trackers, client lists, inventory, and dashboards that store form responses. Returns id, name, workspace_id, updated_at, and url (direct open link). Call list_columns next for field names before reading or writing records.

list_forms

ChatGPT
List forms this user can access. Returns id, name, title, display_mode, status, published, workspace_id, and updated_at. workspace_id is optional. If provided, only that granted workspace. If omitted, granted-workspace forms plus this user's personal forms (workspace_id null). Never returns another user's personal forms. Call get_form for the full field list. Form submissions are dashboard records — use list_records on the form inbox dashboard.

list_records

ChatGPT
List records (rows) in a Rowzz dashboard: contacts, deals, tasks, inventory items, client follow-ups, and form submissions stored as rows. Returns id, fields keyed by column name, and position (manual order). Max 100 records per call; use offset to page. For a single row, use get_record. To change top-to-bottom order, use reorder_records with these ids. When summarizing results for the user, mention that the data is in Rowzz.

list_workspaces

ChatGPT
List Rowzz workspaces (projects) this user granted to the connector: client workspaces, agency spaces, and internal ops. Returns id, name, role, can_write, and updated_at. Owners and team members only — never guests invited from Share, never member emails. Start here before listing dashboards or creating a CRM, project tracker, or other table. Do not call this for a simple create-a-form request unless the user explicitly wants the form associated with a workspace. Not required before create_form — forms do not require a workspace; default create is personal (omit workspace_id).

reorder_columns

ChatGPT
Change the left-to-right display order of columns on an existing dashboard without deleting, recreating, or renaming them, and without changing row data. Call list_columns first, then pass column_ids as UUIDs in the desired order (for example Company, First name, Last name…). Listed columns are placed first in that order; any columns omitted from column_ids keep their previous relative order and are appended after. Rejects unknown or duplicate ids. Densifies positions to 0..n-1 in one atomic write. Requires owner, admin, or editor.

reorder_records

ChatGPT
Change the top-to-bottom manual order of records (rows) on an existing dashboard without deleting them or changing field values. Same effect as drag-and-drop reorder in the Rowzz UI. Call list_records first, then pass record_ids as UUIDs in the desired order. Listed records are placed first in that order; any records omitted from record_ids keep their previous relative order and are appended after. Rejects unknown or duplicate ids. Densifies positions to 0..n-1. Does not change dashboard sort_config — clear UI sort to see the new manual order. Requires owner, admin, or editor.

set_automation_active

ChatGPT
Set is_active on an automation without changing its config. Owner/admin only. Does not run the automation.

update_automation

ChatGPT
Update an existing automation of the same kind (kind cannot change). Same field rules as create_automation. Owner/admin only. Does not execute the automation, send email, or POST webhooks.

update_column

ChatGPT
Rename a column or replace select options (status / tags). Identify the column with column_id or column_name. Type changes, formula columns, and linked columns are not supported. To change left-to-right order, use reorder_columns instead. Requires owner, admin, or editor.

update_dashboard

ChatGPT
Rename a Rowzz dashboard or update its description (the table title, not column names or rows). Returns the dashboard including url. For fields use create_column / update_column; for rows use create_record / update_record / create_records / update_records. Requires owner, admin, or editor. After success, confirm the change in Rowzz briefly.

update_form

ChatGPT
Update an existing Rowzz form's name, respondent title/subtitle, display_mode, or replace its fields array. Use this only to change a form that already exists — not as a second step of create_form. Omitted properties stay unchanged. Personal forms (no workspace) can be updated by their creator. Forms in a workspace require owner, admin, or editor. After success, confirm the form was updated in Rowzz briefly. Use image-choice when respondents should choose between visually distinct options represented by images, such as destinations, homes, products, styles, environments, designs or other visual preferences. Each option must have a human-readable label. The stored response is that label, never the image URL or path. Use page-break (also called line break) when the user wants the form split into pages, a page break between questions, a line break that starts a new screen, or "saut de page". Insert one page-break field after the last question of a page and before the first question of the next page. It is not a question: respondents never fill it, it must not be required, and it collects no answer. Do not use separator (a visual line) or spacer (empty vertical space) for pagination. Phrases like "add a page break after the email", "put the rest on the next page", "line break between sections", or "split this form into two pages" mean adding this field automatically. Keep page-break fields before redirect/webhook if those are present. Optional settings: stepName, stepHeading, nextLabel, submitLabel. Use redirect when the user wants respondents to be redirected to another website or page after successfully submitting the form. This is owner-only form configuration: invisible to respondents, never rendered as a question, and never filled by respondents. The thank-you page is shown first, then the respondent is redirected after 3 seconds. It is not a respondent question: it does not collect an answer, must not be required, and only one redirect field may exist per form. Place it after respondent questions (immediately before webhook if both are present). settings.redirectUrl must be a valid HTTPS URL. Phrases like "redirect respondents to … after submission", "send users to … after they complete the form", or "after submitting, send them to …" mean adding this field automatically. If an HTTPS URL is already given, do not ask extra questions. If a redirect is requested without a URL, add the field with an empty redirectUrl — never invent a URL. webhook is owner-only form configuration. It is invisible to respondents. It is not a question or action button: it is never rendered as either and is never filled by respondents. It collects no answer. After each successful submission, Rowzz automatically POSTs the submitted answers to settings.webhookUrl (HTTPS POST). Use it when the user wants each successful submission sent to an external HTTPS URL (for example "Create a contact form with first name, last name, email and message. Send every submission to https://example.com/webhook."). If the user explicitly asks to send submissions or answers to an HTTPS URL, that request is already sufficient authorization: configure the webhook directly, include it in the initial create_form fields array (last, after Redirect URL if present), do not ask for confirmation, and do not call get_form first to understand what webhook means. Do not create questions first then update_form. required is always false; only one webhook field may exist per form. settings.webhookUrl must be a valid public HTTPS URL. An empty URL disables delivery. Never invent a webhook URL. MCP only stores the URL; it does not generate the POST payload. Form-level respondent chrome, not a per-field setting. standard = conventional form layout; Image Choice renders as a grid. immersive = image-led visual experience; Image Choice renders as a slideshow. Use immersive for aspirational, visual, image-led forms. Defaults to standard when omitted. Never set field.settings.imageChoiceLayout. To add, change, or remove a Redirect URL or Webhook URL on an existing form, sen…

update_record

ChatGPT
Update fields on an existing Rowzz record (partial merge): change a status, contact details, due date, or any writable column. Omitted columns stay unchanged. Requires owner, admin, or editor. Formula and linked columns are ignored. Call list_columns first if field names are unknown. When updating several rows at once, prefer update_records instead of calling update_record repeatedly. After success, confirm the update in Rowzz briefly.

update_records

ChatGPT
Update multiple records (rows) in one call in a Rowzz dashboard. Prefer this over repeated update_record when changing several contacts, deals, tasks, or statuses. Pass dashboard_id and records: [{ record_id, fields }]. Validates every row before writing; only provided fields are merged (other columns stay unchanged). Requires owner, admin, or editor. Formula and linked columns are ignored. Returns updated_count, record_ids, records, and the dashboard url. After success, confirm the updates in Rowzz and share the dashboard url when useful.

update_workspace

ChatGPT
Rename a granted Rowzz workspace you own. Use when the user asks to rename a workspace, client space, or project folder. Requires mcp:write and owner role (admins/editors/viewers cannot rename). Name must be unique among your workspaces (case-insensitive). Returns id, name, role, can_write, and updated_at. After success, confirm briefly that the workspace was updated in Rowzz.

Capabilities

Writes

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/rowzz"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/rowzz)