Connect NetZen to Claude and ChatGPT

NetZen offers a remote MCP (Model Context Protocol) server so people can work in NetZen from Claude, ChatGPT and other AI apps that support MCP. Each person connects with their own NetZen sign-in, so the AI app has exactly the access their NetZen role allows: nothing more, and nothing it can keep after the connection is revoked.

You need a NetZen account. Start a free 30-day trial at netzenai.com, no card required, or ask your administrator for an invitation. If you are starting a new organization, finish or skip its onboarding tour before connecting.

Connect from Claude

• From the directory: open the NetZen listing in Claude and press Connect. On a Team or Enterprise plan an Owner can also add it under Organization settings, Connectors, Add, Custom, with the server URL https://app.netzenai.com/netzenMcp and the OAuth fields left empty.
• NetZen's sign-in page opens. Sign in, choose your organization if you belong to several, and press Allow access on the consent page. You return to claude.ai.
• In a chat, turn NetZen on from the connectors menu and ask in plain language, for example "What is waiting on me in NetZen today?".
• After a role change or a NetZen update, refresh the connector's tool list from its menu in Claude.

Connect from ChatGPT

• Open Plugins, add a custom MCP server with the URL https://app.netzenai.com/netzenMcp and choose OAuth. Your workspace policy decides whether custom MCP servers are available.
• Sign in to NetZen when prompted, then select NetZen in a new chat.
• After a role change or a NetZen update, open NetZen under Plugins and press Refresh tools, then start a new chat.

What each role can do

• Administrators and owners get the whole desk: tickets, devices, patching, automations and authoring, reports, client billing and projects.
• Technicians work their queue: find and open tickets, reply, add private notes, change status and priority, log time, check devices and patches, and run approved automations.
• Site managers see the shared computers at their sites and can open tickets about them.
• Employees get self-service support: open a ticket, answer the help desk's questions, and close the ticket once it is fixed.

Every tool call checks the person's current permissions, client and site scope. Connecting never grants a broader role, and administrators can see and revoke every active connection under Settings, Connect AI.

Tools

• Find ticket, Get ticket, Create ticket, Reply to ticket, Update ticket. Your own tickets, or every ticket your role covers. Technicians can reply publicly or as a private note, change status and priority, and link devices.
• Answer form, Find approvals, Decide approval. Forms the help desk sent you, and approvals waiting on you. Approvals are decided only from the approval card, never by the AI on its own.
• Log time. Technicians record completed time against a ticket, at least 0.1 hours.
• Find devices, Get device. Devices you can see, with live status, operating system and disk use.
• Patch status, Find missing patches. Devices behind on updates and the updates they are missing, actively exploited ones first.
• Run <automation>, one tool per automation you may run. Each enabled automation is its own tool with its own inputs, for example Run System Information or Run Install Patches. The tool proposes the run; a person starts it from the Run card. Nothing runs until they press Run.
• Get automation run. The result of a run you started, including the device output.
• Authoring guide, List drafts, Get draft, Create automation, Save draft. Automation authors can have the AI draft PowerShell, Bash or Microsoft 365 automations. Drafts are never published from the AI app; a person tests and publishes them in NetZen.
• Desk summary, SLA report, Find support agents. Active work by status and technician, unassigned tickets, SLA due dates and breaches, and the staff directory for people with member-management permission.
• Find clients, Find people, Search knowledge base. Clients, sites and people as your role covers, and knowledge base articles the help desk can answer from.
• Find and get invoices, agreements, quotes, purchase orders. Read existing client billing records as your billing permissions allow. Client roles see sent records in their scope, never drafts.
• Find project, Get project, Create project, Update project, Add project task. Projects and their progress in scope. Staff with project-management permission can create projects and their task tickets.

Approvals, forms and runs stay with people

In Claude and ChatGPT, approvals, help desk forms and proposed automation runs appear as cards in the conversation: Approve or Reject, fields to fill, and Run or Don't run. Cards expire after 10 minutes. The AI can propose an automation run but cannot start it; only a person pressing Run does. The AI cannot approve or reject approvals. Password fields open in the NetZen portal, so passwords and other secrets never pass through the chat.

A new ticket or reply from an employee starts NetZen's help desk AI, which investigates, proposes fixes and hands off to a technician when it cannot resolve the issue. A ticket created by staff goes to the desk queue. Creating a ticket sends the usual desk notifications.

Data handling

Ticket text, device details and other records you ask the tools for are returned to the connected AI app, so use your organization's approved AI workspace and share only what the task needs. Do not enter passwords, authentication codes, payment card details, government identifiers or protected health information in the conversation. NetZen keeps an audit trail of each connection and each call, under the person who made it. How NetZen handles customer data is described in the Privacy Policy.

Support

Questions about the connector go to support@netzenai.com. Signed-in customers find the full product documentation at docs.netzenai.com.