NocoDB MCP integration for AI agents.
Connect AI agents to NocoDB through 24 structured actions, including count records, create records, and delete records. Review authentication, inputs, workfl…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the NocoDB integration exposes
The NocoDB Agent App exposes 24 provider-backed actions for data and productivity work. Its current contract lets an authorized agent count records in one nocodb table, optionally filtered by a where expression, create one or more records in a nocodb table, and delete one or more records from a nocodb table. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected NocoDB account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real NocoDB capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
count_recordsREADCount records in one NocoDB table, optionally filtered by a where expression.
INPUTS: tableId / where / viewId
create_recordsWRITECreate one or more records in a NocoDB table.
INPUTS: tableId / rows
delete_recordsHIGH IMPACTDelete one or more records from a NocoDB table.
INPUTS: tableId / rows
count_table_recordsREADCount records in one NocoDB table using the v3 data API.
INPUTS: baseId / tableId / where / viewId
create_tableWRITECreate a table in a NocoDB base using the v3 metadata API.
INPUTS: baseId / title / description / sourceId / meta
create_table_fieldWRITECreate a field in a NocoDB table using the v3 metadata API.
INPUTS: baseId / tableId / field
create_table_recordsWRITECreate one or more records in a NocoDB table using the v3 data API.
INPUTS: baseId / tableId / records
create_table_viewWRITECreate a view for a NocoDB table using the v3 metadata API.
INPUTS: baseId / tableId / view
delete_tableHIGH IMPACTDelete a NocoDB table using the v3 metadata API.
INPUTS: baseId / tableId
delete_table_recordsHIGH IMPACTDelete one or more records from a NocoDB table using the v3 data API.
INPUTS: baseId / tableId / records
get_base_schemaREADGet schema metadata for one NocoDB base.
INPUTS: baseId
get_current_userREADGet the NocoDB user associated with the connected API token.
INPUT CONTRACTS
Know what the action needs before it runs.
count_records
tableIdREQUIRED- The NocoDB table ID, such as m1abcdefghijk.
whereOPTIONAL- A NocoDB where expression, such as (Status,eq,Done).
viewIdOPTIONAL- The NocoDB view ID used to restrict records to a specific view.
create_records
tableIdREQUIRED- The NocoDB table ID, such as m1abcdefghijk.
rowsREQUIRED- Records to create in the table.
delete_records
tableIdREQUIRED- The NocoDB table ID, such as m1abcdefghijk.
rowsREQUIRED- Records to delete. Each record must include its NocoDB record ID.
count_table_records
baseIdREQUIRED- The NocoDB base ID.
tableIdREQUIRED- The NocoDB table ID, such as m1abcdefghijk.
whereOPTIONAL- A NocoDB v3 where expression, such as (Status,eq,Done).
viewIdOPTIONAL- The NocoDB view ID used to restrict records to a specific view.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Count Records
Count records in one NocoDB table, optionally filtered by a where expression. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
count_recordsControl Create Records
Create one or more records in a NocoDB table. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_recordsVerify with Count Table Records
Count records in one NocoDB table using the v3 data API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
count_table_recordsSAFETY BOUNDARY
Operate NocoDB with explicit limits
- Authorize NocoDB with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_records`, `delete_table`, and `delete_table_records` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in NocoDB rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the NocoDB task completed successfully.
CONNECTION MODEL
API key
NocoDB API token sent in the xc-token header. Create or copy a personal API token from your NocoDB account settings: https://docs.nocodb.com/product-docs/account-settings/api-tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 12
- WRITE SIGNALS
- 9
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by NocoDB.