Create NocoDB Field
Add a field to an existing table. Choose any of the 35 supported types — see the field-management skill and api-reference/references/field-types.md for per-type payloads. Type-specific settings go inside options.
The field types, create payloads and update rules are written down in ${CLAUDE_PLUGIN_ROOT}/skills/field-management/SKILL.md; read it before the first step.
Steps
- Resolve the target table ID —
mcp__plugin_nocodb-dev_nocodb__getTablesListif a name was passed, or prompt. - Snapshot existing fields:
mcp__plugin_nocodb-dev_nocodb__getTableSchema tableId: <tableId> - Confirm the new field title isn't already taken.
- Determine the field type. Common pairings:
- "phone" →
PhoneNumber - "money / price / amount" →
Currency - "status / stage" →
SingleSelect(gather choices) - "tags / categories (many)" →
MultiSelect(gather choices) - "image / file / attachment" →
Attachment - "linked record" →
LinkToAnotherRecord(ask cardinality: bt / hm / mm / oo) - "computed value" →
Formula(gather expression) - "auto-incrementing id" →
AutoNumber
- "phone" →
- Build the payload (per
field-types.md):{ "title": …, "type": …, "options": { … } }. - Create it. On Cloud / licensed:
listTools category: "fields", thencallTool name: "createField"witharguments: { tableId: "<tableId>", field: <payload> }. On Community Edition (or as a fallback):curl -sS -X POST \ -H "xc-token: ${NOCODB_TOKEN}" -H "Content-Type: application/json" \ -d '<JSON>' \ "${NOCODB_URL}/api/v3/meta/bases/${BASE_ID}/tables/<tableId>/fields" - Verify with
mcp__plugin_nocodb-dev_nocodb__getTableSchemaandmcp__plugin_nocodb-dev_nocodb__queryRecords(small page, sanity-check render).
Reference
Skill nocodb-dev:field-management— workflow + cheatsheetSkill nocodb-dev:api-reference— full type catalog (references/field-types.md)Skill nocodb-dev:mcp-patterns—createFieldover MCP vs the REST body
Special Cases
- Lookup / Rollup: the underlying link field must already exist. If it doesn't, run
/nocodb-dev:add-relationfirst. - Formula: after creating, query 3 records to spot-check that the formula renders without
ERR. - System fields (
CreatedTime,LastModifiedTime,CreatedBy,LastModifiedBy): created instantly with{"title":"X","type":"<TypeName>"}; populate themselves. - Select choices later: use the options endpoint /
addFieldOptionsinstead of resending the whole list.