How to integrate NocoDB MCP with Codex

Framework Integration Gradient
NocoDB Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With NocoDB MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install NocoDB MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

What is the NocoDB MCP server, and what's possible with it?

The NocoDB MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your NocoDB account. It provides structured and secure access so your agent can perform NocoDB operations on your behalf.

Supported Tools & Triggers

Tools
Get User InfoTool to get authenticated user information including email, name, roles, and profile details.
Forgot PasswordTool to initiate password reset process by sending a reset email to the user.
Sign Out UserTool to sign out the authenticated user and clear their refresh token from the database and cookie.
Get Sort MetadataTool to retrieve sort configuration by ID from NocoDB.
Update View ColumnTool to update a column configuration in a view.
Delete ViewTool to delete a view from a NocoDB table.
Delete Table View RowTool to delete a specific row from a table view in NocoDB.
Get Integration InfoTool to retrieve metadata for a specific NocoDB integration by type and subtype.
List IntegrationsTool to retrieve all available integrations in NocoDB.
Store Integration ConfigurationTool to store configuration for a NocoDB integration.
Delete NotificationTool to delete a notification for the authenticated user.
List NotificationsTool to retrieve paginated notification records for the authenticated user.
Poll NotificationsTool to poll for notifications using long-polling mechanism.
Get Plugin StatusTool to check if a NocoDB plugin is active or not.
List Public Shared View Grouped DataTool to retrieve grouped data from a publicly shared NocoDB view.
Upload Attachments by URLTool to upload attachments from remote URLs to NocoDB storage.
Get Table SchemaTool to retrieve complete schema information for a specific table.
Update User ProfileTool to update authenticated user's profile information including display name, first name, and last name.
Get Aggregated Meta InfoTool to get aggregated meta information such as tableCount, dbViewCount, viewCount and other statistics about the NocoDB instance.
Get Application Health StatusTool to get the NocoDB application health status.
Get Application InfoTool to get comprehensive NocoDB application information including authentication settings, version, limits, and deployment configuration.
Get Cloud FeaturesTool to get NocoDB Cloud features.
Get Command Palette SuggestionsTool to get dynamic command palette suggestions based on scope.
Report ErrorTool to report errors to NocoDB's error tracking system.
Get Product FeedTool to get NocoDB product feed from social media sources including GitHub, YouTube, Twitter, and Cloud.
Convert URL to Database ConfigTool to convert JDBC URL or database connection URL to connection configuration object.
List Workspace BasesTool to list all bases in a NocoDB workspace.

Conclusion

You've successfully integrated NocoDB with Codex using Composio's Rube MCP server. Now you can interact with NocoDB directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for NocoDB operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various NocoDB operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build NocoDB MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and NocoDB MCP?

With a standalone NocoDB MCP server, the agents and LLMs can only access a fixed set of NocoDB tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from NocoDB and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right NocoDB tools.

Can I manage the permissions and scopes for NocoDB while using Tool Router?

Yes, absolutely. You can configure which NocoDB scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your NocoDB data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.