--- title: "Huntress MCP server for AI agents - actionlake" description: "Give Claude 102 Huntress actions through one MCP server: account agents, agents. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/huntress updated: 2026-10-22 --- Connectors · MSP & PSA # Huntress MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Huntress and the rest of your systems. It gives your agent 102 Huntress actions (62 reads, 30 writes and 10 that wait for a confirmation) and holds the Huntress credential itself, so the agent never does. It paces Huntress's limits and records every call. [Connect Huntress free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "huntress.organizations.list", intent: "check which Huntress account is connected" } # List Organizations · read · 1 upstream call ``` - 102 actions in one signed file - 62 read look, never change - 30 write create and update - 10 wait for a yes destructive, confirmed first Set up ## Connect Huntress in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Huntress. Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` Huntress API Key (public key): generate at [your_subdomain].huntress.io > API Credentials > Setup - `api_secret` Huntress API Secret Key (private key), shown once when the credential is created ``` account { op: "connections.requirements", service: "huntress" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "huntress.organizations.list" } # list organizations · read · 1 upstream call check { action: "huntress.organizations.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Huntress at a glance **Sign-in** Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` `api_secret` **Limits we pace to** 60 calls a minute, per connection **API covered** Huntress API v1 (Swagger 2.0, 102 operations)`api.huntress.io` **Built from** Huntress's documentation, read 22 October 2026[api.huntress.io](https://api.huntress.io/docs) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 61 of 62 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 4, so ask can line Huntress up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Huntress. 102 actions in 36 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **62** read look, never change - **30** write create and update - **10** destructive wait for a confirmation 1. ### Account agents 6 2 read · 2 write · 2 destructive Isolate Agent · List Agents · Get Agent · Update Agent 2. ### Agents 6 2 read · 2 write · 2 destructive List Agents · Get Agent · Update Agent · Uninstall Agent 3. ### Account incident report remediations 5 2 read · 3 write · 0 destructive Bulk Approve Remediations · Bulk Reject Remediations · Set Remediation Completion · List Remediations 4. ### Account memberships 5 2 read · 2 write · 1 destructive Create a Membership · List Memberships · Get Membership · Update a User's membership 5. ### Account organizations 5 2 read · 2 write · 1 destructive Create an Organization · List Organizations · Get Organization · Update an Organization 6. ### Accounts 5 2 read · 2 write · 1 destructive List Accounts · Create Account · Get Specific Account · Update Account 7. ### Incident report remediations 5 2 read · 3 write · 0 destructive Bulk Approve Remediations · Bulk Reject Remediations · Set Remediation Completion · List Remediations 8. ### Memberships 5 2 read · 2 write · 1 destructive Create a Membership · List Memberships · Get Membership · Update a User's membership **28 more areas · 60 actions** - Organizations **5** - Reseller subscriptions **5** - Unwanted access rules **5** - Account incident reports **3** - Escalations **3** - Incident reports **3** - Account external ports **2** - Account incident report comments **2** - Account invoices **2** - Account reports **2** - Account signals **2** - External ports **2** - Identities **2** - Incident report comments **2** - Invoices **2** - Platform actions **2** - Reports **2** - Reseller invoices **2** - Siem log sources **2** - Signals **2** - Account **1** - Account remote access connections **1** - Actor **1** - Known VPNS **1** - Remote access connections **1** - Reseller invoice account usage line items **1** - Reseller invoice organization usage line items **1** - Siem **1** Top actions ## The Huntress API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 30 of Huntress's 30 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `huntress.organizations.list` List Organizations | List Organizations. | read | `crm.company.list` 162 connectors | | `huntress.identities.list` List Identities | List Identities. | read | `identity.user.list` 474 connectors | | `huntress.organizations.create` Create an Organization | Create an Organization. | write | `crm.company.create` 142 connectors | | `huntress.agents.list` List Agents | List Agents. | read | `device.endpoint.list` 65 connectors | | `huntress.organizations.update` Update an Organization | Update an Organization. | write | `crm.company.update` 137 connectors | | `huntress.incident_reports.list` List Incident Reports | List Incident Reports. | read | `security.incident.list` 17 connectors | | `huntress.identities.get` Get Identity | Get Identity. | read | `identity.user.get` 399 connectors | | `huntress.organizations.delete` Delete an Organization | Delete an Organization. | destructive | `crm.company.delete` 119 connectors | | `huntress.signals.list` List Signals | List Signals. | read | `security.alert.list` 22 connectors | | `huntress.agents.get` Get Agent | Get Agent. | read | `device.endpoint.get` 57 connectors | | `huntress.incident_report_comments.list` List Incident Report Comments | List Incident Report Comments. | read | `security.incident_note.list` 9 connectors | | `huntress.incident_report_comments.create` Create an Incident Report Comment | Create an Incident Report Comment. | write | `security.incident_note.create` 8 connectors | Try it ## Prompts to paste into Claude. Each one names the Huntress actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Huntress alerts are open right now? Group them by service. calls `huntress.incident_reports.list` 2. Write write Create an Organization in Huntress. Show me exactly what you will send before you save it. calls `huntress.organizations.create` 3. Across systems read Which Huntress companies have invoices in NetSuite, and how many each? calls `huntress.organizations.list` `netsuite.views.invoices` Across your systems ## Huntress, joined to the rest of your business. One `ask` fetches from Huntress and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row. - Which Huntress companies have invoices in NetSuite, and how many each? `huntress.organizations.list` + `netsuite.views.invoices`, on `crm.company` · [NetSuite](https://actionlake.com/connectors/netsuite) - Which Huntress companies have tickets in HubSpot CRM, and how many each? `huntress.organizations.list` + `hubspot_crm.tickets.list`, on `crm.company` · [HubSpot CRM](https://actionlake.com/connectors/hubspot-crm) Also mapped by other connectors `identity.user` **517** `crm.company` **227** `device.endpoint` **69** `monitoring.alert` **56** ask ``` ask { intent: "which Huntress companies have invoices in NetSuite, and how many each", steps: [ { action: "huntress.organizations.list", as: "co", input: {}, limit: 100, max_pages: 5 }, { action: "netsuite.views.invoices", as: "inv", input: {}, limit: 100, max_pages: 5 }, { join: { left: "co", right: "inv", on: "crm.company", group_by: "co.name", select: ["co.name", "count(inv.id) as invoices"] } } ] } ``` Example. Run it through check first: it validates the steps and prices them, and it is free. Governance for Huntress ## Destructive actions wait for a yes. 10 Huntress actions are destructive. These are all of them: - Delete an Organization `huntress.organizations.delete` - Uninstall Agent `huntress.agents.uninstall` - Permanently Disable an Account `huntress.accounts.delete` - Delete Membership `huntress.memberships.delete` - Uninstall Agent `huntress.account_agents.uninstall` - Release Agent Isolation `huntress.agents.release_isolation` - Delete Membership `huntress.account_memberships.delete` - Delete an Organization `huntress.account_organizations.delete` - Delete Unwanted Access Rule `huntress.unwanted_access_rules.delete` - Release Agent Isolation `huntress.account_agents.release_isolation` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do huntress.organizations.delete confirm_policy: **human** Delete an Organization? **intent:** the user asked me to delete an Organization run suspended · waiting for a named person · key _huntress-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "huntress-agent", allowed_actions: ["huntress.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "huntress.organizations.delete", approver: "lead@example.com" }, { match: "huntress.agents.uninstall", approver: "lead@example.com" }, { match: "huntress.accounts.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Huntress only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Huntress costs on actionlake. Every Huntress action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Huntress refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 102 Huntress actions - 102 actions page each page of a long list is one call - 61 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Huntress action. 102 actions by area: the id your agent calls, what it does, and its effect. **Account agents 6** - `huntress.account_agents.get` Get Agent read - `huntress.account_agents.isolate` Isolate Agent write - `huntress.account_agents.list` List Agents read - `huntress.account_agents.release_isolation` Release Agent Isolation destructive - `huntress.account_agents.uninstall` Uninstall Agent destructive - `huntress.account_agents.update` Update Agent write **Agents 6** - `huntress.agents.get` Get Agent read - `huntress.agents.isolate` Isolate Agent write - `huntress.agents.list` List Agents read - `huntress.agents.release_isolation` Release Agent Isolation destructive - `huntress.agents.uninstall` Uninstall Agent destructive - `huntress.agents.update` Update Agent write **Account incident report remediations 5** - `huntress.account_incident_report_remediations.bulk_approve` Bulk Approve Remediations write - `huntress.account_incident_report_remediations.bulk_reject` Bulk Reject Remediations write - `huntress.account_incident_report_remediations.complete` Set Remediation Completion write - `huntress.account_incident_report_remediations.get` Get Remediation read - `huntress.account_incident_report_remediations.list` List Remediations read **Account memberships 5** - `huntress.account_memberships.create` Create a Membership write - `huntress.account_memberships.delete` Delete Membership destructive - `huntress.account_memberships.get` Get Membership read - `huntress.account_memberships.list` List Memberships read - `huntress.account_memberships.update` Update a User's membership write **Account organizations 5** - `huntress.account_organizations.create` Create an Organization write - `huntress.account_organizations.delete` Delete an Organization destructive - `huntress.account_organizations.get` Get Organization read - `huntress.account_organizations.list` List Organizations read - `huntress.account_organizations.update` Update an Organization write **Accounts 5** - `huntress.accounts.create` Create Account write - `huntress.accounts.delete` Permanently Disable an Account destructive - `huntress.accounts.get` Get Specific Account read - `huntress.accounts.list` List Accounts read - `huntress.accounts.update` Update Account write **Incident report remediations 5** - `huntress.incident_report_remediations.bulk_approve` Bulk Approve Remediations write - `huntress.incident_report_remediations.bulk_reject` Bulk Reject Remediations write - `huntress.incident_report_remediations.complete` Set Remediation Completion write - `huntress.incident_report_remediations.get` Get Remediation read - `huntress.incident_report_remediations.list` List Remediations read **Memberships 5** - `huntress.memberships.create` Create a Membership write - `huntress.memberships.delete` Delete Membership destructive - `huntress.memberships.get` Get Membership read - `huntress.memberships.list` List Memberships read - `huntress.memberships.update` Update a User's membership write **Organizations 5** - `huntress.organizations.create` Create an Organization write - `huntress.organizations.delete` Delete an Organization destructive - `huntress.organizations.get` Get Organization read - `huntress.organizations.list` List Organizations read - `huntress.organizations.update` Update an Organization write **Reseller subscriptions 5** - `huntress.reseller_subscriptions.create` Create Reseller Subscription write - `huntress.reseller_subscriptions.get` Get Reseller Subscription read - `huntress.reseller_subscriptions.list` List Reseller Subscriptions read - `huntress.reseller_subscriptions.update` Update Reseller Subscription write - `huntress.reseller_subscriptions.upgrade` Upgrade Reseller Subscription write **Unwanted access rules 5** - `huntress.unwanted_access_rules.create` Create an Unwanted Access Rule write - `huntress.unwanted_access_rules.delete` Delete Unwanted Access Rule destructive - `huntress.unwanted_access_rules.get` Get Unwanted Access Rule read - `huntress.unwanted_access_rules.list` List Unwanted Access Rules read - `huntress.unwanted_access_rules.update` Update an Unwanted Access Rule write **Account incident reports 3** - `huntress.account_incident_reports.get` Get Incident Report read - `huntress.account_incident_reports.list` List Incident Reports read - `huntress.account_incident_reports.resolve` Create an Incident Report Resolution write **Escalations 3** - `huntress.escalations.get` Get Escalation read - `huntress.escalations.list` List Escalations read - `huntress.escalations.resolve` Create an Escalation Resolution write **Incident reports 3** - `huntress.incident_reports.get` Get Incident Report read - `huntress.incident_reports.list` List Incident Reports read - `huntress.incident_reports.resolve` Create an Incident Report Resolution write **Account external ports 2** - `huntress.account_external_ports.get` Get External Port read - `huntress.account_external_ports.list` List External Ports read **Account incident report comments 2** - `huntress.account_incident_report_comments.create` Create an Incident Report Comment write - `huntress.account_incident_report_comments.list` List Incident Report Comments read **Account invoices 2** - `huntress.account_invoices.get` Get Account Invoice read - `huntress.account_invoices.list` List Account Invoices read **Account reports 2** - `huntress.account_reports.get` Get Summary Report read - `huntress.account_reports.list` List Summary Reports read **Account signals 2** - `huntress.account_signals.get` Get Signal read - `huntress.account_signals.list` List Signals read **External ports 2** - `huntress.external_ports.get` Get External Port read - `huntress.external_ports.list` List External Ports read **Identities 2** - `huntress.identities.get` Get Identity read - `huntress.identities.list` List Identities read **Incident report comments 2** - `huntress.incident_report_comments.create` Create an Incident Report Comment write - `huntress.incident_report_comments.list` List Incident Report Comments read **Invoices 2** - `huntress.invoices.get` Get Account Invoice read - `huntress.invoices.list` List Account Invoices read **Platform actions 2** - `huntress.platform_actions.get` Get Platform Action read - `huntress.platform_actions.list` List Platform Actions read **Reports 2** - `huntress.reports.get` Get Summary Report read - `huntress.reports.list` List Summary Reports read **Reseller invoices 2** - `huntress.reseller_invoices.get` Get Reseller Invoice read - `huntress.reseller_invoices.list` List Reseller Invoices read **Siem log sources 2** - `huntress.siem_log_sources.get` Get Log Source read - `huntress.siem_log_sources.list` List SIEM Log Sources read **Signals 2** - `huntress.signals.get` Get Signal read - `huntress.signals.list` List Signals read **Account 1** - `huntress.account.get` Get Account read **Account remote access connections 1** - `huntress.account_remote_access_connections.list` List Remote Access Connections read **Actor 1** - `huntress.actor.get` Get Actor read **Known VPNS 1** - `huntress.known_vpns.list` List Known VPNs and Proxies read **Remote access connections 1** - `huntress.remote_access_connections.list` List Remote Access Connections read **Reseller invoice account usage line items 1** - `huntress.reseller_invoice_account_usage_line_items.list` List Account Usage Line Items read **Reseller invoice organization usage line items 1** - `huntress.reseller_invoice_organization_usage_line_items.list` List Organization Usage Line Items read **Siem 1** - `huntress.siem.query` Execute ESQL Query read Questions ## The Huntress MCP server, answered. **Is there a Huntress MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 102 Huntress actions across account agents, agents, account incident report remediations and account memberships, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Huntress. **What do I need to connect Huntress?** Huntress API Key (public key): generate at [your_subdomain].huntress.io > API Credentials > Setup and Huntress API Secret Key (private key), shown once when the credential is created. The free call account { op: "connections.requirements", service: "huntress" } lists exactly what to paste. **Can an AI agent delete or change things in Huntress?** Only if its key allows it, and only with an explicit confirmation. 10 Huntress actions are destructive, including delete an Organization, uninstall Agent and permanently Disable an Account. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Huntress API limit?** actionlake paces every call to the limits in the Huntress service file: 60 calls a minute per connection. Repeated reads are answered from cache (61 Huntress actions can be), which never reaches Huntress. **What does a Huntress action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (102 Huntress actions page). Cache hits, searches, dry runs and calls Huntress refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Huntress API does it cover?** The Huntress API v1 (Swagger 2.0, 102 operations) at api.huntress.io. It is built from Huntress's documentation as read on 22 October 2026. 102 actions in 36 areas, each one in the signed service file (version 1.0.0). **Can I combine Huntress with my other systems?** Yes. ask joins Huntress to NetSuite or HubSpot CRM on the same customer and returns the answer rather than every row. Huntress maps crm.company, which 227 other connectors also map. **Does actionlake keep my Huntress data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Huntress credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Huntress Shares the most action names with - [Acronis Cyber Protect Cloud 11](https://actionlake.com/connectors/acronis-cyber-protect-cloud) - [Proofpoint Essentials 10](https://actionlake.com/connectors/proofpoint-essentials) - [Veeam Service Provider Console 10](https://actionlake.com/connectors/veeam-service-provider-console) - [ThreatDown OneView 9](https://actionlake.com/connectors/threatdown-oneview) - [MSP360 Managed Backup 9](https://actionlake.com/connectors/msp360-managed-backup) - [Axcient x360Recover 7](https://actionlake.com/connectors/axcient-x360recover) Joins with, on shared entities - [Bitsight 3](https://actionlake.com/connectors/bitsight) - [Rapid7 InsightIDR 3](https://actionlake.com/connectors/rapid7-insightidr) - [Palo Alto Networks Cortex XDR 3](https://actionlake.com/connectors/palo-alto-networks-cortex-xdr) - [Microsoft 365 Users 2](https://actionlake.com/connectors/microsoft-365-users) - [Salesforce Sales Cloud 2](https://actionlake.com/connectors/salesforce-sales-cloud) - [Xero 2](https://actionlake.com/connectors/xero) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Huntress; the name is the vendor's own. Counts are from the Huntress service file, version 1.0.0. ## Give your agent Huntress today. [Connect Huntress free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/huntress More: https://actionlake.com/llms.txt