Connect Arpuro to Claude, ChatGPT or any other MCP-aware tool.
The Arpuro MCP server is switched off for new organisations. It is free to enable — there is no extra licence and no added cost. Email support@arpuro.io from your work address, tell us your organisation name, and we will turn it on for you.
You need three things:
https://mcp.arpuro.io
If your company runs its own Arpuro platform, use https://mcp.<company>.arpuro.io instead, where <company> is your company's identifier.
There is no API key to copy and no separate password. Every client signs in through a standard OAuth flow against your Arpuro account, so you keep the roles and site permissions you already have — a user who cannot see a site in the platform cannot see it through the connector either. Access is read-only: the model can query measurements, locations, sites and exposure limits, and it cannot change anything.
https://mcp.arpuro.io as the remote MCP server URL and click Add. Leave the advanced OAuth fields empty — the connector supplies its own. On Team and Enterprise plans an owner adds the connector once for the whole organisation, and each member then connects their own account to it.
https://mcp.arpuro.io and click Add. From the terminal, add the server once and authenticate in the browser window that opens:
claude mcp add --transport http arpuro https://mcp.arpuro.io
In a conversation, use the + button below the message box to choose which connectors that chat may use. Claude will not reach for Arpuro data unless the connector is switched on for the conversation.
Custom MCP connectors in ChatGPT live behind developer mode, which is available on Plus, Pro, Business, Enterprise and Education accounts, on the web. On Business and Enterprise workspaces an admin must first allow it under Workspace settings → Permissions & roles.
https://mcp.arpuro.io as the MCP server URL. ChatGPT picks tools more reliably when you name the source. "Ask Arpuro for last month's respirable dust at the tapping floor" beats "what was the dust last month".
MCP is an open standard, so anything that speaks it can use the same URL and the same OAuth sign-in — Cursor, Copilot, n8n, or a client you write yourself. Consult that client's own documentation for where to paste a remote MCP server URL; there is nothing Arpuro-specific to configure beyond https://mcp.arpuro.io. If you get a client working that is not listed here, tell us and we will document it.
On Claude Team and Enterprise, and on ChatGPT Business and Enterprise, an owner or admin has to add or permit the connector before members can see it. Check with whoever administers your workspace before assuming the URL is wrong.
Make sure you are signing in with the Arpuro account that belongs to the enabled organisation — a personal account, or one from another organisation, will authenticate and then have nothing to read. Blocked pop-ups also break the OAuth window; allow them for the client and try again.
That is the signature of an account whose organisation has not been enabled, or of a user without permission to the sites being asked about. Confirm you can see the same sites in the platform; if you can and the connector still returns nothing, send us the question you asked.
Models can misread a question even when the data is correct. Ask it to show which sites, locations and time range it used — every answer is reproducible against the platform. Report anything that still disagrees; the connector is read-only, so no answer can have changed your data.
Still stuck? Email support@arpuro.io or see the support page.
Use of the Arpuro MCP Server is governed by the MCP Server Terms of Service.