Connect Claude to Netos

The Netos connector lets Claude work with your network estate in Netos: inventory, lifecycle and end-of-life exposure, contracts and renewals, and reviewed data imports. Claude works as you, with your Netos permissions, on your own Netos environment.

What you need

  • A Netos account that can already sign in to your environment in a browser.
  • Your server URL, for example https://uks001.app.netos.io/example/production/mcp. See Find your server URL.
  • Access to the Netos tables you want to ask about. See Groups and permissions.
  • On a Claude Team or Enterprise plan, an Owner may need to add the connector for your organization first. See For Claude Team and Enterprise Owners.

Steps

  1. In Claude, open Customize > Connectors.
  2. Add the Netos connector and enter your server URL when Claude asks for it.
  3. Select Connect. Claude opens your zone's sign-in page.
  4. Enter your work email and sign in. If your company uses Okta or Microsoft Entra ID, you continue there and complete MFA.
  5. Netos shows Authorize access. Check that it names https://claude.ai as the app you started from, then select Approve.
  6. Return to Claude. The connector shows as connected.

Try: "How many devices, sites and circuits do we have?" Claude answers from your environment and links to the Netos pages behind the answer.

Disconnecting

Open Customize > Connectors in Claude, select Netos and disconnect it. To stop access from your company's side, remove the user from their Netos groups in your sign-in.

Example

Maria is a network engineer at Example Corp. Her Netos environment is https://uks001.app.netos.io/example/production/.

  1. She adds the Netos connector in Claude with https://uks001.app.netos.io/example/production/mcp.
  2. She signs in with her Example Corp Okta account, checks that the page names https://claude.ai as the app she started from, and approves.
  3. She asks: "Which devices reach end of life in the next 12 months, by site and vendor?" Claude answers from her Netos environment.
  4. She asks Claude to stage a device spreadsheet for import. Claude stages it and returns a link to the run in Netos Atlas. Nothing is written until an approver approves it there.

For Claude Team and Enterprise Owners

Make the connector available to your people, with sign-in and access controlled by your own identity provider. This is for the Owner of your Claude plan and your Netos administrator, working together.

  • Netos needs no client ID or secret from you. Claude registers itself with your zone when a user connects.
  • Adding the connector grants no data access by itself. Each user signs in as themselves and gets only their own Netos table permissions.
  1. Netos administrator: set up sign-in and groups (Okta or Microsoft Entra ID), decide which groups may use each environment, and send Netos the groups and the access each should get.
  2. Claude Owner: in your organization's connector settings, add the Netos connector.
  3. Both: tell your people which server URL to use for each environment, for example https://uks001.app.netos.io/example/lab/mcp and https://uks001.app.netos.io/example/production/mcp.
  4. Each user connects with the steps above.

Test with three users: one in a linked group asks "How many devices do we have?" and gets an answer; one asks for a change and gets a review link; one without a table permission gets "Contact your administrator for access to <Table> ..." with a flow ID.

To remove the connector for everyone, the Claude Owner removes it from the organization.

Data and privacy

Netos processes your organization's data under your agreement with Netos. What you type in Claude is handled by Anthropic under your agreement with Anthropic. See the Netos Privacy Policy.