Skip to main content

Connecting to the OneIQ MCP

How to connect to the OneIQ MCP so you can access OneIQ data directly inside your AI assistant.

Written by Omega Team

OneIQ can now be connected directly to AI assistants like Claude and ChatGPT using a secure, read-only connector. Once connected, you can ask your assistant to pull in OneIQ data as part of your conversation, without leaving the chat.

Setup takes about a minute and works a little differently depending on which assistant you use. Find your tool below.

Jump to:

Requirements

  • A OneIQ account with an active login to the OneIQ platform

  • Claude - Free, Pro, Max, Team, or Enterprise plans

  • ChatGPT - Plus (web only), Pro, Business, Enterprise and Edu)

  • Microsoft 365 Copilot - A Microsoft 365 Copilot licence

  • Copilot Studio - A Copilot Studio licence (or an active trial) and maker permissions in your Power Platform environment along with a Microsoft 365 Copilot licence

  • Grok - A Grok account

  • Grok Bot - A Grok account on a Premium plan or higher, or a seat on a Grok Business plan

  • Muse - A Meta account

  • The connector URL: https://mcp.oneiq.com

Claude

OneIQ is available as a connector in the Claude directory.

Free, Pro and Max plans

  1. Go to Settings > Connectors

  2. Click the Discover tab

  3. Search for oneiq

  4. Under More you can add, select OneIQ (by OneIQ Corp.)

  5. On the OneIQ page, click Connect to Claude
    ​


    ​

  6. This will redirect you to OneIQ to log in (if needed) and authorize access (see What happens next (all plans) below). Click Allow to finish connecting and keep the offline access permission checked if desired.

Team and Enterprise plans

An Owner adds the connector once, org-wide (Organization settings is only visible to Owners):

  1. Navigate to Organization settings > Connectors

  2. Click Browse connectors at the bottom of the page

  3. Select OneIQ and click Add to your team

Each member then connects individually:

  1. Go to Settings > Connectors

  2. Select OneIQ

  3. Click Connect to authenticate

  4. This will redirect you to OneIQ to log in (if needed) and authorize access (see What happens next (all plans) below). Click Allow to finish connecting and keep the offline access permission checked if desired.

If your Owner hasn't added OneIQ yet, you can find it in the directory and click Request to ask them to add it.

What happens next (all plans)

After clicking Connect, Claude will redirect you to OneIQ. If you're not already logged in to the OneIQ platform, you'll be asked to log in first.


​
​

You'll then see a consent screen asking you to authorize Claude to access OneIQ on your behalf, in read-only mode. Click Allow, and you'll be redirected back to Claude with the connector active.

AI generated image


​

On this consent screen you'll also see a checkbox for Maintain access to your account so it can continue working even when you're not using it. OneIQ's connector now advertises support for offline access (i.e. refresh token), so most clients request it and the box is checked by default. Leaving it checked means your connection can keep working beyond your current sign-in session, without needing to be re-authorized.
​
If you'd rather limit access to just this session, uncheck the box before clicking Allow — without offline access, your connection stays tied to your current session, which lasts 7 days before you'll need to sign in again.

You don't need to fill in any OAuth Client ID or Secret fields — authentication is handled automatically once you log in.

Once connected, you can enable OneIQ for a specific conversation via the "+" button in the lower left of the chat box, then Connectors.
​

Optional: Set tool permissions

Once connected, you can control how much autonomy Claude has when using OneIQ's tools. Go to Settings > Connectors, then select OneIQ.

Under Tool permissions, you'll see the list of OneIQ tools available to you (e.g. Find cloud instance, Get exchange rate, Query datasource, and others). For each tool — or for all of them at once via the "Other tools" group — you can choose:

  • Always allow (check icon) — Claude can use the tool without asking first

  • Needs approval (hand icon) — Claude will ask before each use (this is the default)

  • Never allow (blocked icon) — Claude cannot use the tool at all

This lets you decide, for example, whether Claude should be able to query OneIQ data sources automatically, or should check with you before running each query.


​
​

Optional: Set up a OneIQ project

A Claude project lets you give Claude standing instructions for every chat inside it. We recommend creating a OneIQ project with the instructions below. Claude will then answer only from your OneIQ data, tell you which environment and time window each answer comes from, and say so when a question is outside what OneIQ covers.

  1. In Claude, click Projects in the left sidebar

  2. Click + New Project, enter a name (e.g. "OneIQ") and create the project

  3. Click Set project instructions

  4. Copy the instructions below and paste them in

  5. Replace each [Your environment name] with the name of your environment as it appears in the OneIQ portal

  6. Click Save instructions

  7. Start your OneIQ chats from inside this project, with the OneIQ connector enabled

Finding your environment ID

Open your environment in the OneIQ portal (my.oneiq.com). The environment ID is the part of the address between ~/ and /overview, for example: my.oneiq.com/~/3r6gqy8d8f8ntdjg13inyc6hpy/overview. You can give Claude the ID, the environment's name, or simply paste the whole URL.


​

Project instructions

ROLE
You are the OneIQ assistant. You answer infrastructure questions (VMs, hosts, clusters, storage, utilization, sizing, cloud instances, pricing and exchange rates) using the OneIQ connector. The default environment is [Your environment name].

SOURCES, IN ORDER OF AUTHORITY
1. The OneIQ connector. It is the only source for infrastructure facts: counts, names, specs, utilization, prices, rates and recommendations. If OneIQ can't answer, say so. Never fill the gap from memory or another source.
2. Context I give you in this conversation, such as pasted text, an attached file, notes or goals. Use it to decide what to ask OneIQ and how to frame the results. It never supplies infrastructure numbers. If it states one (e.g. "we run about 60 VMs"), treat that as a claim to check against OneIQ. If the two disagree, show both and say where each came from.
3. Nothing else. Don't use web search or other connectors to find infrastructure facts, even if something there looks relevant. If another document would help, ask me for it.
You may explain general terms (what a vCPU or a datastore is), but never use general knowledge to supply a number, price, spec or fact about an environment.

CHOOSING THE ENVIRONMENT
- Use [Your environment name] unless I name a different one. When I do, use mine for that question and the ones after it, until I switch again.
- I can name an environment by its name, by its ID (a string like 3r6gqy8d8f8ntdjg13inyc6hpy), or by pasting its URL from the OneIQ portal. If I paste a URL, pull the ID out of it yourself.
- Whichever I give, confirm it against list_datasources and refer to it by the Name OneIQ returns. If it matches nothing, or matches more than one, list the possible matches by name and ask which one I mean.
- Always say which environment an answer comes from when it isn't [Your environment name].

WORKING WITH ONEIQ
- Start each session with list_datasources. If the connector errors or asks for sign-in, stop and tell me; reconnecting it in Settings usually fixes an expired sign-in.
- Call get_datasource_summary before query_datasource, and again whenever the environment changes.
- Questions about an environment go to query_datasource. Reference facts go to find_processor, find_cloud_instance, recommend_cloud_instance, get_instance_price and get_exchange_rate. Never present reference figures as measurements from an environment.
- Ask one clearly scoped question per call, naming the statistic, time window and unit. Check that what comes back matches what you asked. Don't show query text unless I ask for it.
- If OneIQ refuses a query, read what the refusal says is available and rephrase once. If it still can't answer, tell me.

GROUND EVERY ANSWER
- Report figures as OneIQ returns them. Never estimate or fill in missing values.
- Say what each answer is based on: which entities, which time window, and which measure (peak, average or 95th percentile).
- If a result is empty or partial, or contradicts an earlier answer, say so plainly.

TIME AND HISTORY
[Your environment name] runs on OneIQ's rolling 7-day collection interval. For performance and utilization questions, default to the most recent 7-day window unless I name a different one, and always state the window you used. If I ask about a period OneIQ doesn't return results for, say so rather than extrapolating.

WHAT'S OUTSIDE THE CONNECTOR
Through this connector, OneIQ does not cover network devices or network traffic, and it cannot see RPO/RTO, failover test results, replication lag, OS patch levels, open ports or CVE exposure. Hardware warranty dates are available only for some vendors. If I ask about any of these, say it's outside what the connector provides rather than estimating.

OUTPUT
Lead with the answer, then the supporting detail. Use tables when comparing several entities, and offer a chart when a trend or distribution would be clearer. Keep answers in the chat unless I ask for a file.

Using these instructions with other AI tools

These instructions aren't specific to Claude. You can use the same text with most other AI tools that support the OneIQ connector:

  • ChatGPT: add them as project instructions in a ChatGPT project

  • Microsoft Copilot Studio: paste them into your agent's Instructions field

  • Grok: add them as Custom Instructions

  • OpenAI Codex, Google Antigravity and Claude Code: save them in an AGENTS.md file (or CLAUDE.md for Claude Code)

Wherever you use them, replace [Your environment name] with your environment's name.

Claude Code

For instructions on configuring Claude Code, please click here.

ChatGPT

In ChatGPT, this feature is called a Plugin rather than a connector, but the flow is the same.

  1. Launch the ChatGPT Desktop app or login to chatgpt.com

  2. In the sidebar and select Plugins (under "More" if it's not shown directly)
    ​

  3. [ChatGPT Desktop] On the Plugins page, first click on "Browse Directory"
    ​


    ​[ChatGPT Web] On the plugins page, click on + and then click on Add custom MCP server


    ​

  4. [ChatGPT Desktop] Next, click on the Add button in the top right and select Create MCP App
    ​


    ​[ChatGPT Web] Click on Create MCP App
    ​


    ​

  5. In the Create MCP App dialog, enter a Name (e.g. "OneIQ"). Leave the icon and description optional

  6. Under Connection, keep Server URL selected and enter https://mcp.oneiq.com

  7. Leave Authentication set to OAuth — no manual credentials are needed.

  8. Click on Advanced OAuth settings to bring up the advanced settings

  9. Under Scopes (optional, one per line) enter the following scopes:

    1. mcp_user (this may already be checked as a default scope)

    2. offline_access

  10. Check "I understand and want to continue"

  11. Click Create

  12. After clicking Create, ChatGPT will first ask you to continue to confirm that you want to add the OneIQ MCP.

  13. Click on Continue to OneIQ MCP. This will redirect you to OneIQ to log in (if needed) and authorize access — the same as the Claude flow above (see What happens next (all plans)). Click Allow to finish connecting and keep the offline access permission checked if desired.
    ​

Microsoft 365 Copilot

OneIQ ICG is a Microsoft 365 Copilot connector, available in Microsoft 365 Copilot Chat. Once connected, Copilot Chat (and the Researcher agent) can query your OneIQ environments whenever a question calls for infrastructure data. You don't need to pick an agent or type a command, just ask.

Before you start

  • A Microsoft 365 Copilot licence

  • A OneIQ account with access to at least one environment (sign up at oneiq.com if you don't have one)

  • Your Microsoft 365 administrator hasn't turned off agents and plugins built by Microsoft (they're on by default). If OneIQ ICG doesn't appear in step 3, see Troubleshooting

Connect OneIQ ICG

  1. Open the Microsoft 365 Copilot desktop app, or go to m365.cloud.microsoft/chat in your browser

  2. Click the ... (More options) button in the top-right corner and select Settings

  3. In the left-hand menu, click Sources, then search for OneIQ. The OneIQ ICG connector should be listed. Click Connect.

  4. In the Connect to OneIQ ICG dialog, click Continue to OneIQ ICG

  5. A OneIQ window opens. Sign in with your OneIQ account and click Allow to authorize access. This is the same flow used for Claude and ChatGPT (see What happens next (all plans))

  6. Back in Sources, OneIQ ICG now shows as connected (the Connect button is gone; opening the entry shows Disconnect)

  7. Click New chat and ask a question, for example: "Using OneIQ ICG, which OneIQ environments can I access?" Copilot calls OneIQ and cites it in the answer (the OneIQ icon next to the text)

Note: Naming OneIQ ICG in your question helps Copilot pick the right source, especially in the first message of a chat. You can also name the environment, paste its environment ID (see Finding your environment ID), or paste its OneIQ portal URL.

Using OneIQ ICG in Researcher

In the Researcher agent, open Sources in the prompt box and select OneIQ ICG so that deep-research reports draw on your environment data.

What the connector can do

OneIQ ICG reads your OneIQ environments (VMs, hosts, clusters, storage, utilization) and OneIQ reference data (processors, cloud instance specifications and prices, exchange rates, compute-only cloud sizing recommendations). It has one write action: the problem-reporting tool, which files feedback about a query with the OneIQ team. Copilot asks for your approval before using it.

For Microsoft 365 administrators

OneIQ ICG is a pre-enabled connector: it is provisioned into every tenant automatically, so there is nothing to add from the connector Gallery. You can see and manage it in the Microsoft 365 admin center under Copilot > Connectors > Your Connections.

From this panel you can limit who sees it (Staged rollout > Change) or turn it off for your organization (Enable/disable this source for users). Users can only connect it if Allow agents and plugins built by Microsoft is on under Copilot > Settings > Agent and plugin access.

The public listing is on Microsoft Marketplace: OneIQ ICG (WA200012465).

Microsoft Copilot Studio

If you'd rather build your own agent in Copilot Studio, please click here for instructions.

Grok

  1. Log in to Grok and go to Plugins in the left navbar
    ​

  2. Click New Connector in the top right corner
    ​


    ​

  3. Click + Custom to add your own custom connector
    ​

  4. Enter a name for your connector (e.g. "OneIQ MCP") and enter https://mcp.oneiq.com for the Server URL, then click Add Connector
    ​

    ​
    ​

  5. This will redirect you to OneIQ to log in (if needed) and authorize access — the same as the Claude flow above (see What happens next (all plans)). Click Allow to finish connecting and keep the offline access permission checked if desired.
    ​

Grok Bot

For instructions on configuring Grok Bot (team and individual accounts), please click here.

Muse (Meta AI)

Muse sets up the connection from the chat itself, so there's no separate settings page to fill in.

  1. Log in to Muse and start a new chat
    ​

  2. Ask Muse to connect to the OneIQ MCP Server, for example: "Can you create a connection to the OneIQ MCP Server at https://mcp.oneiq.com?"
    ​

  3. Muse will reply with a short explanation of how the connection works and show an Oneiq Connector card. Click Connect on the card
    ​


    ​

  4. A Custom connector dialog appears, noting that Meta doesn't review custom connectors. Click Connect to continue
    ​


    ​

  5. This will redirect you to OneIQ to log in (if needed) and authorize access — the same as the Claude flow above (see What happens next (all plans)). Click Allow to finish connecting and keep the offline access permission checked if desired.
    ​

    AI generated image


    ​

  6. You'll be redirected back to Muse, which will confirm that OneIQ is connected. You can then ask Muse to list your data sources, summarize one, or look up cloud instance and processor reference data
    ​

You can disconnect OneIQ from Muse at any time in Muse's Settings.
​

OpenAI Codex

For instructions on configuring Codex, please click here.

Google Antigravity

For instructions on configuring Google Antigravity (and Antigravity CLI), please click here.

Troubleshooting

I don't see the OneIQ connector under Organization settings (Claude Team/Enterprise)

Only Owners can add connectors org-wide. Ask your Claude Owner to add OneIQ from Organization settings > Connectors > Browse connectors, or click Request on the OneIQ connector in the directory. Then connect to it yourself from Settings > Connectors.

OneIQ ICG doesn't appear in Microsoft 365 Copilot Sources

Ask your Microsoft 365 administrator to check that Allow agents and plugins built by Microsoft is turned on under Copilot > Settings > Agent and plugin access, and that OneIQ ICG is enabled for you under Copilot > Connectors > Your Connections.

I'm stuck on the OneIQ login or authorization screen

Make sure you're logging in with your OneIQ account credentials, not your Claude, ChatGPT, Microsoft or Meta credentials. If the issue persists, contact your OneIQ administrator.

Have questions or run into an issue not covered here? Let us know! 🙂

Did this answer your question?