Init Project

Initialize Composable Stack v1

Set up environment variables, verify all MCP connections, and create project configuration for the Composable Stack.

Architecture Overview

NocoBase: Two Instances

This stack uses two NocoBase instances for a safe develop-then-promote workflow:

Rule of thumb:

• Build new tables, fields, collections, menus, pages, blocks, and workflows on the dev instance first.
• Test API flows and test apps against the dev instance — safe to break.
• Promote validated schema and UI to prod via export/import or migration.

The nocobase-dev MCP server in this plugin points at ${NOCOBASE_DEV_URL}/api/mcp, so the full nc-mcp toolset (~146 tools: collections, fields, resources, workflows, flow-surfaces, RBAC, data sources) is available for the dev instance out of the box.

Step 1: Environment Variables

Using Infisical (recommended)

Pull all secrets from Infisical in one command:

./scripts/setup.sh dev .env .claude/settings.local.json

This writes .env and injects variables into .claude/settings.local.json for MCP resolution.

Manual Setup

Copy the template and fill in values:

cp templates/.env.example .env

Required variables:

Step 2: Verify MCP Connections

Test each service connection in order.

2a. NocoDB (Data layer)

Tool: mcp__nocodb__getTablesList

Expected: returns a list of tables from the connected NocoDB base.

2b. n8n External MCP (Logic layer)

Tool: mcp__n8n-mcp-external__searchNodes
Input: { "query": "webhook" }

Expected: returns matching n8n node types.

2c. n8n Native MCP (Logic layer)

Tool: mcp__n8n-native-mcp__listWorkflows

Expected: returns workflows from the n8n instance.

2d. Trigger.dev (Logic layer)

Tool: mcp__trigger-dev__list_runs

Expected: returns recent task runs.

2e. PostgreSQL MCP (Data layer — direct)

Tool: mcp__postgresql-mcp__database_overview

Expected: returns PostgreSQL server version, uptime, connection counts, and replica status.

2f. PostgREST API (Data layer — REST)

Verify with a direct HTTP call:

curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer ${POSTGRESQL_API_TOKEN}" \
  "${POSTGRESQL_API_URL}/"

Expected: HTTP 200 with OpenAPI spec of available endpoints.

2g. NocoBase dev instance (Interface layer — sandbox)

The nocobase-dev MCP server in this plugin targets ${NOCOBASE_DEV_URL}/api/mcp. Verify with any nc-mcp tool:

Tool: mcp__nocobase-dev__collections_list

Expected: returns the collections defined on the dev NocoBase instance.

Also verify HTTP API access:

curl -s -H "Authorization: Bearer ${NOCOBASE_DEV_API_KEY}" \
  "${NOCOBASE_DEV_URL}/api/collections:list" | head -c 500

Expected: HTTP 200 with a JSON list of collections.

2h. NocoBase production instance (Interface layer)

Production NocoBase is accessed via HTTP API only (no MCP transport in this plugin — keeps prod safe from accidental MCP mutations):

curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer ${NOCOBASE_API_KEY}" \
  "${NOCOBASE_URL}/api/collections:list"

Expected: HTTP 200.

If you need MCP against production, the nocobase-dev technology plugin can be re-pointed at NOCOBASE_URL — but prefer to build on the dev instance and promote.

Step 3: Create CLAUDE.md

Copy the template:

cp templates/CLAUDE.md.template CLAUDE.md

Replace {{PROJECT_NAME}} with your project name.

Step 4: Verify Installed Plugins

Confirm all technology plugins are enabled in .claude/settings.json:

• trigger-dev@agents-store-claude-plugins
• n8n-dev@agents-store-claude-plugins
• nocodb-ops@agents-store-claude-plugins
• nocobase-dev@agents-store-claude-plugins
• postgresql-external-dev@agents-store-claude-plugins
• n8n-provision@agents-store-claude-plugins

These provide tool-specific knowledge. The stack plugin provides integration patterns between services.

Troubleshooting