Workflows and Automation with NocoDB MCP
An MCP client can build NocoDB workflows step by step, test and publish them, and read their runs. It can also manage webhooks, scripts and automation folders, and set up agents, talk to them and read what they did.
These 60 tools are in the Automation section of Tools & Permissions. A tool needs the access level in its row: Read, Read & write, or Read, write & delete. Two more tools, executeWorkflow and testHook, are opt-in tools: a connection gets them only when you switch them on.
How the assistant works with workflows
Read and write workflow drafts. Add nodes and test nodes. Publish an automation after all its nodes are tested.
List, read, create, update, and delete scripts.
A test of a workflow node over MCP is a check, not a run. The node does not do its action. For example, a create-record node writes no row, and a messaging node sends nothing. NocoDB resolves the node configuration against the results of the nodes before it and checks it with read-only calls. The result shows as simulated.
Some nodes can only be checked with a real run, for example a script step or a node that declares no outputs. For these nodes, the test fails and MCP cannot clear the failure. You cannot publish until someone runs that step in the automation editor.
executeWorkflow runs a published automation for real, so its steps write records, call external services and send messages. It is an opt-in tool, off until you switch it on for the connection.
Manage webhooks.
Tools
Workflows
Needs workflows on your plan. Without it, these tools are not offered.
| Tool | What it does | Access level |
|---|---|---|
listWorkflows | List the automations (workflows) of the current project. | Read |
getWorkflow | Get one automation, including its editable draft graph and the published nodes/edges. | Read |
listWorkflowNodeTypes | List automation node types available here: id, title, category, description, icon, ports, requiredConfigKeys, hidden status, and plan lock status. | Read |
getWorkflowAuthoringInstructions | How to author an automation draft over this API: graph shape, trigger and edge rules, expression syntax, and what is rejected. | Read |
listExecutions | List past runs of an automation. | Read |
getExecution | Get one run of an automation, including its node results. | Read |
createWorkflow | Create an automation. | Read & write |
updateWorkflow | Update an automation's title, description or draft graph. | Read & write |
duplicateWorkflow | Duplicate an automation into the same project. | Read & write |
publishWorkflow | Publish an automation: the tested draft becomes the live version and starts running for real on its trigger. | Read & write |
deleteWorkflow | Delete an automation. | Read, write & delete |
executeWorkflow | Run the published version of an automation now, with optional inputs for its trigger. This is a real run: its nodes write records, call external services and send messages. NocoDB refuses the run when the automation is turned off. The run is queued, so read its outcome with getExecution. | Opt-in |
Workflow steps
Needs workflows on your plan. Without it, these tools are not offered.
| Tool | What it does | Access level |
|---|---|---|
addWorkflowNode | Add one node to an automation's draft. | Read & write |
updateWorkflowNode | Update one node of an automation's draft. | Read & write |
connectWorkflowNodes | Add one edge to an automation's draft. | Read & write |
disconnectWorkflowNodes | Remove the edge between two nodes of an automation's draft. | Read & write |
validateWorkflowNode | Test one node of an automation and store the result, which is what the validate flag on the node-editing tools does, and what publish requires of every node. | Read & write |
deleteWorkflowNode | Delete one node from an automation's draft. | Read, write & delete |
Webhooks
Needs webhooks in MCP on your plan. Without it, these tools are not offered.
| Tool | What it does | Access level |
|---|---|---|
listHooks | List webhooks of a table. | Read |
getHook | Get a webhook by ID. | Read |
createHook | Create a webhook on a table. | Read & write |
updateHook | Update an existing webhook. | Read & write |
deleteHook | Delete a webhook. | Read, write & delete |
testHook | Fire a webhook once, as configured, with a sample payload built from its table. This is a real request to the hook URL, or a real email or message for other notification types, and the hook log records it. | Opt-in |
Scripts
Needs scripts in MCP on your plan. Without it, these tools are not offered.
| Tool | What it does | Access level |
|---|---|---|
listScripts | List NocoDB scripts in a project. | Read |
getScript | Get a NocoDB script by ID. | Read |
getScriptAuthoringInstructions | How to write the source for a NocoDB script: the runtime globals, the record read/write API, and the silent-failure modes the generated editor typings do not mention. | Read |
createScript | Create a new NocoDB script. | Read & write |
updateScript | Update an existing NocoDB script. | Read & write |
duplicateScript | Duplicate a script into the same project. | Read & write |
restoreScript | Restore a script from the project trash. | Read & write |
deleteScript | Move a script to the project trash. | Read, write & delete |
Automation folders
Needs folders on your plan. Without it, these tools are not offered.
| Tool | What it does | Access level |
|---|---|---|
listAutomationFolders | List the automation folders of the current project with the workflows and scripts inside each, plus the unfoldered automations under topLevel. | Read |
createAutomationFolder | Create an automation folder in the current project. | Read & write |
updateAutomationFolder | Rename an automation folder or change its order. | Read & write |
moveAutomationToFolder | Move a workflow or script into an automation folder, or back to the top level with folderId: null. | Read & write |
deleteAutomationFolder | Delete an automation folder. | Read, write & delete |
Agents
Needs agents on your plan. Without it, these tools are not offered. Creating, changing and deleting agents and their channels needs the Creator role or a higher role in the project.
A turn runs in the background. Poll getAgentSession until its turn is no longer running, then read the reply with listAgentMessages.
| Tool | What it does | Access level |
|---|---|---|
listAgents | List the agents of the current project, with their roles and channels. | Read |
getAgent | Get one agent: its instructions, tools, triggers, delivery and, for a coding agent, its code settings. | Read |
listAgentSessions | List the conversations and triggered runs of an agent. | Read |
getAgentSession | Where the turn of one session stands: idle, running, waiting for a person to approve the tools that it named, or failed. | Read |
listAgentMessages | Read the messages of one agent session. The messages of a coding turn are written when it ends. | Read |
sendAgentMessage | Send a message to an agent, in a new session or an existing one. For a coding agent this works on its default repository. | Read & write |
stopAgentSession | Stop the turn that a session is running. The session stays, so another message carries on from there. You can stop a session that you started, and a Creator can stop the coding session of anyone. | Read & write |
createAgent | Create an agent in a project. | Read & write |
updateAgent | Update an agent. The change applies at once, with no separate publish step. | Read & write |
duplicateAgent | Copy an agent with its instructions, tools, triggers and, for a coding agent, its repositories. | Read & write |
createAgentChannel | Connect an agent to a channel, for example Slack or Telegram, through a channel integration of the workspace. | Read & write |
updateAgentChannel | Rename an agent channel, switch it off, or change its settings. | Read & write |
testAgentChannel | Check the connection of an agent channel to its platform, without sending a message. | Read & write |
deleteAgent | Move an agent to the project trash. | Read, write & delete |
deleteAgentChannel | Disconnect an agent from a channel. The integration stays. | Read, write & delete |
Coding agents
Needs coding agents on your plan, and they run on NocoDB Cloud only. Without them, these tools are not offered. Listing the repositories of an agent, starting a session and reading its changes need the Editor role or a higher role in the project. Launching an agent, finding repositories and their tasks, and changing the repositories of an agent need the Creator role or higher.
| Tool | What it does | Access level |
|---|---|---|
listAgentRepos | List the GitHub repositories of a coding agent. A session starts on the default one unless it names another. | Read |
listAvailableRepos | List the repositories that a GitHub App connection of the workspace can reach. | Read |
listRepoTasks | List the open issues and pull requests of a repository, to start a session from. | Read |
getCodingSessionDiff | Get everything that a coding session changed, as one patch, with its branch and its commits. A large patch is cut at file boundaries and names the files that it left out. | Read |
launchCodingAgent | Create a coding agent ready to run: its repositories, its machine and its first session, in one call. | Read & write |
startCodingSession | Start a coding session on one of the repositories of the agent. It starts from the start branch of the repository unless it names a branch, an issue or a pull request. | Read & write |
addAgentRepo | Add a GitHub repository to a coding agent. The first repository becomes the default and starts a setup session that installs the project. | Read & write |
setDefaultAgentRepo | Make a repository the default of a coding agent, where sessions and triggers start. | Read & write |
updateAgentRepo | Change the branch that sessions on this repository start from. | Read & write |
removeAgentRepo | Take a repository off a coding agent. Sessions already on it keep their checkout. | Read, write & delete |
Related
Last updated on