API & Integrations
Drive NetCrunch from outside the console - the REST API for nodes, views, monitoring packs and credentials, and the MCP server that exposes the same operations to AI tools.
In this chapter
- Getting StartedLearn how to create a NetCrunch API key and use it with both REST API and MCP Server access channels.
- NodesNodes API gives many possibilities to access, modify, add, and remove node data from NetCrunch. It can be used to manage NetCrunch through scripts and external applications.
- Atlas Views and FoldersViews and Folders API allows us to add, remove, access, and retrieve Folders and Views data in NetCrunch.
- Monitoring Packs And Map PoliciesMonitoring Packs and Map Policies API allows us to get and set various properties of Monitoring Packs and Map Policies; additionally, it can be used to get a list of nodes that are using monitoring pack or policy and modify such list by adding and removing nodes.
- CredentialsCredentials API allows to get information and remove credentials in NetCrunch
- NotesNotes API allows to add, edit, retrieve, and archive notes
- Data Properties ReferenceFind a reference to all NetCrunch object properties exposed through API
- REST API Use CasesUse NetCrunch REST API to automate repeatable administration tasks, including maintenance mode, node import, custom field updates, and monitoring provider assignment.
- MCP and AI-Compatible AutomationUse the NetCrunch MCP Server to connect MCP-compatible tools to selected NetCrunch management operations. MCP is intended for controlled automation and assistant-assisted administration, not for unrestricted data discovery or building external monitoring systems on top of NetCrunch.
- REST API ReferenceList below contains all requests currently available in REST API, divided into scopes
- NetCrunch MCP ServerNetCrunch exposes its REST API as an [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server, allowing AI assistants and LLM-based tools to discover and call the NetCrunch management API programmatically.