neoom BEAAM MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@neoom BEAAM MCP ServerHow much solar am I producing right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
neoom BEAAM MCP Server
A Model Context Protocol (MCP) server for the neoom BEAAM energy management system. It lets AI assistants like Claude query your solar production, battery state, grid power, and control devices using natural language.
Features
π€οΈ Real-time energy flow data (PV production, grid, battery, self-sufficiency)
π Battery control (set charge/discharge power)
β‘ EV charger control (set max charging current)
π Device inventory (list all connected Things and their data points)
βοΈ Two modes: local BEAAM API (full control) or ntuity cloud API (remote read-only)
π Automatic OAuth token refresh in cloud mode
Requirements
Node.js 18 or higher
A neoom BEAAM device
An API key from neoom.com/developers
Installation
git clone https://github.com/your-username/neoom-mcp.git
cd neoom-mcp
npm install
npm run buildConfiguration
The server supports two modes, auto-detected from environment variables.
Local mode (recommended β full control, requires local network)
Variable | Description |
| IP address of your BEAAM on the local network (e.g. |
| Bearer API key from neoom.com/developers |
Cloud mode (remote access, read-only energy data)
Variable | Description |
| OAuth Client ID from developer.neoom.com |
| OAuth access token (see setup below) |
| OAuth refresh token (see setup below) |
| (optional) Pin to a specific site ID β skip the |
Getting cloud tokens (one-time)
NTUITY_CLIENT_ID=<your_client_id> npm run oauth-setupThis opens your browser for neoom login, completes the PKCE OAuth flow, and prints the tokens to paste into your config.
Usage with VS Code + GitHub Copilot
Create .vscode/mcp.json in this workspace (already gitignored to protect your secrets):
Local mode:
{
"servers": {
"neoom-beaam": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/build/index.js"],
"env": {
"BEAAM_IP": "192.168.1.100",
"BEAAM_API_KEY": "sk_beaam_..."
}
}
}
}Cloud mode:
{
"servers": {
"neoom-beaam": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/build/index.js"],
"env": {
"NTUITY_CLIENT_ID": "your_client_id",
"NTUITY_ACCESS_TOKEN": "your_access_token",
"NTUITY_REFRESH_TOKEN": "your_refresh_token",
"NTUITY_SITE_ID": "your_site_id"
}
}
}
}Then open Copilot Chat (Cmd+Shift+I), switch to Agent mode, and the tools will be available automatically.
Usage with Claude for Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"neoom-beaam": {
"command": "node",
"args": ["/absolute/path/to/neoom-mcp/build/index.js"],
"env": {
"BEAAM_IP": "192.168.1.100",
"BEAAM_API_KEY": "sk_beaam_..."
}
}
}
}Usage with Claude Code CLI
claude mcp add --transport stdio neoom-beaam node -- /absolute/path/to/neoom-mcp/build/index.jsSet the env vars in your shell profile or prepend them when running Claude.
Available Tools
Local mode
Tool | Description |
| Current grid/PV/battery/SoC/self-sufficiency values |
| All connected devices with IDs and DataPoint keys |
| Per-device metrics by Thing ID |
| Set battery |
| Set EV charger |
Cloud mode
Tool | Description |
| Current energy flow (requires |
| All sites accessible to the authenticated account |
Example Prompts
How much solar am I producing right now?
What is my battery state of charge?
Set my battery to charge at 3000W.
List all devices connected to my BEAAM.
What is the current state of my battery master?
Pause EV charging.
Am I currently exporting to the grid?Project Structure
src/
βββ index.ts # MCP server β tool registration, mode detection
βββ neoom-client.ts # Local BEAAM REST API client
βββ ntuity-client.ts # ntuity cloud API client with OAuth token refresh
βββ oauth-setup.ts # One-time CLI helper for cloud OAuth PKCE flow
build/ # Compiled JavaScript (run npm run build)
.vscode/
βββ mcp.json # Your local config with secrets (gitignored)
βββ mcp.json.example # Template to share with othersDevelopment
npm run build # Compile TypeScript
npm run dev # Watch mode (tsc --watch)
npm run oauth-setup # Run cloud OAuth setupSecurity
.vscode/mcp.jsonis gitignored β your IP and API keys will not be committed.Use
.vscode/mcp.json.exampleas a template to share the config structure without secrets.Never commit
.envfiles or tokens to version control.
License
This project is licensed under the MIT License.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/thorstenroth4040/Neoom-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server