Connect Claude or ChatGPT to CreaRack (AI assistant)

What it is

You can connect your own AI assistant — Claude or ChatGPT — to CreaRack and ask it questions in plain language, for example “Which rooms have more than 100 WiFi clients right now?”, “What is down at the moment?”, “How much free space is left in rack A12?” or “Which screens are not playing their playlist?”. The assistant answers with live data from CreaRack.

• Read-only. The assistant can look, never change anything.
• Your own account. You sign in with your CreaRack username and password (and your MFA if you have it). The assistant sees exactly what you see in CreaRack, and only your organization.
• Off by default. An administrator of your organization has to switch it on first, because the data you ask about goes to the AI company that runs your assistant.
• Included in every plan. You pay nothing extra to CreaRack; the AI itself runs on your own Claude or ChatGPT subscription.

What it can answer

Since version 1.177.0 (1 October 2026) the assistant covers every area of CreaRack. It only sees the modules your plan includes and your role can view.

• Overview and search: what your organization has in CreaRack (how many racks, devices, plans, access points, UPS units, screens), which modules are active, and a single search by name, IP or location that looks in racks, network devices, monitored devices and screens at once.
• Your own criteria: the free-text notes your team keeps on the monitoring overview. Write there how you want things handled (for example “radar channel changes are left to the access points”) and the assistant takes it into account before recommending changes.
• Racks and data center: the list of racks with free space in U, what is inside each rack and at which position, where a device is by its name, your plans (maps, rows, rooms) and which racks of a plan have devices down or in warning.
• Network: your switches, routers and firewalls with their details (model, serial number, firmware, ports up and down, neighbours), how a device behaved over the last hours (latency, packet loss, availability, traffic of its busiest ports, errors), which configuration backups exist and whether they changed (never their content), the cabling between ports and the status of your Local Agents.
• Wireless: groups and their access points; the summary of a group; clients per access point and per radio, with channel, power, noise and signal quality; the table of clients connected to an access point (radio, band, signal, speed, device type, with how old that snapshot is); the history of each radio (channel changes and how noise, signal, utilization and clients evolved); channel changes across the site; clients per network (VLAN/SSID) now and over time.
• Monitoring: active alerts, devices down now, outages in the last 24 hours, the alert rules you have configured, the availability of a device over the last days, the notes your team left on the charts, maintenance windows in progress, the diagnoses of the network assistant and the average response times to incidents, and a search in your runbooks and known issues.
• UPS: one UPS with its readings and history, the whole fleet with the worst cases, or a group.
• Digital signage: which screens are connected and what they are really showing (including when a screen is paused or black), the playlists and schedules, what was played over the last days and the state of your media library.
• For administrators only: the users of the organization with their role and two-factor status, the login history, the audit log of who did what, and a security summary (who has no two-factor, failed logins, active assistant connections). Users who are not administrators do not even see these queries in their assistant, and any attempt is recorded as refused.

Series look back at most 24 hours (availability up to 30 days, signage playback up to 7 days). For longer periods, use the CreaRack reports.

Step 1 · An administrator switches it on

1. Open User Settings (Configuration → Users → User Settings). The switch is only visible to administrators.
2. In AI assistant (MCP), tick Allow users to connect an AI assistant. A message confirms “AI assistant enabled”.
3. Tell your team to open User Settings: once the assistant is on, every user sees the address to paste, https://crearack.com/mcp, in the AI assistant section of the left column (under Email alerts), together with a link called How to connect an assistant. Until an administrator switches it on, that section only says “Your administrator has not enabled the AI assistant for this organization.”

Unticking the box disconnects every assistant in the organization at once. Users have to connect again after it is switched back on.

Step 2 · Each user connects their assistant

Claude (claude.ai on the web, the desktop app or the mobile app):

1. In Claude, open Settings → Connectors and choose Add custom connector.
2. Give it a name (for example “CreaRack”) and paste https://crearack.com/mcp as the server URL.
3. Click Connect. A CreaRack page opens: sign in if you are asked to.
4. CreaRack shows Allow this app to access CreaRack? with the app name, the address you will be sent back to (it must be claude.ai), your organization and the access level. Click Allow.

ChatGPT: add a connector (custom app) with the same address and follow the same sign-in and Allow steps; the address you are sent back to must be chatgpt.com.

Claude Code (for technical users): claude mcp add --transport http crearack https://crearack.com/mcp, then /mcp to sign in. Here the page warns that the app is on this computer — that is expected. If you add the server while Claude Code is already open, restart it so the new server appears in /mcp.

One connection, one organization. Your assistant sees the organization of the account you signed in with. To ask about another organization you have an account in, disconnect and connect again with that account.

Step 3 · See and disconnect your assistants

Every user can see which assistants are connected with their account and cut any of them:

1. Open User Settings and look at the AI assistant section in the left column.
2. Under My connected assistants each connected assistant appears with its app name, the address it connected from and when it was Last used. If there is none, you will see “No assistant connected yet.”
3. Click Disconnect next to the one you want to cut. A message confirms “Assistant disconnected”. That assistant stops working straight away and has to ask for your permission again (the Allow page) to reconnect.

Each time you connect an assistant from a different app or device it appears as its own entry, so you can cut one without affecting the others.

For administrators · see every connection and what was asked

Administrators can see the assistants of the whole organization and what they looked at:

1. Open User Settings. In the AI assistant (MCP) section, click View Connections & Activity. A window called “AI assistant: connections and activity” opens.
2. Connected assistants lists every connection in your organization: the user, the app, the address it connected from, since when (Since) and when it was last used (Last used).
3. Click Disconnect on a row to cut that assistant. You can do it for any user of your organization; the user has to allow it again to reconnect.
4. Activity shows the latest 100 questions the assistants asked CreaRack: time, user, tool, result (OK, Denied, Error or Rate limited) and detail. Hover over the tool name to see what was asked, shortened. Use the user filter (All Users by default) to look at one person. Refused attempts are listed too.

Only administrators see this window; other users see just their own assistants.

Where to be careful

• After an update, reconnect. Claude fixes the list of queries at the moment you connect. When CreaRack adds new ones (as on 1 October 2026), disconnect the connector in Claude and connect it again to see them; otherwise the assistant will say it cannot answer things it actually can.
• Snapshots are not always current. Some answers come from the last snapshot CreaRack took of a device (for example the table of WiFi clients of an access point). The assistant tells you when that snapshot was taken and whether it is recent; treat an old one as history, not as “now”.
• Check the address on the Allow page. The app name is written by whoever connects, so it proves nothing; the address is what counts. It must be claude.ai, chatgpt.com or, for Claude Code, a local address on your own computer. If it shows anything else, click Deny.
• The answers go to your AI provider. Whatever the assistant reads from CreaRack is processed by Anthropic (Claude) or OpenAI (ChatGPT) under your agreement with them. That is why an administrator decides whether to allow it.
• Your role still applies. If your role cannot see a module in CreaRack (for example the Wireless Monitor), the assistant cannot see it either and will tell you so. Passwords, SNMP communities, configuration backup contents, publishing tokens and screenshots never leave CreaRack.
• Every question is recorded. CreaRack keeps a record of what each assistant looked at and when, including refused attempts. Administrators can read it in View Connections & Activity.
• Disconnecting. Use Disconnect in User Settings to cut one assistant, or the administrator’s switch to cut everyone at once. Removing the connector in Claude or ChatGPT also stops your assistant from using it on your side, but only Disconnect in CreaRack closes its access on the CreaRack side.
• Heavy use is limited. An assistant that asks too many questions in one minute is asked to wait and the attempt is recorded as “Rate limited”.
• Old connection attempts are cleaned up. Apps that registered but never finished connecting are removed automatically after a few days.

Glossary

• AI assistant: an app such as Claude or ChatGPT that answers questions in plain language.
• Connector: the setting in Claude or ChatGPT that links the assistant to an outside service, here CreaRack.
• MCP (Model Context Protocol): the open standard that assistants use to talk to services like CreaRack.
• Snapshot: the last full reading CreaRack took of a device (for example the list of WiFi clients), as opposed to the live figures it measures every few seconds.

Véase también

• [[crearack—settings—user-management]]
• [[crearack—settings—mfa-and-login-security]]
• [[crearack—wireless—groups-and-reports]]
• [[crearack-tech—backend—mcp-server]]