Skip to content
actionlake
Start free

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 freeSee 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
  • 102actionsin one signed file
  • 62readlook, never change
  • 30writecreate and update
  • 10wait for a yesdestructive, 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_keyHuntress API Key (public key): generate at [your_subdomain].huntress.io > API Credentials > Setup
    • api_secretHuntress 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 callcheck { 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_keyapi_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 2026api.huntress.io
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.

  • 62readlook, never change
  • 30writecreate and update
  • 10destructivewait 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.

ActionWhat it doesEffectSame name in
huntress.organizations.listList OrganizationsList Organizations.readcrm.company.list162 connectors
huntress.identities.listList IdentitiesList Identities.readidentity.user.list474 connectors
huntress.organizations.createCreate an OrganizationCreate an Organization.writecrm.company.create142 connectors
huntress.agents.listList AgentsList Agents.readdevice.endpoint.list65 connectors
huntress.organizations.updateUpdate an OrganizationUpdate an Organization.writecrm.company.update137 connectors
huntress.incident_reports.listList Incident ReportsList Incident Reports.readsecurity.incident.list17 connectors
huntress.identities.getGet IdentityGet Identity.readidentity.user.get399 connectors
huntress.organizations.deleteDelete an OrganizationDelete an Organization.destructivecrm.company.delete119 connectors
huntress.signals.listList SignalsList Signals.readsecurity.alert.list22 connectors
huntress.agents.getGet AgentGet Agent.readdevice.endpoint.get57 connectors
huntress.incident_report_comments.listList Incident Report CommentsList Incident Report Comments.readsecurity.incident_note.list9 connectors
huntress.incident_report_comments.createCreate an Incident Report CommentCreate an Incident Report Comment.writesecurity.incident_note.create8 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. Readread

    Which Huntress alerts are open right now? Group them by service.

    callshuntress.incident_reports.list

  2. Writewrite

    Create an Organization in Huntress. Show me exactly what you will send before you save it.

    callshuntress.organizations.create

  3. Across systemsread

    Which Huntress companies have invoices in NetSuite, and how many each?

    callshuntress.organizations.listnetsuite.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

  • Which Huntress companies have tickets in HubSpot CRM, and how many each?

    huntress.organizations.list + hubspot_crm.tickets.list, on crm.company · HubSpot CRM

Also mapped by other connectorsidentity.user 517crm.company 227device.endpoint 69monitoring.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 Organizationhuntress.organizations.delete
  • Uninstall Agenthuntress.agents.uninstall
  • Permanently Disable an Accounthuntress.accounts.delete
  • Delete Membershiphuntress.memberships.delete
  • Uninstall Agenthuntress.account_agents.uninstall
  • Release Agent Isolationhuntress.agents.release_isolation
  • Delete Membershiphuntress.account_memberships.delete
  • Delete an Organizationhuntress.account_organizations.delete
  • Delete Unwanted Access Rulehuntress.unwanted_access_rules.delete
  • Release Agent Isolationhuntress.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.

dohuntress.organizations.deleteconfirm_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: "[email protected]" },    { match: "huntress.agents.uninstall", approver: "[email protected]" },    { match: "huntress.accounts.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 102 Huntress actions
  • 102actions pageeach page of a long list is one call
  • 61reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Huntress action.

102 actions by area: the id your agent calls, what it does, and its effect.

Account agents6
  • huntress.account_agents.getGet Agentread
  • huntress.account_agents.isolateIsolate Agentwrite
  • huntress.account_agents.listList Agentsread
  • huntress.account_agents.release_isolationRelease Agent Isolationdestructive
  • huntress.account_agents.uninstallUninstall Agentdestructive
  • huntress.account_agents.updateUpdate Agentwrite
Agents6
  • huntress.agents.getGet Agentread
  • huntress.agents.isolateIsolate Agentwrite
  • huntress.agents.listList Agentsread
  • huntress.agents.release_isolationRelease Agent Isolationdestructive
  • huntress.agents.uninstallUninstall Agentdestructive
  • huntress.agents.updateUpdate Agentwrite
Account incident report remediations5
  • huntress.account_incident_report_remediations.bulk_approveBulk Approve Remediationswrite
  • huntress.account_incident_report_remediations.bulk_rejectBulk Reject Remediationswrite
  • huntress.account_incident_report_remediations.completeSet Remediation Completionwrite
  • huntress.account_incident_report_remediations.getGet Remediationread
  • huntress.account_incident_report_remediations.listList Remediationsread
Account memberships5
  • huntress.account_memberships.createCreate a Membershipwrite
  • huntress.account_memberships.deleteDelete Membershipdestructive
  • huntress.account_memberships.getGet Membershipread
  • huntress.account_memberships.listList Membershipsread
  • huntress.account_memberships.updateUpdate a User's membershipwrite
Account organizations5
  • huntress.account_organizations.createCreate an Organizationwrite
  • huntress.account_organizations.deleteDelete an Organizationdestructive
  • huntress.account_organizations.getGet Organizationread
  • huntress.account_organizations.listList Organizationsread
  • huntress.account_organizations.updateUpdate an Organizationwrite
Accounts5
  • huntress.accounts.createCreate Accountwrite
  • huntress.accounts.deletePermanently Disable an Accountdestructive
  • huntress.accounts.getGet Specific Accountread
  • huntress.accounts.listList Accountsread
  • huntress.accounts.updateUpdate Accountwrite
Incident report remediations5
  • huntress.incident_report_remediations.bulk_approveBulk Approve Remediationswrite
  • huntress.incident_report_remediations.bulk_rejectBulk Reject Remediationswrite
  • huntress.incident_report_remediations.completeSet Remediation Completionwrite
  • huntress.incident_report_remediations.getGet Remediationread
  • huntress.incident_report_remediations.listList Remediationsread
Memberships5
  • huntress.memberships.createCreate a Membershipwrite
  • huntress.memberships.deleteDelete Membershipdestructive
  • huntress.memberships.getGet Membershipread
  • huntress.memberships.listList Membershipsread
  • huntress.memberships.updateUpdate a User's membershipwrite
Organizations5
  • huntress.organizations.createCreate an Organizationwrite
  • huntress.organizations.deleteDelete an Organizationdestructive
  • huntress.organizations.getGet Organizationread
  • huntress.organizations.listList Organizationsread
  • huntress.organizations.updateUpdate an Organizationwrite
Reseller subscriptions5
  • huntress.reseller_subscriptions.createCreate Reseller Subscriptionwrite
  • huntress.reseller_subscriptions.getGet Reseller Subscriptionread
  • huntress.reseller_subscriptions.listList Reseller Subscriptionsread
  • huntress.reseller_subscriptions.updateUpdate Reseller Subscriptionwrite
  • huntress.reseller_subscriptions.upgradeUpgrade Reseller Subscriptionwrite
Unwanted access rules5
  • huntress.unwanted_access_rules.createCreate an Unwanted Access Rulewrite
  • huntress.unwanted_access_rules.deleteDelete Unwanted Access Ruledestructive
  • huntress.unwanted_access_rules.getGet Unwanted Access Ruleread
  • huntress.unwanted_access_rules.listList Unwanted Access Rulesread
  • huntress.unwanted_access_rules.updateUpdate an Unwanted Access Rulewrite
Account incident reports3
  • huntress.account_incident_reports.getGet Incident Reportread
  • huntress.account_incident_reports.listList Incident Reportsread
  • huntress.account_incident_reports.resolveCreate an Incident Report Resolutionwrite
Escalations3
  • huntress.escalations.getGet Escalationread
  • huntress.escalations.listList Escalationsread
  • huntress.escalations.resolveCreate an Escalation Resolutionwrite
Incident reports3
  • huntress.incident_reports.getGet Incident Reportread
  • huntress.incident_reports.listList Incident Reportsread
  • huntress.incident_reports.resolveCreate an Incident Report Resolutionwrite
Account external ports2
  • huntress.account_external_ports.getGet External Portread
  • huntress.account_external_ports.listList External Portsread
Account incident report comments2
  • huntress.account_incident_report_comments.createCreate an Incident Report Commentwrite
  • huntress.account_incident_report_comments.listList Incident Report Commentsread
Account invoices2
  • huntress.account_invoices.getGet Account Invoiceread
  • huntress.account_invoices.listList Account Invoicesread
Account reports2
  • huntress.account_reports.getGet Summary Reportread
  • huntress.account_reports.listList Summary Reportsread
Account signals2
  • huntress.account_signals.getGet Signalread
  • huntress.account_signals.listList Signalsread
External ports2
  • huntress.external_ports.getGet External Portread
  • huntress.external_ports.listList External Portsread
Identities2
  • huntress.identities.getGet Identityread
  • huntress.identities.listList Identitiesread
Incident report comments2
  • huntress.incident_report_comments.createCreate an Incident Report Commentwrite
  • huntress.incident_report_comments.listList Incident Report Commentsread
Invoices2
  • huntress.invoices.getGet Account Invoiceread
  • huntress.invoices.listList Account Invoicesread
Platform actions2
  • huntress.platform_actions.getGet Platform Actionread
  • huntress.platform_actions.listList Platform Actionsread
Reports2
  • huntress.reports.getGet Summary Reportread
  • huntress.reports.listList Summary Reportsread
Reseller invoices2
  • huntress.reseller_invoices.getGet Reseller Invoiceread
  • huntress.reseller_invoices.listList Reseller Invoicesread
Siem log sources2
  • huntress.siem_log_sources.getGet Log Sourceread
  • huntress.siem_log_sources.listList SIEM Log Sourcesread
Signals2
  • huntress.signals.getGet Signalread
  • huntress.signals.listList Signalsread
Account1
  • huntress.account.getGet Accountread
Account remote access connections1
  • huntress.account_remote_access_connections.listList Remote Access Connectionsread
Actor1
  • huntress.actor.getGet Actorread
Known VPNS1
  • huntress.known_vpns.listList Known VPNs and Proxiesread
Remote access connections1
  • huntress.remote_access_connections.listList Remote Access Connectionsread
Reseller invoice account usage line items1
  • huntress.reseller_invoice_account_usage_line_items.listList Account Usage Line Itemsread
Reseller invoice organization usage line items1
  • huntress.reseller_invoice_organization_usage_line_items.listList Organization Usage Line Itemsread
Siem1
  • huntress.siem.queryExecute ESQL Queryread

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

Joins with, on shared entities

Browse

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 freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.