Skip to content

Commit 08377b8

Browse files
authored
Merge pull request #324 from nocodb/docs/rate-limit
docs: rate limits
2 parents 25ffa21 + c1620da commit 08377b8

File tree

3 files changed

+106
-2
lines changed

3 files changed

+106
-2
lines changed
Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
title: MCP Server
3+
description: Connect NocoDB to Large Language Models (LLMs) via the Model Context Protocol (MCP).
4+
tags: ["MCP", "LLM", "AI", "Claude", "Cursor", "Windsurf"]
5+
keywords: ["MCP", "Model Context Protocol", "NocoDB MCP", "LLM Integration", "Claude", "Cursor", "Windsurf"]
6+
---
7+
8+
The **Model Context Protocol (MCP) Server** lets you connect NocoDB with LLMs that support MCP, such as Claude, Cursor, or Windsurf. With this integration, LLMs can interact directly with your NocoDB workspace to create, query, update, and manage records.
9+
10+
Each MCP endpoint in NocoDB provides a secure URL that can be linked to an MCP-compatible client.
11+
Once configured, the LLM can execute database operations in your workspace through natural language prompts.
12+
13+
<Callout type="info"> The MCP integration currently works only with desktop clients that support MCP. Support for web based clients is coming soon. </Callout>
14+
15+
MCP server exposes standard CRUD operations. These can be triggered conversationally, without writing SQL or scripts.
16+
17+
| Action | Purpose | Sample Prompt |
18+
|--------|----------------------|---------------------------------------------------------------|
19+
| Create | Add new records | Create a task named ‘Review Documentation’ |
20+
| Read | Look up information | Show me all projects with deadlines this week |
21+
| Update | Change existing data | Mark the status of Project X as completed & re-assign to John |
22+
| Delete | Remove records | Remove all tasks assigned to John |
23+
24+
25+
## Server Configuration (NocoDB)
26+
27+
1. Click on the **Overview** button in the left sidebar.
28+
2. Select the **Settings** tab.
29+
3. Select the **Model Context Protocol**
30+
4. Click on the **New MCP Endpoint** to create a new MCP config JSON for your base.
31+
5. Provide a name for the MCP endpoint
32+
6. Click **Create** to generate the MCP Config JSON.
33+
7. Copy the generated JSON configuration. This will be used in your LLM client configuration.
34+
35+
![MCP Config](/img/v2/mcp/server-configuration.png)
36+
37+
![MCP Config](/img/v2/mcp/server-configuration-2.png)
38+
39+
40+
## Client Configuration
41+
42+
### Claude
43+
44+
1. Open **Claude Desktop Preferences** (`⌘+,`).
45+
2. Under **Develop**, click **Edit Config**.
46+
3. Insert the JSON block copied [here](#server-configuration-nocodb) as `claude_desktop_config.json`.
47+
4. Save the file and restart Claude Desktop.
48+
49+
50+
### Cursor
51+
52+
1. Go to **Cursor Settings** (`⇧+⌘+J`).
53+
2. Open the **MCP** tab and select **Add Custom MCP**.
54+
3. Paste the JSON block copied [here](#server-configuration-nocodb). Save.
55+
56+
<Callout type="info"> On success, you will see `11 tools enabled` below the MCP Server just installed. If you see an error, double-check the JSON configuration. </Callout>
57+
58+
![Cursor MCP Settings](/img/v2/mcp/cursor-mcp.png)
59+
60+
61+
### Windsurf
62+
63+
1. Open **Windsurf Settings** (`⌘+,`).
64+
2. In the **Cascade** section > `Plugins (MCP Server)` > Click **Manage Plugins**
65+
3. Paste the JSON block copied [here](#server-configuration-nocodb). Save.
66+
67+
![Windsurf MCP Settings](/img/v2/mcp/windsurf-mcp-1.png)
68+
69+
![Windsurf MCP Settings](/img/v2/mcp/windsurf-mcp-2.png)
70+
71+
72+
## JSON Example
73+
74+
```json
75+
{
76+
"mcpServers": {
77+
"NocoDB MCP": {
78+
"command": "npx",
79+
"args": [
80+
"mcp-remote",
81+
"https://your-domain.com/mcp/<ncId>",
82+
"--header",
83+
"xc-mcp-token: <ncToken>"
84+
]
85+
}
86+
}
87+
}
88+
89+
````
90+
91+
<Callout type="warning"> Your MCP configurations generated above functions as a set of access credentials, granting full control over your NocoDB base. Ensure it remains confidential, never include it in source control, and store it only in secure, protected locations.</Callout>
92+
93+
---
94+
95+
Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
{
2-
"title": "Developer resources",
2+
"title": "Developer",
33
"pages": [
44
"rest-apis",
5-
"webhook"
5+
"mcp"
66
],
77
"icon": "code"
88
}

content/docs/developer-resources/rest-apis/index.mdx

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,15 @@ Additional information on the REST APIs is provided below.
1818

1919
- When querying using v3 apis, see [v3 Where Clause](/docs/product-docs/developer-resources/rest-apis#v3-where-query-parameter) for a slight difference between the two version's where clause.
2020

21+
22+
## Rate Limits
23+
NocoDB APIs are rate-limited to ensure fair usage and optimal performance for all users. The default rate limit is set to **5 requests per second per user**. These limits are the same across all plans.
24+
25+
If these limits are exceeded, the API will return a 429 status code (Too Many Requests). You’ll need to wait 30 seconds before sending additional requests.
26+
27+
NocoDB may adjust these limits or introduce additional rate tiers based on pricing plans to maintain optimal service performance.
28+
29+
2130
## Query params
2231

2332
| **Name** | **Alias** | **Use case** | **Default value** | **Example value** |

0 commit comments

Comments
 (0)