Netverge + Model Context Protocol
Run your IT from your own AI.
Connect an MCP-compatible assistant to Netverge. Work with monitoring events, tickets, documents and the client context behind them, from the AI you choose.
Available tools and actions depend on your account permissions and assistant configuration. Confirm compatibility and access before connecting.
Your assistant, connected to operational records.
MCP gives an assistant a defined set of tools. Netverge supplies the IT records those tools work with: clients, sites, services, assets, tickets, events and documents.
Use the assistant to gather evidence and prepare the next step. When a change is needed, review the target and effect, then use the permitted action. Artemis agents remain available inside Netverge.
Three practical places to start
These are example requests for supported tool categories, not transcripts or claims about a customer's results. Review the returned records before acting.
01
Investigate an event before changing anything
Read this event and its action history. Summarize the affected client, service and asset, and tell me what still needs checking. Do not change its status.
Netverge's event tools return the event and its related client, service and asset names. Requesting the action history gives your assistant the recorded steps, so its summary can distinguish the evidence from a suggested next action.
02
Prepare a ticket handoff with the context attached
Read this ticket and the related records. Summarize the problem, current owner and next step. Show me the proposed update before making a change.
Ticket tools expose the category, assigned contributors, linked entities and merged-ticket relationships. The assistant can use those records to prepare a handoff. Authorized write tools can update the priority, status or assignments when you choose to proceed.
03
Find the documentation for a client
Find the documents for this client about the affected service. List the matching records and identify any information we still need to verify.
Document search can filter by client and match document names, tags and templates. Connected client, location, service and asset records help your assistant find the relevant operational context instead of relying on a generic answer.
Put safeguards around the workflow
Use these operating practices alongside your organization's access controls and the assistant's approval settings.
Start with read-only work
Begin with searches, record lookups and summaries. Review the tools and permissions available to the connected assistant before enabling changes. A prompt asking for approval is useful guidance, but it is not a substitute for access controls.
Check the effect of each write
Confirm the exact record and intended change. Closing a Netverge ticket also resolves its linked events. Sending a message, changing a sensor and closing a ticket are separate decisions, even when they are part of one investigation.
Use bounded changes and previews
Temporary sensor monitoring supports an expiry time and restores the baseline on expiry or revert. Report previews and workflow test runs support dry-run mode. Use those options where they fit, then inspect the result before a live action.
Review the record after acting
Read the updated ticket or event and its available history to confirm what happened. Keep customer communications tied to the approved recipient and content. Share only the operational data the chosen assistant is authorized to receive.
Frequently asked questions
What is Netverge MCP?
MCP stands for Model Context Protocol. Netverge exposes tools that a compatible AI assistant can use to read operational records and carry out supported actions. The tools connect the assistant to monitoring, ticketing, documentation and related IT context.
Do I need to replace Artemis to use my own AI?
No. Artemis is Netverge's in-platform agent system. MCP is a way to work with Netverge from your own compatible assistant. They are different entry points to operational work and can be used alongside each other.
Can every assistant perform every Netverge action?
No. Compatibility, available tools and permissions depend on the assistant, its configuration and the connected Netverge account. Confirm the tools and access available in your setup before planning a workflow.
Does MCP automatically require approval for every change?
MCP itself does not guarantee a human approval step for every tool call. Configure the assistant's approval behavior and account permissions for your workflow. Review consequential actions and their effects before allowing them.
Start with one real IT question.
Choose a ticket, event or documentation lookup. Confirm assistant compatibility and permissions, test a read-only request, then decide which actions your team wants to allow.