AI Connectors.
Ask Claude, ChatGPT or Copilot about your maintenance.
Connect the AI tool your team already uses to yCloudx. Ask in plain language which assets broke down most, which PMs are overdue, what is low in stock or which licences expire soon, and get answers from your own yCloudx records. Read only, and each person sees only what they can already see.
- Signed in as this user
- Only their sites
- Only their modules
- Shared by the admin
- Read only
Ask a question. Get an answer from yCloudx.
Connect Claude, ChatGPT, Copilot or another AI tool that supports MCP connectors, then ask about your maintenance in plain language: which assets broke down most, which PMs are due, what is low in stock, which licences expire soon. It is read only, and each person sees only what they can already see in yCloudx.
Your admin decides
Switch AI tools on for your organisation and choose what they may read. Try switching one off, then ask about it.
AI tools can read, never add, change or delete records.
Each question runs as that user: only their sites, and only the modules they have in yCloudx.
Access is re-read from the database on every question, so changes apply immediately.
Each person connects with their own yCloudx login, using OAuth with PKCE. No shared passwords or keys.
Codes work once. Reusing an old token cuts off the whole connection.
A yCloudx screen shows who you are signed in as and what the tool will read, before you allow it.
Turn AI tools on or off and choose which data they may read, from assets and work orders to licences and failure risk.
Users can disconnect in their AI tool, or ask the admin to remove access.
Illustrative conversation with sample data. Answers come from the records each user can access in yCloudx. Check AI answers before acting on them.
Set up once. Then just ask.
Your admin switches AI tools on and chooses which data they may read. Each person then connects their own AI tool with their own yCloudx login.
Admin turns it on
Allow AI connectors for your organisation and choose what they may read: assets, corrective and preventive work orders, spare parts, licences, bookings and failure risk.
User connects and approves
Add yCloudx as a connector in Claude, ChatGPT, Copilot or another MCP-compatible tool. A yCloudx screen shows who you are signed in as and what the tool will read, before you allow it.
Ask in plain language
Ask questions the way you would ask a colleague. Answers come from the yCloudx records you can access, with work order and asset numbers so you can find them in yCloudx.
Questions your team asks every day.
Whatever your admin shares, your AI tool can look up, count, rank and summarise.
Breakdowns and corrective work
Open jobs, response times and the assets that keep failing.
Which assets broke down most this quarter?
Preventive maintenance
PMs due, overdue and completed, by site, team or asset.
Which PMs are overdue by more than a week?
Assets and their history
Where an asset is, its details and everything done to it.
Show me the history of chiller CH-02.
Spare parts and stock
What is low, what is out and where parts are used.
Which spare parts are below minimum stock?
Licences and bookings
Certificates and permits about to expire, and upcoming bookings.
Which licences expire in the next 30 days?
Failure risk
The assets Cloudy Predict rates most likely to fail, and why.
Which assets have the highest failure risk?
Two ways to use AI with yCloudx.
Use either, or both. Many teams use Cloudy inside yCloudx for daily work, and their own AI tool when they are already working there.
Cloudy AI
- Works inside yCloudx, on web and mobile
- Fills in forms from text, voice, photos and documents
- Answers questions and predicts failures
- Cloudy Agents check your data on a schedule
AI Connectors
- Works inside Claude, ChatGPT, Copilot or another MCP-compatible tool
- Ask about yCloudx alongside your other work in that tool
- Read only, with each user's own access
- Your admin chooses what is shared
Answers from across yCloudx.
AI Connectors questions
What are yCloudx AI Connectors?
AI Connectors let you connect an AI tool such as Claude, ChatGPT or Copilot to yCloudx, so you can ask questions about your maintenance data in plain language and get answers from your own yCloudx records.
Which AI tools can I use?
Claude, ChatGPT, Copilot and other AI tools that support MCP (Model Context Protocol) connectors. Whether connectors are available can depend on the AI tool and the plan you use with it.
Can the AI tool change anything in yCloudx?
No. AI Connectors are read only. The AI tool can look up, count and summarise records, but it cannot add, change or delete anything.
Who can see what?
Each question runs as the person who asked it. They see only their own sites and only the modules they have in yCloudx. Access is checked again on every question, so if a user's access changes, it applies immediately.
How do users sign in?
Each person connects with their own yCloudx login using OAuth with PKCE, and approves the connection on a yCloudx screen that shows what the tool will read. There are no shared passwords or keys. Sign-in codes work only once, and reusing an old token cuts off the whole connection.
Can our admin control it?
Yes. Your admin can turn AI connectors on or off for your organisation and choose which data AI tools may read, such as assets, work orders, spare parts, licences, bookings and failure risk. Users can disconnect at any time.
Is this the same as Cloudy AI?
No. Cloudy AI is built into yCloudx. AI Connectors let you use your own AI tool with yCloudx data. You can use either, or both.
Should we check the answers?
Yes. Answers come from your yCloudx records, and they include work order and asset numbers so you can check them in yCloudx before acting on them.
Ask your yCloudx data a question.
Book a demo and we will show you AI Connectors working with Claude, ChatGPT or Copilot.
