myUplink MCP Server

A Model Context Protocol (MCP) server that connects Claude (or any MCP client) to your NIBE myUplink heat-pump account.

Based on kalmma/myUplink-MCP-Server.

Credentials

Do not upload credentials to GitHub, or put them in any file that gets committed.

That includes the myUplink client id, client secret, access token, and refresh token.

• Keep them only in a local .env file. .env is gitignored and must never be committed or pushed.

• .env.example lists the variable names with empty values. Copy it to .env and fill it in on your own machine.

• Do not paste secrets into mcp.json when that file is committed, into issues, into pull requests, or into this README.

• Before every push, check git status. .env must not appear as a staged or untracked file that you then add.

The server loads .env from the project directory itself, so a client does not need the secret embedded in its own config.

Related MCP server: unofficialMCP4Vaillant

Features

Prerequisites

• Node.js 18+

• A myUplink account with at least one connected device

• An OAuth2 application created at https://dev.myuplink.com/apps

Setup

git clone <this-repo>
cd myuplink-mcp
npm install
cp .env.example .env
# Edit .env – add your CLIENT_ID and CLIENT_SECRET
npm run build

Running the server

npm start
# or during development:
npm run dev

Claude Desktop integration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):

{
  "mcpServers": {
    "myuplink": {
      "command": "node",
      "args": ["/absolute/path/to/myuplink-mcp/dist/index.js"],
      "env": {
        "MYUPLINK_CLIENT_ID": "your_client_id",
        "MYUPLINK_CLIENT_SECRET": "your_client_secret",
        "MYUPLINK_REFRESH_TOKEN": "optional_saved_refresh_token"
      }
    }
  }
}

First-time authentication (Authorization Code flow)

1. Call get_authorization_url → open the URL in a browser

2. Log in and approve the scopes

3. Copy the code=… value from the redirect URL

4. Call exchange_auth_code with that code

5. From now on the server auto-refreshes tokens using the refresh token

No-browser alternative (Client Credentials)

If your myUplink application supports it, call authenticate_client_credentials – no browser needed, but only your own account data is accessible.

Common myUplink parameter IDs

Find more by calling get_device_points without a filter.

Scopes

License

MIT