Tools

neoom MCP for Power Partners: setup and use

Updated on 17/11/2026

What is the neoom MCP for?

With the neoom MCP, your AI assistant gets access to neoom's product knowledge. Instead of searching manuals and articles yourself, you ask your question in the chat, and the assistant gets the answer directly from the neoom sources. This saves you time during installation, commissioning and support.

Access covers two sources with publicly released content:

  • Knowledge base: manuals, knowledge base articles (docs.neoom.com) and support cases.
  • Product ontology: products, compatibility, prerequisites, limitations and fault patterns.

Typical use cases:

  • Installation and commissioning: what do you need to consider for a specific combination of components?
  • System questions: does a function work with this system, and which prerequisites apply?
  • Faults: what can be behind an error message or error code, and which details are missing to clarify it?
  • Support: prepare draft replies to customer requests that you check before sending. You can find an example prompt for this in the article System prompt for support reply drafts.

Internal neoom information is not included. If an answer depends on it, the assistant tells you, and you clarify the point with neoom support.

The rest of this article describes the technical connection.

1. Request a token

neoom creates the token for you. To get one, create a support ticket at support.neoom.com. You will then receive the token separately and encrypted.

2. Set up

In your MCP client, enter the URL `https://mcp.neoom.com/` (transport Streamable HTTP) and the header `Authorization: Bearer <your token>`. Replace `YOUR_TOKEN` in the examples with your token.

Claude Code

```bash
claude mcp add --transport http neoom https://mcp.neoom.com/ --header "Authorization: Bearer YOUR_TOKEN"
```

VS Code (`.vscode/mcp.json`, asks for the token at startup and does not store it in the file)

```json
{
"inputs": [
{ "type": "promptString", "id": "neoom-token", "description": "neoom MCP Token", "password": true }
],
"servers": {
"neoom": {
"type": "http",
"url": "https://mcp.neoom.com/",
"headers": { "Authorization": "Bearer ${input:neoom-token}" }
}
}
}
```

Cursor (`~/.cursor/mcp.json`, do not check the file into a repository)

```json
{
"mcpServers": {
"neoom": {
"url": "https://mcp.neoom.com/",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
```

Your own applications and agents: any MCP client with Streamable HTTP and a freely settable header works, with the same two details.

Caution: The connectors in Claude (web and desktop) are not suitable. They sign in with a login and cannot send a token. A login is also only possible with an approved email domain.

3. Check the connection

This call lists the available tools. If a JSON list comes back, everything is set up.

```bash
curl -s https://mcp.neoom.com/ \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

If the server responds with `401`, the token is missing, misspelled, expired or blocked by neoom.

If the product ontology tools, such as `suche`, are missing from the list, the ontology is currently unavailable. Reconnect later; many clients only load the tools when connecting.

Alternatively with the MCP Inspector: start `npx @modelcontextprotocol/inspector`, transport "Streamable HTTP", URL `https://mcp.neoom.com/`, header `Authorization` with `Bearer YOUR_TOKEN`.

4. Which tools are available

Your assistant chooses the tools itself. The most important ones per source:

Source

Content

Most important tools

Knowledge base

Manuals, knowledge base articles, support cases

`search_documents` (search), `get_document` (full document)

Product ontology

Products, compatibility, prerequisites, limitations, fault patterns

`anleitung` (once at the start), `suche` (entry point), `eintraege`, `konfiguration_auswerten`, `klaerungsstand`, `rueckfrage_plan`

The ontology tools have German names; your assistant uses them regardless of the language you write in.

Example questions for your assistant:

  • "What do I need to consider when installing a KJUUBE with a Solax inverter?"
  • "The BEAAM stays on 'updating' permanently. What can I do?"

Name the product in your question, such as STAAK Flex or BLOKK. Otherwise your assistant may ask for it first, because the answer depends on it.

If an answer depends on internal information, it contains a note such as "Details intern" (details internal). Then clarify the point with neoom support.

If something is missing or a detail is wrong, your assistant can report it to neoom with the `rueckmeldung` tool.

As a source, the knowledge base provides the public links on docs.neoom.com. You do not get links to internal storage.

5. Good to know

  • Limit: Up to 30 knowledge base queries per minute and 1,000 per day (`search_documents`, `get_document`). The product ontology tools do not count. The day changes at midnight UTC, in Austria at 01:00 in winter and 02:00 in summer. Above the limit you get the error `rate_limited` with the waiting time in seconds (`retry_after`).
  • Treat the token like a password: Store it only in a password manager or secret store, never in code repositories, tickets, chats or prompts. The token has an expiry date. You request a new token the same way as the first one, via a support ticket.
  • Suspected misuse or loss: Create a support ticket at support.neoom.com immediately. We will block the token and issue you a new one.
  • No personal data: Requests are logged. Do not write names, addresses, serial numbers or other customer data in your questions.
  • Check answers: The answers are created by an AI based on the neoom sources. Binding information, for example on warranty or replacement, is provided by neoom support.

Questions, new token or blocking: create a support ticket at support.neoom.com.

More on For partners