MCP Server Beta

The Solarize MCP server offers the endpoints of the public API as tools for your AI assistant, apart from the few listed under Not available as tools. With your permission, it can also change data for you.

The MCP server is in beta and available on request only. Tools, their names and their parameters can change at any time without notice. Send feedback to support@solarize.de.

Server address

The MCP server is available at https://mcp.solarize.energy/mcp. The server uses MCP over HTTP with OAuth authentication. It supports MCP 2026-07-28 and provides stateless Streamable HTTP compatibility for clients using 2025-06-18.

Authentication

You don’t need an API token. Your AI tool opens the Solarize sign-in in your browser. Sign in with Google, Microsoft or a magic link, using your existing Solarize user. The email address of the login must be verified and must belong to that user.

Open the magic link in the same browser that started the sign-in, or the sign-in can’t finish.

After you sign in, a consent page names your AI tool and asks what it may do. It appears on every sign-in:

Reading is always granted.
Writing means creating, changing and deleting data. If your AI tool asks for it, the consent page shows the checkbox “Also allow creating and changing data”. Writing is granted only if you tick it, as the scope mcp:write.

A writing tool called without writing access fails. Some AI tools then offer to sign in again. Otherwise, disconnect and reconnect your AI tool, and tick the checkbox on the consent page.

Your AI tool keeps the connection alive by itself. If it asks you to sign in again, your session has ended.

Connect your AI tool

You can connect Claude, Claude Code, ChatGPT, Codex, Cursor, Antigravity and GitHub Copilot in VS Code. For any other AI tool, ask support@solarize.de.

Request access. Write to support@solarize.de and name each account the MCP server should be enabled for. Access is enabled per account. Your access to other accounts in the app doesn’t open them to the MCP server.
Add Solarize to your tool.
1. Go to Customize > Connectors, click + Add, then Add custom connector.
2. Enter the name Solarize and the URL https://mcp.solarize.energy/mcp, then click Continue.
3. Under Authentication, choose Sign in now. Keep the other detected settings and click Add.
Works in claude.ai and Claude Desktop. On Team and Enterprise plans, an Owner adds the connector under Organization settings > Connectors first, then you click Connect under Customize > Connectors.
claude mcp add --transport http solarize https://mcp.solarize.energy/mcp
Then run /mcp inside Claude Code, select solarize and sign in. Add --scope user to the command to use Solarize in all your projects.
1. In ChatGPT on the web, open Plugins, click +, then Add custom MCP server.
2. Enter the name Solarize. Under Connection, enter the server URL https://mcp.solarize.energy/mcp.
3. Choose OAuth as the authentication.
4. Accept the risk warning, click Create as a plugin, then install the plugin.
In a workspace, its permissions decide whether you can add a custom MCP server.
codex mcp add solarize --url https://mcp.solarize.energy/mcp codex mcp login solarize
The Codex CLI, the IDE extension and the ChatGPT desktop app share this configuration.
Add Solarize to ~/.cursor/mcp.json to use it in all your projects, or to .cursor/mcp.json in a project:
{ "mcpServers": { "solarize": { "url": "https://mcp.solarize.energy/mcp" } } }
Cursor then asks you to sign in. You can switch the server on and off under Customize in Cursor’s sidebar.
Sign in and allow access. Your AI tool opens the Solarize sign-in and consent page in your browser. Reading is always on. Writing is the checkbox on the consent page, see Authentication.

Tools

Each tool is one endpoint of the API Reference and takes the same parameters. A request body goes into the body argument. The tool’s description is the endpoint’s summary and description from the API Reference.

A few examples:

Tool	Endpoint	Access
`get_sites`	`GET /v1/sites`	read
`get_meter`	`GET /v1/meters/{id}`	read
`get_measurements`	`GET /v1/measurements`	read
`create_measurements`	`POST /v1/measurements`	write, needs write access
`complete_bill_run`	`POST /v1/bill-runs/{id}/complete`	write, needs write access

Writing tools are marked as destructive, so your AI tool can ask you before each call. Keep that confirmation switched on. Some tools have effects outside Solarize. For example, complete_bill_run sends invoices.

During the beta, the list of tools and their names and parameters can change at any time.

Working with several accounts

Every account-scoped tool takes an optional accountId argument with the account’s ID. If MCP access is enabled for only one of your accounts, you never need to pass it. If it is enabled for several, your assistant finds them with get_accounts and names one in each call, so one connection covers all of them. Account-independent tools such as get_accounts take no account.

{
  "name": "get_meters",
  "arguments": {
    "accountId": "e988f1e8-43f3-4e43-aacb-95273659114b",
    "siteId": "..."
  }
}

A call without accountId from a user with several accounts gets an error that asks for it and points to get_accounts.

Only accounts with MCP access enabled can be used. get_accounts lists only these. An account-scoped tool called for another of your accounts gets an error that says to request access.

If you signed in with a magic link, you reach only the accounts where magic link is enabled for you, as in the app.

Not available as tools

An endpoint is not available as a tool if any of these applies:

Its request body or successful response is not JSON-only, such as file uploads and downloads. An endpoint that also offers another format counts as not JSON-only. Error responses don’t count.
It is deprecated.
It is the API-token exchange, because the MCP server handles sign-in itself.
It is the cross-account search.
It creates or changes a template, because the firewall in front of the MCP server blocks the template HTML.

These endpoints are currently excluded:

Endpoint	Reason
`POST /v1/oauth`	API-token exchange
`POST /v1/files`	File upload
`POST /v1/files/batch`	File upload
`POST /v1/sepa-export`	Returns a file, not JSON
`GET /v1/customer-emails/{id}/content/{filename}`	File download
`GET /v1/customer-emails/{id}/attachments/{index}/{filename}`	File download
`GET /v1/search`	Cross-account search
`POST /v1/templates`	Template HTML is blocked by the firewall
`PATCH /v1/templates/{id}`	Template HTML is blocked by the firewall

Deprecated endpoints are excluded as well.

Permissions and data

Every tool call runs with the permissions of the user who signed in, the same as in the app. Sign in with a user whose role is restricted to limit what the assistant can see.
Tool results go to your AI tool and its provider. Before you connect, check with your information security and data protection teams that this fits your policies.
Rate limits apply as for the REST API. They count per client IP address, not per user.

Disconnect

Removing the Solarize connector in your AI tool stops that tool from using Solarize. It doesn’t revoke its sign-in on Solarize’s side.

To cut off access on Solarize’s side, ask support@solarize.de to switch off MCP access for the account. This cuts off every user and AI tool on that account, not just yours. Tool calls for that account then stop immediately.

Authentication API Overview