All servers / Project management / Suppa MCP server
Suppa MCP server
MCP server for the Suppa platform (modern.suppa.me) — Tasks, Docs/Pages, Entities Schema, Forms, Automations, and file attachments, with multi-tenant Google a
Tested by ConnectATDScore 80 out of 100. Tested 2026-11-19 on package version 1.45.1. Package: suppa-mcp-2 · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 18 / 20 | |
| Package safety | 12 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.8 seconds including download)
- Tools offered: 108
- Last published: 2026-11-16
- Weekly downloads (npm): 1,217
- License: MIT · Direct dependencies: 4
Notes
- The package runs install scripts, which execute code when you install it.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
suppa_get_meno parametersGet the current authenticated user's profile (name, position, roles).
suppa_search_tasks11 of 13 parameters describedSearch tasks. Use my=true for your tasks, active=true for open tasks, or search by title substring. Several known tasks: task_ids=[…] reads them in ONE call. fields_json narrows each row to what you need — task_ids + fields_json replaces N suppa_get_task calls.
suppa_count_tasks7 of 7 parameters describedCount tasks matching filters without returning full data.
suppa_get_task1 of 2 parameters describedGet a task by its ID — full details by default, or only fields_json (e.g. ["id", "shortUID"]). For SEVERAL tasks call suppa_search_tasks(task_ids=[…], fields_json=…) once, not this per task. The description is htmlDescription; plainDescription is included only when it differs from that HTML with the tags removed.
suppa_create_task9 of 10 parameters describedCreate a new task. Deadline accepts: 'today', 'tomorrow', '+3d', '+2h', '+30m', '+1w', or ISO datetime. HTML: plain text is auto-wrapped in <p>…</p>; to pass raw HTML, start the string with <.
suppa_update_task9 of 11 parameters describedUpdate fields on an existing task. Only provided fields are changed. Any list-valued field written here is REPLACED wholesale — this tool has no merge option. To ADD to / REMOVE from a task's list field, use suppa_update_record("Tasks", ...) with merge_json / unmerge_json. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_task1 of 2 parameters describedSoft-delete a task. SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record('Tasks', task_id); it drops out of normal reads, so find it again with suppa_search_records('Tasks', deleted_scope='deleted'). Not the platform's permanent delete (rows leave the table and cannot be restored), which this server does not expose. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_move_task2 of 3 parameters describedMove a task to a different workflow stage. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_close_task1 of 2 parameters describedClose a task by moving it to the workflow's completed stage. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_add_comment2 of 3 parameters describedAdd a comment to a task. Supports HTML — plain text is auto-wrapped in <p>…</p>, so start the string with < to pass raw markup. mention_ids: comma-separated 'userId:Name' pairs for @mentions.
suppa_get_comments0 of 2 parameters describedGet the latest N comments on a task, in chronological (oldest-first) order.
suppa_attach_file1 of 2 parameters describedUpload a local file and attach it to a task.
suppa_list_workflows0 of 1 parameter describedList all workflows with their stages in order. Optionally filter by name. A stage's status is the enum value ('active', 'completed', …).
suppa_list_stages1 of 1 parameter describedList all stages in a specific workflow, in order. status is the enum value ('active', 'completed', …).
suppa_list_task_typesno parametersList all available task types.
suppa_search_users1 of 2 parameters describedSearch users by name.
suppa_list_docs2 of 3 parameters describedList documents, optionally filtering by title. fields_json narrows each row.
suppa_get_doc1 of 2 parameters describedGet a document by ID including its page tree, or only fields_json.
suppa_create_doc0 of 2 parameters describedCreate a new document.
suppa_update_doc1 of 4 parameters describedUpdate a document's title or visibility. Any list-valued field written here is REPLACED wholesale — this tool has no merge option; use suppa_update_record("Docs", ...) with merge_json to add. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_doc1 of 2 parameters describedSoft-delete a document (and its pages). SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record('Docs', doc_id); it drops out of normal reads, so find it again with suppa_search_records('Docs', deleted_scope='deleted'). Not the platform's permanent delete (rows leave the table and cannot be restored), which this server does not expose. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_list_pages1 of 3 parameters describedList all pages in a document. fields_json narrows each row.
suppa_get_page1 of 2 parameters describedGet a page's metadata, or only fields_json.
suppa_create_page2 of 5 parameters describedCreate a new page in a document.
suppa_update_page1 of 6 parameters describedUpdate a page's metadata. Any list-valued field written here is REPLACED wholesale — this tool has no merge option; use suppa_update_record("Pages", ...) with merge_json to add. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_page1 of 2 parameters describedSoft-delete a page. The platform refuses to delete a document's LAST page (HTTP 400) — delete the whole doc instead (suppa_delete_doc). SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record('Pages', page_id); it drops out of normal reads, so find it again with suppa_search_records('Pages', deleted_scope='deleted'). Not the platform's permanent delete (rows leave the table and cannot be restored), which this server does not expose. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_get_blocks0 of 1 parameter describedGet all content blocks on a page in order (raw JSON with IDs and properties).
suppa_read_page0 of 1 parameter describedRead a page as human-readable markdown-like text.
suppa_create_blocks1 of 2 parameters describedCreate content blocks on a page (appended at end). blocks_json: JSON array of {type, title} objects. Types: text, head1, head2, head3, bulletList, numberedList, checkList, quote, callout, divider, code, table, toggle.
suppa_insert_block3 of 4 parameters describedInsert block(s) at a specific position. Provide after_id OR before_id as anchor. blocks_json: JSON array of {type, title} objects.
suppa_update_block3 of 4 parameters describedUpdate a block's content. Provide title (text/HTML) or full properties_json. Plain text is auto-wrapped in <p>…</p>; start the string with < for raw HTML. properties_json REPLACES the block's properties wholesale (as does any list-valued field) — this tool has no merge option; read the current properties with suppa_get_blocks first and re-send them in full. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_block1 of 2 parameters describedSoft-delete a content block. SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record('PageBlocks', block_id); it drops out of normal reads, so find it again with suppa_search_records('PageBlocks', deleted_scope='deleted'). Not the platform's permanent delete (rows leave the table and cannot be restored), which this server does not expose. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_reorder_blocks4 of 5 parameters describedReorder blocks on a page. block_ids: comma-separated IDs to move. Provide after_id or before_id as anchor. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_list_entities2 of 2 parameters describedList all entities (database tables) on the platform, tabular parts too (type 'tabular-part', with their owner). Optionally filter by name.
suppa_describe_entity2 of 2 parameters describedGet the schema of an entity — all fields, types, relations, and constraints. Compact by default: a field lists only what departs from the platform defaults, and the result's _legend says exactly what an absent key means — a quarter of the raw size. full=true returns the platform's raw schema.
suppa_list_tabular_parts1 of 1 parameter describedList an entity's tabular parts (owned child sub-tables / "таблична частина"). Each result has type='tabular-part' and a relationEntity pointing back to the parent.
suppa_search_records8 of 10 parameters describedSearch records of any entity. filters_json: [{field, value, comparator}]. fields_json: {field: true}. Comparators: =, !=, <, >, <=, >=, like, not like, in, not in, between, not between, is null, is not null. 'like' is a case-insensitive CONTAINS — send the bare text; the platform adds % and escapes yours, so 'LMS.%' matches nothing. 'in' takes a JSON array, 'between' [from, to] or a period like "$this_month". Field paths may be dotted — "stage.status.value", "owner.id" — and the value "$current-user" resolves to the signed-in user's id. match_any=true combines filters with OR instead of AND. NESTED GROUPS: a filters_json entry may be {"operator": "and"|"or", "filters": [...]} (nested to any depth), so (status=open AND owner=me) OR priority=high is ONE call. An EMPTY result (or a 400) is auto-diagnosed with select/validate: if the query references a field that does not exist you get "validation" naming it, not silence. Returns {records, returned, has_more, next_offset, deleted_scope} — page with offset until has_more is false. Enum fields read back as objects {value, title, id} — project them as {"myEnum": {"value": true}} and read .value, not as a bare string. SOFT-DELETED ROWS: deleted_scope='deleted' returns ONLY records that suppa_delete_record removed — that is how you find the id to hand to suppa_restore_record. 'all' returns live and removed together (removed ones carry a non-null deletedAt; project it to tell them apart).
suppa_validate_select5 of 5 parameters describedCheck a search/select payload against the entity WITHOUT running it — POST /core/data/:entity/select/validate. Use it when a search returns nothing: a typo'd field name gives an EMPTY result, not an error, and this turns that into {"valid": false, "invalidFields": [{path, location, kind, reason}]} naming the reference that does not resolve. suppa_search_records already runs this automatically on an empty result or a 400 — call it directly to pre-flight an expensive query.
suppa_query3 of 3 parameters describedRun ONE read-only SuppaSQL statement — POST /core/data/query, the endpoint the builder's SQL charts and tables use. Check a chart/table SQL source with it before writing the form: an incomplete one shows demo data, a wrong one fails at runtime. SELECT / WITH only, one statement, no comments (SuppaSQL has none); anything else is refused and nothing is sent. Runs with the caller's read permissions; deleted rows are excluded. A missing LIMIT is added and a bigger literal one clamped, so at most `limit` rows come back, with `truncated` and `columns` — the keys of every row, nested ones as dot paths (owner.firstName): a TABLE column's key. `chart_note` says when the same text fails as a CHART source: a chart needs LIMIT 10000 or less (it sends LIMIT 10001, refused with query.row_limit). A CHART's sqlCategoryColumn / sqlValueColumns[].key is a field's last segment (firstName) or the alias of a COMPUTED item (COUNT, CASE, TO_CHAR…); never alias a plain field in a chart query — the chart reads it by its path and shows nothing. Writing one: suppa_sql_kb (check a draft offline first); slow, or failing for some role: suppa_query_analyze, once.
suppa_sql_kb5 of 5 parameters describedThe SuppaSQL skill (skills/writing-suppa-sql): write, check and tune a query for suppa_query, a chart / table SQL source or an application. Offline; touches no tenant. rules the cycle, request discipline, the five rules cheatsheet goal → query mistakes common mistakes and their fix check a draft's TEXT: what the platform refuses ($now, CURRENT_DATE, LEFT JOIN, LIMIT > 10000…) and the measured slow shapes it shows (P1–P14) ref topic language|unsupported|performance|practices|analytics|actions|http-api, section = a heading (e.g. P14); a long topic without one lists its sections
suppa_query_analyze5 of 5 parameters describedONE analysis of a FINAL SuppaSQL query on the active tenant: the plan for you and for every role (× the full-rights cost, the access rules' share, the roles it FAILS for), the size and indexes of the tables it reads, and the actions to PROPOSE — create / rebuild / drop an index, rewrite the query; none is applied. Plan only: nothing runs unless run_query=true. Needs the owner group or DATABASE_ANALYTICS.VIEW. Up to 13 requests; /query-analyze allows 10 calls a minute per user — iterate on drafts with suppa_sql_kb mode='check', analyse the final one once. On a rate limit it stops and reports what it has: do not repeat it.
suppa_get_record4 of 5 parameters describedGet a single record of any entity by id. fields_json: {field: true} projection — request only the fields you need (relations as nested objects, e.g. {"owner": {"id": true, "fullName": true}}). A soft-deleted record is NOT returned by default: read it with deleted_scope='deleted' (or 'all') to inspect it before calling suppa_restore_record.
suppa_create_entity5 of 6 parameters describedCreate a new entity (database table). By default also creates the display-title field so records have a label and titleFieldName resolves to a real field, and sets that field as the entity's representative (what the UI shows for a record). NOT for repeating child rows that belong to one parent record (invoice line-items, "X by category", per-period breakdowns) — those must be a tabular part: use suppa_create_tabular_part instead, or they end up as a stray separate entity.
suppa_update_entity_options3 of 3 parameters describedTurn the platform's per-entity FEATURES on or off (POST /core/builder/<entity>/update-options) — a narrower alternative to editing the entity that touches only options. This is the only way to reach comments, reactions, hierarchy, folders, change history, browsing history, global search, time tracking, favorites, pinned, approvals, checklists, recurrence, reminders, notification mutes and customFields (per-context extra columns — see suppa_add_custom_field) from here; send only the ones you are changing. NOT A FREE TOGGLE: enabling an option CREATES the side table that backs it, and recurrence / reminders / notificationMutes / timeTracking / pinned also refresh the cache of the corresponding system entity. It is a schema change. RESTRICTIONS: on an entity the tenant does not own (initiator 'system' or 'application') only options.stateHistory and options.externalSource may change — the platform answers 403 to the rest, so this server refuses the call first. A system-GENERATED entity (a reserved suffix: Comments, Folders, CustomFields…) refuses comments, customFields and six more — refused here too. The platform answers with the APPLIED options, which may be a subset of the request — anything missing is called out in the result. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_create_tabular_part6 of 7 parameters describedCreate a tabular part (ТЧ / "таблична частина") — an owned child sub-table of parent_entity, edited inline in the parent (like 1C invoice line-items). Use this — NOT suppa_create_entity — whenever a child holds repeating rows that belong to ONE parent record. The platform marks it type='tabular-part', auto-adds a system `owner` (many-to-one → parent) field, and nests it under the parent. Add data fields afterwards with suppa_add_field, then verify with suppa_list_tabular_parts(parent_entity).
suppa_add_field15 of 17 parameters describedAdd a field to an entity. field_type: a real Suppa 2.0 type — text, numeric, integer, serial, boolean, timestamp, json, uuid, multi-language, bytea, tsvector, multi-type, icon, enum, multi-enum, file, multi-file, many-to-one, many-to-many, many-to-many-backref. There is NO date/datetime/richtext/email/url/phone type — use timestamp (+sub_type='date' for date-only) and multi-language for localized text. 'relation' is accepted as an alias for many-to-one. Provide relation_entity for relations, enum_name for enums. The sub_type matrix and the field options (searchable + searchPriority is the one usually worth setting) live on the sub_type and options_json parameters — read them; enum/multi-enum take no sub_type (the platform sets it). Constraints: max_length/min_length (text), decimal_places / min_value / max_value / only_positive (numeric). Options can be changed later with suppa_update_field; a plain TYPE with suppa_change_field_type. required=true makes the column NOT NULL. Where a defaultValue APPLIES it is also required, and the call is refused before any request if missing — no default is ever invented for you. defaultValue does NOT apply to relations, enums, files or unique fields (builder.txt:43): there it is dropped, and the result says so under not_applicable. notNull itself does not apply to many-to-many / multi-enum, nor unique to relations and enums (builder.txt:41-42) — those are withheld and reported the same way. 'one-to-many' is REFUSED: an owned child collection is a TABULAR PART (suppa_create_tabular_part, which auto-creates the child's 'owner' and the parent link); never hand-build parent.one-to-many + child.owner. Use 'many-to-many' for a shared lookup referenced by many records.
suppa_update_field14 of 14 parameters describedEdit an EXISTING field of an entity (POST /core/builder/<entity>/<field>/update-field). Send only what changes — everything is optional. Use it to fix a label, rename a field, flip required/unique, set a default, or change the field OPTIONS: searchable / searchPriority (1-4) / readOnly / canGroup / canSort / showInTable / editFromTable / canFilter. A new field already has the defaults — visible, sortable, groupable, filterable, editable, not read-only, NOT searchable — so the usual reason to come here is searchable, or turning one OFF. WHAT THE PLATFORM DOES NOT ALLOW (refused here BEFORE any request, so a rejected call changes nothing): - The TYPE (and a timestamp's date/time/timestamp) is NOT changed here — use suppa_change_field_type, which shows the platform's conversion plan first. - Of the other subtypes only encryption toggles: encrypt=true sets 'encrypted', encrypt=false clears it. - 'encrypted' is only allowed on a TEXT field, and it forces searchable, canFilter, canSort and canGroup off (plus unique, max_length, min_length, mask), so it cannot be combined with them in one call. Encrypting rewrites the existing rows. - A field the tenant does not own (initiator 'system' or 'application') takes only a title and options.trackStateHistory (an application's also a default — until the app's next re-sync); the platform answers 403 to the rest. Removing a CORE field is still UI-only — this server has no remove-field call for one. A CUSTOM field is different: suppa_remove_custom_field parks it reversibly. This tool edits a custom field too — pass entity_name='<Entity>CustomFields'. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_change_field_type9 of 9 parameters describedChange a field's TYPE, converting every row (POST /core/builder/<entity>/<field>/ update-field, planned first by /change-plan). Converts only plain types: text, numeric, integer, boolean, timestamp, json, icon, uuid, multi-language — never a relation, enum, file, serial or multi-type (add a new field instead). sub_type date|time|timestamp on a timestamp field is a type change too. Without confirm it is a DRY RUN: the platform's own plan comes back — decision (ready / needs-input / refused), rows, and every conflict with sample values and what it does. A refused plan is never sent. A LOSS is sent only when accepted by name: accept_locale_loss (multi-language → text keeps one language per row; json keeps all), accept_stash_restore (changing BACK to an earlier type restores the column saved then — later edits reverted, newer rows NULL). A default the new type cannot hold needs default_value or drop_default in the same call. The column converts under an ACCESS EXCLUSIVE lock, and even the dry run holds that lock while it scans; tables over 500,000 rows are refused. Show the plan to the user first. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_add_enum_values4 of 4 parameters describedAdd values to an enum (lookup table). values: comma-separated 'code' or 'code:Label' — a value with no label is stored with the code as its label. WHICH GROUP THEY JOIN: an enum field's subType IS the name of its group of values, and that is the only binding the platform enforces. For a field that already exists pass entity_name + field_name and the name is READ from it — never rebuild it from 'Entity.field', which is a convention, not a rule. Use enum_name alone only for a NEW group, before its field exists; then pass the same enum_name to suppa_add_field.
suppa_resolve_custom_fields4 of 4 parameters describedWhich custom fields are live for a record (or a context), and what it holds. Custom fields are extra columns a tenant adds per CONTEXT — a set keyed on a field such as project — so the answer differs from record to record. This is the only CURRENT view: /schema lags up to a minute behind add/remove. Values live on the OWNER under the reserved 'customFields' key — read them with fields_json '{"customFields": {"budget": true}}', write them with suppa_update_record fields_json '{"customFields": {"budget": 600}}'.
suppa_add_custom_field8 of 14 parameters describedCreate a CUSTOM field on an entity, live in ONE context. Needs context_field + context_value (the set for that context is created if it has none) or set_ids — a custom field belonging to neither is refused. The entity needs options.customFields on (suppa_update_entity_options). Types, sub_type and options are suppa_add_field's. required=true marks it mandatory in THIS context (its CustomFieldSetFields row), binding when the values row is written; column-level notNull is a different thing this build cannot create. Enum values come after: suppa_add_enum_values(entity_name='<Entity>CustomFields', field_name='<field>') — both, or it cannot read the group off the field.
suppa_remove_custom_field3 of 3 parameters describedRemove custom fields from an entity — reversibly. The metadata is soft-deleted and the column is RENAMED to <name>_<timestamp>, not dropped, so the values survive and suppa_restore_custom_field brings both back. Only CUSTOM fields — core and platform columns are refused. APPROVAL GATE: without confirm=true this returns a confirmation request and removes nothing.
suppa_restore_custom_field3 of 3 parameters describedUndo suppa_remove_custom_field: the field and the values behind it come back. APPROVAL GATE: without confirm=true this returns a confirmation request and restores nothing.
suppa_add_custom_fields_batch5 of 5 parameters describedCreate MANY custom fields in ONE atomic call - one bad entry creates NOTHING. Context rules are suppa_add_custom_field's: context_field + context_value (that set must already exist) or set_ids. Every entry passes the same guards as a single add.
suppa_apply_custom_fields2 of 2 parameters describedCustom fields DECLARED IN A REPO FILE, applied to a tenant — the file is the source of truth. On @suppa/sdk 1.38.0+ prefer @CustomFields in the entity class (SKILL.md rule 22). declaration: {"entity","context_field","fields":[{"name","type","title","contexts":["PL"]}]}. Idempotent — a second run answers already_converged. Creates per context in ONE atomic batch, then links existing fields into their other contexts. NEVER deletes (a dropped field → not_declared), never re-creates a REMOVED one (→ parked: restore it) and never changes a type (type_drift — that is a data migration). Dry run by default; confirm=true applies.
suppa_link_custom_field8 of 8 parameters describedPut EXISTING custom fields into another context, take them out of one, or set required. A field joins a context through a row, so ONE field can be live in several contexts at once, keeping one column and one set of values. required is the only per-context flag offered: the platform enforces it and enforces neither readOnly nor defaultValue. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_set_title_field3 of 3 parameters describedSet an entity's display-title (representative) field; creates it if missing. This CHANGES what every existing record of the entity displays as its label, so it is confirm-gated like any other edit to live data. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_list_field_typesno parametersList all available field types for entity/form creation.
suppa_create_record2 of 2 parameters describedCreate a record in any entity. fields_json: JSON object of field values. BATCH: pass a JSON ARRAY of record objects to create many in ONE request (e.g. [{"title": "A"}, {"title": "B"}]) — do not loop this tool. The batch returns {created, requested, entity, records} and is validated as a unit: if any record is malformed, nothing is inserted. Write relations as {"id": N} and enum fields as {"id": <enumValueId>} — a bare number/string returns HTTP 201 but silently stores null. A Forms widget with a stale compiledRender is refused.
suppa_update_record5 of 6 parameters describedUpdate a record in any entity. fields_json: JSON object of fields to change. Write relations as {"id": N} and enum fields as {"id": <enumValueId>} — a bare number/string returns HTTP 201 but silently stores null. LIST FIELDS ARE REPLACED, NOT APPENDED: fields_json={"watchers": [{"id": 15}]} makes 15 the ONLY watcher — every other watcher is dropped. To ADD the listed items instead, pass merge_json=["watchers"]; to REMOVE only the listed items, pass unmerge_json=["watchers"]. A form's draft is suppa_write_form_draft; a Forms widget with a stale compiledRender is refused. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_record2 of 3 parameters describedSoft-delete a record (instance) from any entity. SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record; it disappears from normal reads, so find it again with suppa_search_records(deleted_scope='deleted'). Not the platform's permanent delete (/core/data/<entity>/delete — rows leave the table and cannot be restored), which this server does not expose; every delete tool here is the reversible one. Removes a single instance, not the entity/schema. Entities and fields are created with suppa_create_entity / suppa_add_field and edited with suppa_update_field (its type with suppa_change_field_type); REMOVING a core field is UI-only. Custom fields have their own reversible pair: suppa_remove_custom_field / suppa_restore_custom_field. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_restore_record2 of 3 parameters describedUNDO a soft delete: bring a removed record of any entity back by clearing deletedAt. This is the counterpart of suppa_delete_record (and of every other delete tool here — they all only set deletedAt), so a deletion the user regrets is recoverable; nothing was purged. FINDING THE ID: a removed record is invisible to a normal read. List the candidates with suppa_search_records(entity_name, deleted_scope='deleted') — project deletedAt (fields_json {"id": true, "deletedAt": true, ...}) to see when each was removed — or read one you already know by id with suppa_get_record(..., deleted_scope='deleted'). Only soft-deleted rows are touched: the platform scopes the restore to deletedAt IS NOT NULL, so calling this on a live record changes nothing and returns restored=false. A record removed with the platform's PERMANENT delete cannot be restored — but this server never issues that call. ALSO WRITES to <Entity>CustomFields: the platform's own restore leaves the record's custom-values row deleted, so this restores that too — which is why calling it on an ALREADY-ACTIVE record is not a no-op. APPROVAL GATE: without confirm=true this returns a confirmation request and restores nothing.
suppa_copy_record5 of 5 parameters describedDuplicate an existing record of any entity, server-side. fields_json holds the values that must DIFFER on the copy — they are applied on top of the copied ones (pass {} to copy as-is). Write relations/enums as {"id": N}. copy_files=true duplicates the source record's ATTACHMENTS onto the copy. This is the only way to do that here: suppa_attach_file_to_record uploads from a local path, which you do not have for a file that lives on the platform. copy_related_entities=true also copies the records related to this one — it multiplies data, so leave it false unless the user asked for a deep copy. Creates a NEW record and never changes the source, so no approval gate.
suppa_list_record_files4 of 4 parameters describedList the files attached to one record of any entity. Returns file_ids ready for suppa_download_file / suppa_download_files_zip, plus fileName, filePath, pdfPath, previewPath, size, mimeType and type for each attachment. A row that carries no id can be looked up on the 'Files' entity with suppa_search_records. An empty list can also mean the entity has no file field at all; check it with suppa_describe_entity.
suppa_download_file4 of 4 parameters describedDownload one attached file to a local path. file_id is the id of the row in the 'Files' entity — from suppa_search_records on 'Files', or from what suppa_attach_file_to_record returned. file_type picks the variant: the original ('file'), its image preview ('preview'), or the generated PDF ('pdf'). dest_path must be ABSOLUTE. Point it at a directory to keep the platform's own file name. An existing file is never overwritten unless overwrite=true — the bytes are discarded instead.
suppa_download_files_zip5 of 5 parameters describedDownload several attachments at once as one ZIP archive. Two ways to choose what goes in, and exactly one of them at a time: file_ids — those specific files entity_name + record_ids — EVERY file attached to those records file_ids are ids from the 'Files' entity, as returned by suppa_list_record_files or suppa_attach_file_to_record. dest_path must be ABSOLUTE; point it at a directory and the archive is named download.zip, since this endpoint sends no filename of its own. Nothing is overwritten unless overwrite=true.
suppa_attach_file_to_record3 of 4 parameters describedAttach a local file to a record (instance) of any entity. Auto-detects the entity's file/attachment field from its schema; pass field_name only when the entity has more than one file field. Provide the absolute file_path. A record can carry files at all only if its entity has a 'file' or 'multi-file' field — check with suppa_describe_entity and add one with suppa_add_field if it has none. KEEP THE RETURNED file_ids: they are the only handle that gets the bytes back (suppa_download_file / suppa_download_files_zip). suppa_list_record_files returns them too, for files already attached. To put a record's attachments on a copy, use suppa_copy_record(copy_files=true) — a file already on the platform has no local path to re-upload from.
suppa_list_automations2 of 4 parameters describedList automation workflows (AutomationWorkflow). NOTE: these are platform automations, distinct from Task workflows (suppa_list_workflows).
suppa_get_automation1 of 1 parameter describedGet one automation workflow as a normalized graph: nodes + edges, settings, and the published snapshot. nodes [{id,type,name,config,position,…other keys}], edges [{from,fromHandle,to,toIndex}], under "published". Distinct from Task workflows. Design / reshape: skill building-suppa-automations (suppa_health_check names its folder).
suppa_list_automation_runs2 of 4 parameters describedList runs (executions) of one automation, newest first.
suppa_get_automation_run0 of 1 parameter describedGet one automation run with its per-node `steps` (nodeId/status/timing/ output/error) and `triggerPayload` (the run input).
suppa_list_automation_node_types1 of 1 parameter describedList automation node types from the authoritative catalog endpoint ({type, label, category, description, requiredParams, paramCount, usedCount}); falls back to deriving the catalog from live graphs on builds without it.
suppa_get_automation_node_schema1 of 1 parameter describedSchema for one automation node type from the authoritative catalog (params name/type/required/description + credentials), enriched with sample values and input/output handles from live graphs; falls back to a graph- derived schema on builds without the endpoint or for an unknown type.
suppa_search_entities1 of 2 parameters describedFuzzy-search the entity registry by name/title and return each match's canonical name, label, description, and recordCount. recordCount costs one capped id-page per match — keep `query` specific. Abstract/unqueryable entities (e.g. BaseEntity) return recordCount=null + recordCountError rather than failing the search.
suppa_create_automation4 of 4 parameters describedCreate a DRAFT automation workflow (AutomationWorkflow). Writes only draft columns (name/nodes/connections/settings) with isActive=false — it is NOT live until published (suppa_publish_automation). Runs pre-flight validation (at least one trigger — triggerEntity, triggerManual, triggerWebhook, triggerSchedule, formSubmission or any the live catalog lists; several are allowed, in any position — unique node ids, connections reference known nodes, DAG, trigger and suppa node params); on failure nothing is written and the errors are returned.
suppa_update_automation6 of 6 parameters describedPartial update of a DRAFT automation (read-modify-write). Only supplied fields change; settings is merged over the stored value (pinData and untouched keys preserved); nodes/connections are whole-document replaces. Runs pre-flight validation on the resulting graph. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_delete_automation2 of 2 parameters describedSoft-delete an automation workflow. SOFT DELETE: sets deletedAt — the row remains and the delete is reversible with suppa_restore_record('AutomationWorkflow', automation_id). It disappears from normal reads and STOPS RUNNING, so treat it as gone for further work; find it again with suppa_search_records('AutomationWorkflow', deleted_scope='deleted'). Not the platform's permanent delete (rows leave the table and cannot be restored), which this server does not expose. APPROVAL GATE: without confirm=true this returns a confirmation request and deletes nothing.
suppa_publish_automation2 of 2 parameters describedPublish (activate) an automation — promotes the draft to the live snapshot via the automation-service. Requires the automation-service deployed on the tenant; if absent the call 404s and the error is returned. A typed 400 returns {published:false, errors, warnings, message}. APPROVAL GATE: without confirm=true nothing changes; the answer carries the draft's pre-flight (E1–E21 run on publish).
suppa_unpublish_automation2 of 2 parameters describedUnpublish (deactivate) an automation — clears the live snapshot via the automation-service. Requires the automation-service deployed (else 404, returned as an error). APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_migrate_entities_from_v110 of 10 parameters describedMigrate entity schemas (tables + fields + enums) from a Suppa 1.0 backend into this Suppa 2.0 platform. Reads entities and their fields from Suppa 1.0 (configured via SUPPA_V1_API_KEY / SUPPA_V1_ACCESS_TOKEN and SUPPA_V1_BASE_URL) and recreates them here. Relations are created in a second pass. Recommended workflow: 1. Dry run + export: dry_run=true, output_file="migration_plan.json" → review/edit the file. 2. Execute the file: dry_run=false, plan_file="migration_plan.json". dry_run: when True (default), returns the migration plan without writing anything to 2.0. entity_names: comma-separated 1.0 entity names/aliases to migrate (empty = all). include_builtin: include builtin/system entities (default: custom only). skip_relations: skip relation/foreign-key fields. output_file: write the plan as JSON to this path (for review/editing). plan_file: load the plan from this JSON file instead of reading from Suppa 1.0. check_relation_instances: probe Suppa 1.0 to see whether each relation candidate is actually populated in the source; annotates the plan with v1_populated + create. skip_empty_relations: exclude relation fields that have no populated instances in v1 (create:false) — deciding the field isn't needed. Probe errors keep the field.
suppa_read_v1_entities1 of 1 parameter describedList entities on the configured Suppa 1.0 backend (read-only).
suppa_read_v1_entity_props3 of 3 parameters describedDescribe ALL fields of one Suppa 1.0 entity (read-only). Returns a clean, type-aware summary per field (type, sub_type, relation target, constraints, required/readonly/visible flags, title), resolves custom-enum values inline, and — for tabular parts (Табличні частини, i.e. one-to-many relations into custom child entities) — expands the child entity's own fields. Also returns `tabular_parts` (child-table field names) and `relations` (every relation + its target).
suppa_read_v1_enum1 of 1 parameter describedRead a Suppa 1.0 custom-enum's values (read-only).
suppa_create_workspace7 of 8 parameters describedCreate a Workspace (and, by default, a NavigationMenu item linking to it). Build the sidebar menuPanel form with suppa_create_form first, then pass its id as sidebar_form_id. Relations are written as {id} for you.
suppa_add_menu_item7 of 9 parameters describedCreate a NavigationMenu item (sidebar/menu entry). Provide href or entity.
suppa_list_forms2 of 3 parameters describedList forms. Optionally filter by entity name or form type (e.g. 'elementForm').
suppa_get_form2 of 3 parameters describedGet a form by ID. 2.x: the builder's read — schema, settings, variables, localizations, the Code Form's files (`code`), `revision`; saved to a file, the gate's baseline and a suppa_write_form_draft draft (its code: suppa_form_code). Suppa 1.0: the row's `data`.
suppa_create_form8 of 11 parameters describedCreate a new form. Provide schema_json (array of fields or {formShema}), or set generate_from_entity=true WITH entity_name to auto-build fields from the entity (without entity_name it is refused, rather than creating an empty form). Form names are UNIQUE platform-wide — a duplicate name fails; pick a distinct one. SUPPA 1.0 FORM. This writes data.formShema and the v1 field types. A Suppa 2.0 (entity-builder) form is a different product — the `schema` column, 57 types: use suppa_form_kb and suppa_validate_form_schema.
suppa_update_form4 of 6 parameters describedUpdate a form's name, schema (data.formShema), settings, or module code. Form names are UNIQUE platform-wide — renaming to an existing name fails. APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_generate_form_schema3 of 3 parameters describedAuto-generate a form schema (formShema + formSettings) from an entity's fields. Returns JSON usable as create_form's schema_json. 'fields' limits/orders included fields. SUPPA 1.0 FORM — formShema and the v1 field types. For a 2.0 entity-builder form use suppa_form_kb (mode='template') instead.
suppa_add_field_to_form4 of 7 parameters describedAppend a field to a form's schema. Types: text, textarea, richtext, date, select, userSelect, files, toogle, etc. This modifies an existing form (data.formShema). APPROVAL GATE: without confirm=true this returns a confirmation request and changes nothing.
suppa_list_form_field_typesno parametersList the available form field types.
suppa_login1 of 1 parameter describedSign in to a Suppa tenant via Google — call this whenever the user is not authenticated (no need to ask them for a key; there isn't one). Opens a Google sign-in page in the user's default browser (a local page at http://localhost:8080) and BLOCKS until they pick an account, then exchanges the Google identity for Suppa tokens and stores them in the OS keychain (auto-refreshed afterwards — a one-time step per tenant). Tell the user a sign-in page has opened and to finish there; if the browser didn't open, the returned JSON includes a URL to open manually. Returns {"status":"ok", ...} on success, or {"error": ...} (e.g. the localhost origin isn't whitelisted in the Google OAuth client, or the account isn't a member of that tenant). A successful login also makes that tenant the ACTIVE one for every later call. After a successful login, retry whatever the user originally asked for. tenant: alias / host / URL (default: the active tenant).
suppa_use_tenant1 of 1 parameter describedSwitch the active Suppa tenant for this session. Accepts a known alias ('testing'), a host ('testing.modern.me'), or a full URL. New tenants are remembered. Subsequent tool calls hit the selected tenant.
suppa_list_tenantsno parametersList known Suppa tenants — which one is active and whether each is authenticated.
suppa_form_kb3 of 3 parameters describedThe Suppa 2.0 (entity-builder) FORM knowledge base. Offline; touches no tenant. components the 56 element types (start here) api prop table for the types you name base props every element supports note one type's BEHAVIOUR ref layout|binding|tables|charts|custom-chart|conditions|styling|publishing| choosing-elements template a starting draft by name rules the nine rules and what blocks kit the look of every record card, create form, window: the card kit's patterns (topic='p_block,…' = their elements); rules: ref card-kit note dynamicComponent = the widget contract (sandbox, formAPI, styles, translations) No mode returns all 57 prop tables: they are ~14,200 tokens stripped, and not carrying them is what this skill is for. Full skill: skills/suppa-form-v2/SKILL.md.
suppa_validate_form_schema4 of 4 parameters describedRun the gate over a Suppa 2.0 form draft BEFORE writing it. Offline; touches no tenant. The platform form builder's own STRUCTURAL checker: 37 error codes — unknown types and props, bindings that resolve to nothing, malformed geometry and containment, bad option values, collisions. It does NOT carry the authoring lints (an unbound select, an empty container, a second Save): those live in the source agent's uxVerify pass, which is not vendored here. Passing is structural, not editorial. It also refuses chart SQL the runtime refuses or reads empty, warns on low contrast and heightless charts, and compiles every widget's compiledRender as the builder does. FOR AN EDIT PASS baseline_path, the form as it exists on the tenant: the component manifest lags the live platform, so without it the tenant's own props read as errors. Measured on every live form of a dev tenant: 59 of 96 cold, 73 as an edit. passed=false means fix and re-run; passed=true WITH warnings is not a clean form.
suppa_write_form_draft5 of 5 parameters describedSave a Suppa 2.0 form as a DRAFT on the tenant, through the builder's own save (PUT /core/forms/:id/schema). It never publishes: what others see stays the published version; a published form reads `editing`. The save appears in the builder's History. The gate runs first, judged against the live form: what the form already has does not block, a refusal or an error the draft adds and nothing is written. It compiles each changed widget's compiledRender from its template; a hand-written one is never saved. The row is read first and a read that does not clearly succeed ABORTS — merging over a failed read is how a saved mobile layout and code-form vanish on a call returning 200. Writes schema and settings; `variables` only when the draft lists some — the list is the FULL state (an omitted variable is deleted), so an empty one is never sent and one that drops the form's default variable is refused. mobileSchema, code (suppa_push_form_code), localizations, entity, alias and parent are never sent; `schema.overrides` is preserved. Refuses: someone else's lock (lockedBy), another form's file, a child's layer over a root, a merged tree over a child, an emptied form, a published read. The file's `revision` (or expected_revision) guards it: a form that moved is refused, not overwritten.
suppa_form_code4 of 10 parameters describedA 2.x form's Code Form (TypeScript against the global formAPI), checked as the builder's code editor checks it. rules (once) → pull → api → edit src/** → check → suppa_push_form_code. rules how form code is written, its traps; topic = one section pull the DRAFT's code into a workspace folder with the editor's typings (SDK, this form's elements and variables, tsconfig) api what code may call: path 'formAPI.elements.<name>' | 'formAPI…', or type '<elementType>'; member = one in full, filter = a word. Never read the SDK file check tsc as the editor runs it + imports, invented events, the agent's deny list
suppa_push_form_code4 of 6 parameters describedSave the workspace's Code Form changes to the form's DRAFT: only `code` (PUT /core/forms/:id/schema), revision-guarded, re-read and re-checked first. The server builds it; a failed build is reported and the previous build keeps running. Refused: a file someone saved since your pull (theirs in .suppa-code/conflicts/), a @shared-import file, type errors in changed files, another user's lock. Never publishes.
suppa_create_form_v27 of 7 parameters describedCreate a Suppa 2.0 form: the row and its draft in one transaction (POST /core/forms/schema), as the builder does — isFormBuilderV2 stamped. The default variable of a form with an entity is the record (a relation named after it; a draft's entity-less `submitData` default is replaced, and refused if fields bind into it); `submitData` otherwise. A draft, nothing is published. `path` (optional) is a draft file, gated against those variables. A duplicate name or an unknown entity or folder is refused before any write. `workspace` forms inherit the base form: builder only. A dashboard is `custom` with folder='dashboards'. A create / update form takes the record-card kit's look (suppa_form_kb mode='kit'), judged by `type`. Without confirm=true: the plan only.
suppa_form_versions3 of 4 parameters describedA Suppa 2.0 form's published versions (newest first, which one users see), optionally the component diff between two of THIS form's versions, and a summary of the last N draft saves (change-sets, without their patches). Read-only.
suppa_form_lifecycle3 of 5 parameters describedPublish, roll back, discard or promote a Suppa 2.0 form. publish freezes the draft as the new default version, live for every user. rollback RESTORES an old version over the draft and PUBLISHES it. discard overwrites the draft with the live version — unrecoverable, no history. promote makes a version the one users see. publish and rollback are refused when the form gate finds errors the live version does not have; rollback and promote refuse a version of another form (the platform would act on THAT form). Without confirm=true: the preview only.
suppa_validate_entity_code2 of 2 parameters describedRun the schema gate over an application repo's *.entity.ts / *.seed.ts / module files. CALL THIS BEFORE REPORTING ANY ENTITY OR SEED FILE DONE. It is the same checker the bundled suppa-entity-code skill names as its close-out gate, and it catches what tsc cannot: an unregistered entity class (no table is ever created for it), a JS value in 'default' where a SQL string is required, a relation without a thunk, seed records that duplicate on every restart — plus the house rules, which fail the gate: * a relation property must be typed to match its decorator (Target / Target[], and optional when the relation is nullable) — never 'any'; * enum member keys are PascalCase; * no field option may be written at its default (canGroup/canSort/showInTable/ editFromTable/canFilter are already true, readOnly/searchable already false); * @Enum/@MultiEnum take a global name ONLY when another entity shares the enum; * a relation target that already exists on the tenant gets a STUB — @Entity({name,key}) + extends SystemBaseEntity, EMPTY body, its own file, registered in forFeature(); a bare 'export class Accounts {}' registers nothing (E116), and stubs sharing a file are W616; * to ADD columns to an entity you do NOT own (a system entity, or another application's), declare an EXTENSION — the entity's existing name, only your own columns, in <owner>.extension.entity.ts. Extension mode ignores entity options (W618), refuses @OneToMany/@ManyToManyBackRef (E118) and primary: true (E119), requires a default with nullable: false (E120), and allows @Index/@Check over your own columns only, listed literally (E121/E122). Write every options object out literally: one passed by reference or spread hides all of that (E123). A relation there names its target by string and is typed by shape — that form is W620 anywhere else; * 'owner' comes first in a tabular part's importKeyFields, and no 'inverse' is passed to @ManyToOne/@ManyToMany. Pass the app ROOT, not one file: several rules read the whole repo ("nothing references this enum name" cannot be judged from a single file). passed=false means fix and re-run — it is not advisory.
suppa_versionno parametersWhich suppa-mcp-2 build this session is actually running, and whether a newer one is published. Ask this FIRST whenever a fix, tool or behaviour you were told exists is missing or behaves the old way: an MCP client keeps whatever version it started with (npx cache / node_modules) for the whole session, so a release changes nothing until the client is restarted on the new package. Reports running, latest, whether an upgrade is available, the command to run, and capabilities (cellWidgets = the form gate checks table cell widgets).
suppa_logout2 of 2 parameters describedRemove stored keychain credentials for a tenant (default: the active one). APPROVAL GATE: without confirm=true this returns a confirmation request and removes nothing. Signing back in needs suppa_login and a browser.
suppa_diagnostics1 of 1 parameter describedValidate the whole multi-tenant setup in one report. Checks environment prerequisites (keychain backend, Google client id, login origin to whitelist, registry) and, per known tenant, its registration, stored credentials, expiry and — when deep=true — a live authenticated call that also exercises token refresh. Use this to confirm tenants are configured correctly. Returns JSON with a status, per-tenant rows, and warnings.
suppa_health_check1 of 1 parameter describedHealth check for stdio clients. - deep=false: configuration-only (token present) - deep=true: configuration + upstream connectivity check
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.