Prime Forecast MCP

Read-only MCP gateway Phase 1 for Prime Forecast V3

• Production Laravel: https://sale.primes.co.th

• Remote MCP: https://mcp.primes.co.th/mcp

• Runtime: Node.js 24.19.0

• Plesk startup file: app.js

• Transport: stateless Streamable HTTP

• Data path: MCP → Laravel API Gateway → Prime Forecast V3

• Phase 1 policy: no create/update/delete/write tools

Phase 1 tools

Every tool has MCP annotations readOnlyHint: true, destructiveHint: false and checks both role and explicit permission from Laravel

Related MCP server: salesforce-mcp

Getting started locally

Copy-Item .env.example .env
npm install
npm test
$env:NODE_ENV='development'
$env:LARAVEL_MCP_SERVICE_TOKEN='local-test-service-token'
node app.js

Values from the .env file are not loaded automatically in production; set them directly via Plesk Environment Variables

Documentation

• Phase 1 plan and approval criteria

• Architecture and security boundaries

• Laravel API contract

• How to integrate Laravel V3

• Deploy via Plesk/GitHub without a Terminal

• Permission test matrix

Important status

The Node MCP and automated tests are ready, but do not expose production data until the Laravel adapter is aligned with the real model/schema, tested with real Sales / Team Admin / Admin accounts across all cases, and the OAuth 2.1 or token issuance mechanism to be used with real clients is confirmed. Do not add write tools until the approval gate in docs/phase-1-plan.md is passed.