Huntress API MCP Server

What is Huntress API MCP Server?

The Huntress API MCP Server is a Model Context Protocol server that provides tools for interacting with the Huntress API. It enables programmatic access to Huntress functionality including account management, organization management, agent management, incident reports, summary reports, and billing reports. It is designed for developers and security teams using Huntress.

How to use Huntress API MCP Server?

Clone the repository, install dependencies with npm install, create a .env file with your Huntress API key and secret, then build the server with npm run build. Configure it in your MCP settings by adding a huntress entry with the command node, the path to the built index.js, and the required environment variables.

Key features of Huntress API MCP Server

• Account information retrieval
• Organization management
• Agent management and monitoring
• Incident report access
• Summary and billing report generation
• Built‑in rate limiting (60 requests/minute)

Use cases of Huntress API MCP Server

• Retrieve account and organization details for auditing.
• Monitor and manage agents across your Huntress environment.
• Access incident reports for threat analysis and investigation.
• Generate summary reports for security reviews.
• Obtain billing reports for financial tracking.

FAQ from Huntress API MCP Server

What is the rate limit for API requests?

The server enforces Huntress’s rate limit of 60 requests per minute on a sliding window—no more than 60 requests within any 60‑second period.

How do I obtain Huntress API credentials?

Obtain your API Key and API Secret Key from your Huntress account at <your_account_subdomain>.huntress.io under API Credentials.

What tools are available in the server?

Tools include get_account_info, list_organizations, get_organization, list_agents, get_agent, list_incident_reports, get_incident_report, list_summary_reports, get_summary_report, list_billing_reports, and get_billing_report.

What runtime and dependencies are required?

The server requires Node.js and uses npm for dependency management. It is built with TypeScript and compiled to JavaScript.

How does the server handle errors?

It handles invalid API credentials, rate limit exceeded, invalid request parameters, and API response errors with appropriate error messages.