Slingrs ERP (Red Mesa) — Model Context Protocol (MCP) Server

Connects AI assistants (Claude Desktop, Antigravity CLI, OpenCode, Claude Code, Cursor, Windsurf) to the Slingrs ERP (Red Mesa) REST API.

Exposes ERP endpoints as MCP tools derived dynamically from the live OpenAPI specification, enabling models to query and act on sales orders, inventory, production (BOMs & Work Orders), purchasing, and shipments.

📦 Usage & Installation

Option 1: Claude Desktop (One-Click .mcpb Bundle)

1. Download the pre-built .mcpb bundle from the dist/ directory or GitHub Releases:
   • redmesa-erp-1.0.3.mcpb (Production — minimal prompt, only requires API Token)
   • redmesa-erp-staging-1.0.3.mcpb (Staging)
   • redmesa-erp-dev-1.0.3.mcpb (Dev)
2. In Claude Desktop, go to Settings → Extensions → Advanced settings → Install Extension…
3. Drag and drop the .mcpb file into the Claude Desktop window.
4. Paste your 32-character Red Mesa API token and complete the installation.

Option 2: CLI Tools & IDEs (OpenCode, Antigravity agy, Cursor, Windsurf)

The server is published to npm as @fmiranda5/redmesa-mcp.

Method A: Direct Execution via npx (Recommended — No prior installation required)

Add the server to your MCP configuration file (e.g., ~/.gemini/config/mcp_config.json, mcp.json, or OpenCode settings):

{
  "mcpServers": {
    "redmesa-erp": {
      "command": "npx",
      "args": [
        "-y",
        "@fmiranda5/redmesa-mcp"
      ],
      "env": {
        "REDMESA_API_TOKEN": "YOUR_32_CHAR_ACCESS_TOKEN"
      }
    }
  }
}

Method B: Global Installation

1. Install the package globally from npm:

   npm install -g @fmiranda5/redmesa-mcp

2. Configure your client:

   {
     "mcpServers": {
       "redmesa-erp": {
         "command": "redmesa-erp",
         "env": {
           "REDMESA_API_TOKEN": "YOUR_32_CHAR_ACCESS_TOKEN"
         }
       }
     }
   }

Method C: Claude Code CLI

claude mcp add redmesa-erp npx -y @fmiranda5/redmesa-mcp \
  -e REDMESA_API_TOKEN=YOUR_32_CHAR_ACCESS_TOKEN

🌐 Multi-Environment Configuration

By default, the server targets the Production environment when only REDMESA_API_TOKEN is provided. You can target Staging or Dev by supplying the corresponding environment variables:

| Environment | Base API URL (REDMESA_API_BASE_URL) | OpenAPI Spec URL (REDMESA_OPENAPI_SPEC) | | :--- | :--- | :--- | | Production (Default) | https://redmesa.slingrs.io/prod/runtime/api | https://redmesa.slingrs.io/dev/runtime/api/files/public/documents/mcp-docs.json | | Staging | https://redmesa.slingrs.io/staging/runtime/api | https://redmesa.slingrs.io/dev/runtime/api/files/public/documents/mcp-docs-staging.json | | Dev | https://redmesa.slingrs.io/dev/runtime/api | https://redmesa.slingrs.io/dev/runtime/api/files/public/documents/mcp-docs-dev.json |

Environment Configuration Examples

Production (Default):

"env": {
  "REDMESA_API_TOKEN": "PROD_TOKEN"
}

Staging:

"env": {
  "REDMESA_API_TOKEN": "STAGING_TOKEN",
  "REDMESA_API_BASE_URL": "https://redmesa.slingrs.io/staging/runtime/api",
  "REDMESA_OPENAPI_SPEC": "https://redmesa.slingrs.io/dev/runtime/api/files/public/documents/mcp-docs-staging.json"
}

Dev:

"env": {
  "REDMESA_API_TOKEN": "DEV_TOKEN",
  "REDMESA_API_BASE_URL": "https://redmesa.slingrs.io/dev/runtime/api",
  "REDMESA_OPENAPI_SPEC": "https://redmesa.slingrs.io/dev/runtime/api/files/public/documents/mcp-docs-dev.json"
}

⚡ How Tools Are Loaded & Refreshed

The extension does not embed a static list of tools. Each time the process starts, it fetches the live OpenAPI specification and dynamically generates the tool schemas in memory.

Refreshing Tools After Backend Changes

If new endpoints or fields are added to the ERP API:

• Claude Desktop: Toggle the extension OFF and ON in Settings → Extensions.
• CLI Tools / IDEs: Restart the active chat session or assistant process.

🛠️ Building Bundles Locally

To build .mcpb bundles for all or specific environments:

# 1. Install dependencies (required before packing)
npm install --omit=dev

# 2. Build bundles
npm run build:all        # Builds Dev, Staging, and Production bundles into dist/
npm run build:staging    # Builds only Staging
npm run build:prod       # Builds only Production

🚀 Releasing & CI/CD

To publish a new version to npm:

npm publish --access public

👤 Author & Support

• Author: Maxi Miranda ([email protected])
• Company: Slingr