Acceleronix/acc-mcp-server-local

Acceleronix IoT MCP Server

A Model Context Protocol (MCP) server for managing Acceleronix IoT devices. This server provides seamless integration with AI assistants like Claude Desktop and Cursor to control and monitor IoT devices through natural language commands.

🚀 Ready to use: Pre-built DXT package available in dxt-release/ folder
🔧 Developer friendly: Full source code with TypeScript support
🌐 Universal compatibility: Works with any MCP-compatible AI assistant

✨ Features

• 📋 Device Management: List IoT products and devices with pagination support
• 🎛️ Device Control: Control device fan switch, set fan speed modes, and manage buzzer
• 📊 Data Monitoring: Read real-time sensor data (temperature, humidity, pressure)
• 📍 Location Services: Query device location and resource information
• 📈 Historical Data: Access device data history and event logs with full sensor data parsing
• 🔧 Thing Model Support: Dynamic TSL (Thing Specification Language) integration for universal device compatibility
• ✅ Fully Tested: Successfully retrieves and parses device sensor data including temperature, humidity, and pressure readings

📦 Installation Methods

This MCP server supports two installation methods:

🚀 Method 1: DXT Package for Claude Desktop (Recommended)

The quickest way to get started - no build process required!

1. Download DXT Package

   # Navigate to the dxt-release folder
   cd dxt-release/
   
   # The pre-built DXT file is ready to use
   ls acceleronix-iot-mcp-server-v1.0.0.dxt
   

2. Install in Claude Desktop

   • Open Claude Desktop
   • Go to Settings → Extensions
   • Click "Install from DXT file"
   • Select acceleronix-iot-mcp-server-v1.0.0.dxt
   • Configure your API credentials (see Prerequisites section)

📁 What's included: The dxt-release/ folder contains the complete DXT package with documentation, compiled code, and all dependencies - no additional setup required!

🛠️ Method 2: Local MCP Server Installation

For advanced users or integration with other MCP-compatible tools like Cursor, Trae, etc.

Prerequisites

• Node.js 18+
• npm or yarn

Installation Steps

# Clone the repository
git clone <repository-url>
cd acc-mcp-server_local

# Install dependencies
npm install

# Build the project
npm run build

MCP Server Configuration

For Claude Desktop (claude_desktop_config.json):

{
  "globalShortcut": "Ctrl+Space",
  "mcpServers": {
    "acceleronix-iot-mcp-server": {
      "command": "node",
      "args": ["/path/to/acc-mcp-server_local/dist/local-index.js"],
      "env": {
        "BASE_URL": "https://iot-api.acceleronix.io",
        "ACCESS_KEY": "your_access_key",
        "ACCESS_SECRET": "your_access_secret"
      }
    }
  }
}

For Cursor (MCP settings):

{
  "globalShortcut": "",
  "mcpServers": {
    "acceleronix-iot-mcp-server": {
      "command": "node",
      "args": ["/path/to/acc-mcp-server_local/dist/local-index.js"],
      "env": {
        "BASE_URL": "https://iot-api.acceleronix.io",
        "ACCESS_KEY": "your_access_key",
        "ACCESS_SECRET": "your_access_secret"
      }
    }
  }
}

🔑 Prerequisites

Get Acceleronix Platform API Credentials

Before using this MCP server, obtain API credentials from the Acceleronix IoT platform:

Step 1: Sign up and Access Developer Center

1. Sign up: Visit Acceleronix Developer Platform and create an account
2. Access Developer Center: Log into your developer dashboard

Step 2: Create SaaS Application

1. Navigate to "SaaS Development" → "SaaS Management"
2. Click "Create a SaaS Application"
3. Fill in application information and save

Step 3: Configure API Services

1. Go to "SaaS Development" → "Service"
2. Enable and authorize required API service packages
3. Important: You can only call APIs after service authorization

Step 4: Authorize Product Access

1. Navigate to "SaaS Development" → "Product"
2. Authorize product data the application can access
3. Important: Only authorized product data can be queried via API

Step 5: Get API Credentials

1. In your SaaS application settings, find your credentials
2. Note your ACCESS_KEY and ACCESS_SECRET
3. These credentials are used for API authentication

🔧 Available Tools

💡 Usage Examples

Natural Language Commands

• "Turn on the fan for my IoT device (device key or device name)"
• "Set the fan to medium speed"
• "What's the latest temperature reading from my device (device key or device name)?"
• "Show me the device location"
• "Get the last 24 hours of sensor data"
• "List all my IoT products (product name or product key)"

Device Control Examples

Fan Control:

• "Please turn on the fan for my device (device key or device name)"
• "Switch the fan to low speed mode"
• "Turn off the fan"

Data Monitoring:

• "Show me the current temperature and humidity readings"
• "Get the latest 10 sensor data points"
• "What's the device status right now?"

Device Management:

• "List all devices in my product (product name or product key)"
• "Show me detailed information about my device (device key or device name)"
• "Where is my device (device key or device name) located?"

📁 Project Structure

acc-mcp-server_local/
├── src/                    # Source code
│   ├── local-index.ts     # Main entry point
│   ├── local-iot-server.ts # MCP server implementation  
│   └── local-iot-utils.ts  # API utilities
├── dist/                   # Compiled JavaScript
├── dxt-release/           # DXT package for Claude Desktop
│   ├── README.md          # DXT-specific documentation
│   ├── *.dxt             # Pre-built DXT file
│   └── build.sh          # DXT build script
├── package.json
└── README.md             # This file

🚧 Development

Building the Project

npm run build

Creating DXT Package

# Use the provided build script
./build.sh

# Or manually from dxt-release folder
cd dxt-release/
./build.sh

🔍 Troubleshooting

Common Issues

💡 Pro tip: Use the health_check tool to quickly verify your configuration and connectivity status.

🤝 Contributing

We welcome contributions from the community! Here's how you can help improve the Acceleronix IoT MCP Server:

• 🐛 Bug fixes and improvements
• 📖 Documentation enhancements
• 🔧 New IoT device integrations
• 🧪 Test coverage improvements
• 🌐 Internationalization support

📄 License

Licensed under the terms specified in the LICENSE file.