How to integrate NocoDB MCP with Grok Build

Connect Grok Build to NocoDB MCP. List all projects updated this week, add a new record to clients table, and more from your terminal, with authentication handled for you.

NocoDB logoNocoDB
Api KeyApi Key

NocoDB is a free, open-source Airtable alternative that turns any database into a smart spreadsheet with REST APIs. Easily manage and collaborate on data without vendor lock-in or steep learning curves.

27 Tools

How to integrate NocoDB MCP with Grok Build

Grok Build is xAI's terminal coding agent. It runs on Grok 4.5, plans its work before it acts, and can run multiple sub-agents in parallel. It also reads Claude Code's MCP configuration, so any server you already have in a .mcp.json is picked up with no changes.

In this guide, I will show you how to connect your NocoDB account to Grok Build through Composio, so it can list all projects updated this week, add a new record to Clients table, update status of Task ID 42 to Done, and more without leaving the terminal. Composio holds the OAuth tokens for you, and Grok Build only calls the tools you approve.

Also integrate NocoDB with

Why use Composio over a standalone MCP server?

  • Read and write access. Composio's NocoDB integration lets Grok Build take real actions like creating drafts, sending updates, and labeling records, not just reading data.
  • 1,000+ SaaS toolkits out of the box. One endpoint gives you a full catalog of pre-built connectors, from Gmail and Slack to Notion, Linear, and Salesforce.
  • One MCP server for every app. Wire up a single Composio server instead of maintaining a separate MCP entry for each app.
  • Smart, context-aware tool loading. Grok Build caps how many tools it holds in a single request. Composio loads only the tools a task needs, so you do not spend that budget on tools you are not using.
  • Cross-app automation. Chain actions across apps in one run. Pull a thread, summarize it in Notion, and post the highlights to Slack from a single prompt.

Prerequisites

  • Grok Build installed and signed in. Install with curl -fsSL https://x.ai/cli/install.sh | bash on macOS or Linux, or irm https://x.ai/cli/install.ps1 | iex on Windows PowerShell. On first launch Grok opens a browser to authenticate; for headless or CI use, set an XAI_API_KEY environment variable instead (create the key at console.x.ai).
  • Access to the NocoDB account you want to connect.
  • The Composio MCP endpoint. Composio's server is remote and hosted, so there is nothing to run locally and no tunnel to set up.

Step-by-step: Connect NocoDB to Grok Build

1. Install and verify Grok Build

Install the CLI, then restart your shell so the grok binary lands on your PATH:

bash
curl -fsSL https://x.ai/cli/install.sh | bash
which grok

On Windows, install with PowerShell instead: irm https://x.ai/cli/install.ps1 | iex. If which grok returns a path, you are set. Grok Build runs on Grok 4.5 by default; you can switch models inside the session with /model <name>.

2. Add the Composio server

Add Composio as a remote HTTP MCP server with the grok mcp add command:

bash
grok mcp add --transport http composio https://connect.composio.dev/mcp

You can also add and manage servers from inside a session. Run /mcps to open the extensions modal on the MCP tab, then add a new server and paste the Composio URL. Added this way, Grok auto-detects the name from the URL and lists the server as connect:

bash
https://connect.composio.dev/mcp
Grok Build /mcps extensions modal listing MCP servers Grok Build adding the Composio MCP server with its URL

Grok also reads Claude Code-style config, so an entry in ~/.grok/config.toml or a project .mcp.json works the same way.

3. Authenticate

Composio uses OAuth. In the /mcps modal, select the Composio server and press i to authenticate (Grok also triggers this browser flow automatically the first time it uses a Composio tool). Click Allow to authorize access. Grok stores the tokens under ~/.grok/mcp_credentials.json, and /mcps shows Composio as connected.

Grok Build prompting to authenticate the Composio MCP server Composio authorization screen with the Allow button for Grok Build

4. Start building

Ask Grok to work with your NocoDB account through Composio. On the first NocoDB action, Composio prompts you to connect the account through OAuth. Approve the scopes once, and Composio handles token refresh from there.

What you can do after connecting NocoDB

  • List all projects updated this week
  • Add a new record to Clients table
  • Update status of Task ID 42 to Done

Security + privacy notes (important)

  • Use least-privilege access. Grant only the NocoDB scopes you actually need.
  • Review OAuth scopes before approving. Check that the requested scopes match what you expect Composio and Grok Build to do.
  • Keep write actions human-reviewed. Grok Build proposes a plan before it acts. Leave that approval step on for actions like sending messages or editing records.
  • Keep secrets out of version control. Your XAI_API_KEY and any tokens should never be committed. Use environment variables or a secrets manager.
TOOLS

Supported Tools

Every NocoDB action and event your agent gets out of the box.

Get User Info

Tool to get authenticated user information including email, name, roles, and profile details.

Forgot Password

Tool to initiate password reset process by sending a reset email to the user.

Sign Out User

Tool to sign out the authenticated user and clear their refresh token from the database and cookie.

Get Sort Metadata

Tool to retrieve sort configuration by ID from NocoDB.

Update View Column

Tool to update a column configuration in a view.

Delete View

Tool to delete a view from a NocoDB table.

Delete Table View Row

Tool to delete a specific row from a table view in NocoDB.

Get Integration Info

Tool to retrieve metadata for a specific NocoDB integration by type and subtype.

List Integrations

Tool to retrieve all available integrations in NocoDB.

Store Integration Configuration

Tool to store configuration for a NocoDB integration.

Delete Notification

Tool to delete a notification for the authenticated user.

List Notifications

Tool to retrieve paginated notification records for the authenticated user.

Poll Notifications

Tool to poll for notifications using long-polling mechanism.

Get Plugin Status

Tool to check if a NocoDB plugin is active or not.

List Public Shared View Grouped Data

Tool to retrieve grouped data from a publicly shared NocoDB view.

Upload Attachments by URL

Tool to upload attachments from remote URLs to NocoDB storage.

Get Table Schema

Tool to retrieve complete schema information for a specific table.

Update User Profile

Tool to update authenticated user's profile information including display name, first name, and last name.

Get Aggregated Meta Info

Tool to get aggregated meta information such as tableCount, dbViewCount, viewCount and other statistics about the NocoDB instance.

Get Application Health Status

Tool to get the NocoDB application health status.

Get Application Info

Tool to get comprehensive NocoDB application information including authentication settings, version, limits, and deployment configuration.

Get Cloud Features

Tool to get NocoDB Cloud features.

Get Command Palette Suggestions

Tool to get dynamic command palette suggestions based on scope.

Report Error

Tool to report errors to NocoDB's error tracking system.

Get Product Feed

Tool to get NocoDB product feed from social media sources including GitHub, YouTube, Twitter, and Cloud.

Convert URL to Database Config

Tool to convert JDBC URL or database connection URL to connection configuration object.

List Workspace Bases

Tool to list all bases in a NocoDB workspace.

FAQ

Frequently asked questions

A standalone NocoDB MCP server gives Grok Build a fixed set of NocoDB tools tied to that one server. The Composio Tool Router lets Grok Build load tools from NocoDB and many other apps on demand, based on the task, all through a single endpoint.

Yes. Grok Build ships with native MCP support. Add a server with the grok mcp add command, from the in-session /mcps modal, or by editing ~/.grok/config.toml. It also reads Claude Code-style .mcp.json files, so Grok Build discovers the tools automatically.

Yes. Grok Build has zero-migration compatibility with Claude Code's configuration, so the same Composio server entry works in both without edits.

Tokens, keys, and configuration are encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant, so your NocoDB data and credentials are handled to that standard.

Start with NocoDB.It takes 30 seconds.

Managed auth, hosted MCP servers, and every NocoDB tool your agent needs.Free to start.

Start building