NocoBase를 위한 MCP(Model Context Protocol) 서버로, Claude와 같은 AI 어시스턴트가 NocoBase 인스턴스와 상호작용할 수 있게 해줍니다. 컬렉션 읽기, UI 스키마 관리, flowPage 블록 빌드, OpenAPI를 통한 동적 API 작업 실행이 가능합니다.
24개의 수동 제작 도구: 컬렉션, UI 스키마, 데스크톱 라우트, 플로우 모델 및 JS 블록을 다룹니다.
동적 도구: NocoBase의 OpenAPI/Swagger 사양에서 자동 생성됩니다 (API 문서 플러그인 필요).
NocoBase v2.x와 호환됩니다 (2.0.17-full에서 테스트됨).
Related MCP server: anyapi-mcp-server
Node.js 18+
실행 중인 NocoBase 인스턴스
NocoBase API 토큰 (루트 또는 충분한 권한)
npm install -g @reroet/nocobase-mcp-server그런 다음 ~/.claude/mcp.json에 추가합니다:
{
"mcpServers": {
"nocobase": {
"type": "stdio",
"command": "nocobase-mcp-server",
"env": {
"NOCOBASE_URL": "http://localhost:13000",
"NOCOBASE_API_TOKEN": "your-api-token-here"
}
}
}
}또는 전역 설치 없이 npx를 사용합니다:
{
"mcpServers": {
"nocobase": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@reroet/nocobase-mcp-server"],
"env": {
"NOCOBASE_URL": "http://localhost:13000",
"NOCOBASE_API_TOKEN": "your-api-token-here"
}
}
}
}git clone https://github.com/puguhsudarma/nocobase-mcp-server.git
cd nocobase-mcp-server
pnpm install그런 다음 ~/.claude/mcp.json에 추가합니다:
{
"mcpServers": {
"nocobase": {
"type": "stdio",
"command": "/absolute/path/to/nocobase-mcp-server/node_modules/.bin/tsx",
"args": ["/absolute/path/to/nocobase-mcp-server/src/index.ts"],
"env": {
"NOCOBASE_URL": "http://localhost:13000",
"NOCOBASE_API_TOKEN": "your-api-token-here"
}
}
}
}/absolute/path/to/nocobase-mcp-server를 실제 경로(예: /Users/yourname/Projects/nocobase-mcp-server)로 바꿉니다.
변수 | 필수 | 기본값 | 설명 |
| 예 | — | NocoBase API 토큰 |
| 아니오 |
| NocoBase 인스턴스 기본 URL |
NocoBase UI에서: 설정 → 플러그인 → API keys 플러그인 활성화
설정 → API keys → API 키 추가로 이동
생성된 토큰 복사
NocoBase에서 API 문서 플러그인을 활성화합니다 (설정 → 플러그인). 활성화되면 서버 시작 시 모든 추가 API 엔드포인트가 도구로 자동 로드됩니다.
도구 | 설명 |
| 모든 컬렉션 나열 |
| 이름으로 컬렉션 가져오기 |
도구 | 설명 |
| 모든 UI 스키마 노드 나열 |
| UID로 전체 중첩 UI 스키마 트리 가져오기 |
| 노드의 부모 스키마 가져오기 |
| 새로운 루트 레벨 UI 스키마 노드 생성 |
| 새로운 UI 스키마 노드 생성 및 삽입 |
| 대상 노드에 상대적으로 스키마 노드 삽입 |
| 기존 UI 스키마 노드 패치 |
| 한 번의 요청으로 여러 UI 스키마 노드 패치 |
| UI 스키마 노드 및 하위 항목 제거 ⚠️ |
| UI 스키마 노드를 재사용 가능한 블록 템플릿으로 저장 |
도구 | 설명 |
| 모든 데스크톱 라우트(페이지, 메뉴, 그룹, 탭) 나열 |
도구 | 설명 |
| UID로 flowPage 블록 가져오기 |
| 부모 ID와 subKey로 flowPage 블록 가져오기 |
| flowPage 블록 생성 또는 업데이트 |
| flowPage 컨테이너에 블록 부착 |
| 블록을 다른 위치로 이동 |
| 블록을 딥 카피하고 자동 부착 |
| 블록 및 하위 항목 삭제 ⚠️ |
도구 | 설명 |
| JS 블록 스키마 가져오기 (클래식 페이지) |
| JS 블록 코드 업데이트 (클래식 페이지) |
| flowPage 내 JS 블록 코드 업데이트 — |
⚠️ 파괴적인 작업은 되돌릴 수 없습니다.
flowPage JS 블록은 NocoBase의 샌드박스에서 실행됩니다. 사용 가능한 API:
// Render HTML
ctx.render(`<h1>Hello</h1>`);
// Render JSX with React + Ant Design
const { React, antd } = ctx.libs;
const { useState } = React;
const { Table, Tag } = antd;
function MyComponent() {
const [tab, setTab] = useState("a");
return <div>...</div>;
}
ctx.render(<MyComponent />);UID를 얻는 방법:
블록 UID — NocoBase UI에서 블록 우클릭 → UID 복사 (예:
add17a3cf3f)페이지 UID — 페이지를 열 때 브라우저 URL에서 확인 가능 (예:
http://localhost:13000/page/96acpujiwc6→ UID는96acpujiwc6)
List all collections in my NocoBase, then create a JS block on flowPage "<your-page-uid>"
that shows a summary dashboard with total records from the "users" collection.Get the flowPage with UID "<your-page-uid>", add a new JS block below the existing ones
(the grid block UID is "<your-grid-uid>"), and implement a tabbed table showing data
from the "orders" and "products" collections.Show me all desktop routes, then fetch the UI schema tree of the first page
and explain its block structure.Here's my Figma design: https://www.figma.com/board/XXXXXXXXXXXXXXXX/MyApp?node-id=8273-xxxx
Implement it as a JS block on flowPage "<your-page-uid>" (grid UID: "<your-grid-uid>").
Use React + Ant Design from ctx.libs. Use dummy data for now.Fetch the Figma design at the link above, then create a new JS block on my NocoBase
flowPage and implement the tabs component with the exact columns from the Figma table.
The block UID I want to update is "<your-block-uid>".기여를 환영합니다! 새로운 도구를 추가하려면:
저장소를 포크하고 기능 브랜치를 생성합니다.
server.registerTool()을 사용하여 src/index.ts에 도구를 추가합니다.
기존 패턴을 따릅니다 — API 호출에는 nocoFetch()를, 응답 형식 지정에는 ok()를 사용합니다.
README.md의 도구 목록을 업데이트합니다.
풀 리퀘스트를 엽니다.
버그 보고나 기능 요청은 GitHub에서 이슈를 열어주세요.
MIT — 자세한 내용은 LICENSE를 참조하세요.
Attach an existing flowPage block/model to a parent. Use this to add an existing block into a flowPage container at a specific position.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Flow model UID to attach | |
| parentId | Yes | Parent flow model UID to attach to | |
| subKey | Yes | Sub-key within the parent (e.g. 'items') | |
| subType | No | Sub-type (e.g. 'array') | |
| position | No | Sort position index |
Patch multiple UI schema nodes in a single request. Each object in the patches array must include 'x-uid' plus the fields to update.
| Name | Required | Description | Default |
|---|---|---|---|
| patches | Yes | Array of partial schema patch objects, each identified by x-uid |
Create a new root-level UI schema node in NocoBase
| Name | Required | Description | Default |
|---|---|---|---|
| schema | Yes | UI schema object to create (JSON) |
Delete a flowPage block/model by UID. DESTRUCTIVE — also removes child blocks.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Flow model UID to delete |
Duplicate an existing flowPage block/model (deep copy) and automatically attach it to the same parent. Returns the new block's data.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Flow model UID to duplicate |
Get a specific collection by name
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Collection name |
Get a flowPage block/model by UID. Use this for blocks inside flowPage type pages (not classic 'page' type). Returns the block's model data including 'use' (component type), 'parentId', 'stepParams', etc.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Flow model UID (from 'Copy UID' on a block inside a flowPage) | |
| includeAsyncNode | No | Whether to include async node data (default false) |
Get a flowPage block/model by its parent ID and subKey. Useful for navigating the flowPage block tree.
| Name | Required | Description | Default |
|---|---|---|---|
| parentId | Yes | Parent flow model UID | |
| subKey | No | Sub-key within the parent (e.g. 'items') | |
| includeAsyncNode | No | Whether to include async node data (default false) |
Get a JS block UI schema by UID (for classic 'page' type pages, not flowPage)
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID of the JS block |
Get the full nested UI schema tree for a node by UID (uses :getProperties to include all descendants)
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID |
Get the parent UI schema of a node by UID
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID of the child node |
Insert a schema node at a position relative to a target node. Position values: beforeBegin (prev sibling), afterBegin (first child), beforeEnd (last child), afterEnd (next sibling)
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Target UI schema UID to insert relative to | |
| schema | Yes | New schema node to insert (JSON) | |
| position | Yes | Insert position relative to the target node |
Create and insert a new UI schema node via NocoBase's insertNewSchema action
| Name | Required | Description | Default |
|---|---|---|---|
| schema | Yes | Schema node to create and insert (JSON) |
List all collections in NocoBase
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
List all desktop routes (pages and menus) in NocoBase v2. Each route has a type: 'page', 'flowPage', 'group', 'tabs'. Use schemaUid to fetch page content. Works for both classic pages and flowPages.
| Name | Required | Description | Default |
|---|---|---|---|
| pageSize | No | Number of routes per page (default 100) |
List all UI schemas in NocoBase (returns raw schema nodes, not page-level navigation)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Move a flowPage block/model to a different position relative to another block.
| Name | Required | Description | Default |
|---|---|---|---|
| sourceId | Yes | UID of the flow model to move | |
| targetId | Yes | UID of the target flow model (reference position) | |
| position | No | Target sort position index |
Remove a UI schema node and all its descendants by UID. DESTRUCTIVE — cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID to remove |
Save an existing UI schema node as a reusable block template
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID to save as template | |
| values | Yes | Template metadata (e.g. name, componentName, collectionName) |
Create or update a flowPage block/model. If 'uid' is provided in values, it updates; otherwise creates a new one. The 'use' field specifies the component type (e.g. 'JSBlockModel', 'TableBlockModel'). NOTE: after creating, call attach_flow_model to make it appear on the page.
| Name | Required | Description | Default |
|---|---|---|---|
| values | Yes | Flow model data. Key fields: uid (optional), use (component type), parentId, subKey, subType, stepParams, sortIndex |
Update the JavaScript code of a JSBlockModel inside a flowPage. Code runs in NocoBase sandbox — use ctx.render(htmlString) to render output. Example: ctx.render(<h1>Hello</h1>);
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | Flow model UID of the JS block (JSBlockModel) | |
| code | Yes | JavaScript code using ctx.render(htmlString) sandbox API |
Update the code content of a JS block UI schema by UID (for classic 'page' type pages, not flowPage)
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID of the JS block | |
| code | Yes | New JavaScript code content |
Patch an existing UI schema node by UID (partial update)
| Name | Required | Description | Default |
|---|---|---|---|
| uid | Yes | UI schema UID | |
| patch | Yes | Partial schema fields to update (JSON) |
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.5get_page_propertiesv1.0.0attach_flow_modelbatch_patch_ui_schemacreate_pagedestroy_flow_modelduplicate_flow_modelget_collectionget_flow_modelget_flow_model_by_parentget_js_blockget_pageget_page_propertiesget_parent_schemainsert_adjacent_schemainsert_new_schemalist_collectionslist_desktop_routeslist_pagesmove_flow_modelremove_ui_schemasave_as_templatesave_flow_modelupdate_flow_js_blockupdate_js_blockupdate_ui_schemaScored across 23 tools
Tools are generally distinct, with clear differentiation between flowPage blocks, classic pages, JS blocks, and UI schema operations. However, the high number of flow model and schema tools could cause some confusion, though descriptions help.
All tool names follow a consistent verb_noun pattern in snake_case, with no mixing of conventions. Examples include 'attach_flow_model', 'batch_patch_ui_schema', 'get_flow_model_by_parent'.
23 tools is slightly on the high side but appropriate for a full-featured low-code platform like NocoBase. The count reflects the complexity of managing UI schemas, blocks, collections, and routes without being excessive.
The tool set covers most essential operations for UI schema management: create, read, update, delete, move, duplicate, and template. Minor gaps exist (e.g., no direct tool for updating page metadata), but these can be handled via update_ui_schema.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
