Create NocoDB View
Create a new view on an existing table. Each view type has different prerequisites — see the view-management skill.
The view types, their prerequisites and create payloads are written down in ${CLAUDE_PLUGIN_ROOT}/skills/view-management/SKILL.md; read it before the first step.
Steps
- Resolve the target table ID.
- Snapshot existing views and the field list:
mcp__plugin_nocodb-dev_nocodb__getTableSchema tableId: <tableId> - Confirm the view title isn't already used on this table.
- Pick the view type and validate prerequisites:
- Grid / Form — no prerequisites
- Gallery — needs an Attachment field for the cover image (recommended); capture its ID for
options.cover_field_id - Kanban — needs a SingleSelect field; capture its ID for
options.stack_by.field_id - Calendar / Timeline — needs a Date or DateTime field; capture for
options.date_ranges[].start_date_field_id(and the end field) - Gantt — needs start/end Date fields;
options.date_dependencyis required (nulltakes the table default) - List — needs linked tables; describe them in
options.levels - Map — needs a Geometry field; capture for
options.geo_data_field_id
- Create the view. On Cloud / licensed:
listTools category: "views", thencallTool name: "createView"witharguments: { tableId, title, type, lock_type?, options?, fields? }. On Community Edition (or as a fallback) — payloads per view-management:curl -sS -X POST \ -H "xc-token: ${NOCODB_TOKEN}" -H "Content-Type: application/json" \ -d '{ "title": "<viewTitle>", "type": "<type>", "options": { … } }' \ "${NOCODB_URL}/api/v3/meta/bases/${BASE_ID}/tables/<tableId>/views" - Verify with
mcp__plugin_nocodb-dev_nocodb__getTableSchema— the new view appears inviews.
Reference
Skill nocodb-dev:view-management— full workflow + payload shape per typeSkill nocodb-dev:cli-reference—curlrecipes (references/view-filter-sort.md)
Notes
- The view APIs need cloud Enterprise or a licensed self-hosted deployment (Business plan and above).
- After creating a view, add filters and sorts: MCP
createFilter/addSort, or RESTPOST …/views/{viewId}/filterswith{ "field_id", "operator", "value" }andPOST …/views/{viewId}/sortswith{ "field_id", "direction" }.