How to integrate NocoDB MCP with LangChain

This guide walks you through connecting NocoDB to LangChain using the Composio tool router. By the end, you'll have a working NocoDB agent that can list all projects updated this week, add a new record to clients table, update status of task id 42 to done through natural language commands. This guide will help you understand how to give your LangChain agent real control over a NocoDB account through Composio's NocoDB MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

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

Introduction

This guide walks you through connecting NocoDB to LangChain using the Composio tool router. By the end, you'll have a working NocoDB agent that can list all projects updated this week, add a new record to clients table, update status of task id 42 to done through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a NocoDB account through Composio's NocoDB MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate NocoDB with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your NocoDB project to Composio
  • Create a Tool Router MCP session for NocoDB
  • Initialize an MCP client and retrieve NocoDB tools
  • Build a LangChain agent that can interact with NocoDB
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

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.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with NocoDB functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to NocoDB tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['nocodb']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to NocoDB tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use NocoDB tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "nocodb-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our NocoDB MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available NocoDB tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any NocoDB related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with NocoDB and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['nocodb']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "nocodb-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any NocoDB related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with NocoDB through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
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

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.

Yes, you can. LangChain 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.

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.

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.

Start with NocoDB.It takes 30 seconds.

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

Start building