Overview
The Huntress Model Context Protocol (MCP) server lets compatible AI assistants connect to data in your Huntress account. MCP access is read-only: it can retrieve information but cannot make changes in Huntress. The data available to a user follows that user's Huntress permissions.
The recommended way to connect is OAuth using your Huntress sign-in. The server URL is:
https://api.huntress.io/v1/mcp
Before you begin
Use an MCP client that supports a remote MCP server over HTTP and OAuth.
Make sure you can sign in to the Huntress account whose data you want to access. Your existing SSO and MFA requirements still apply.
You do not need to create or paste an API key when you choose Sign in with Huntress.
Connect with OAuth (recommended)
In your MCP client, add a remote MCP server. Select HTTP (or the client's equivalent for a remote HTTP MCP server) as the connection type.
Enter the server URL:
https://api.huntress.io/v1/mcp.Save or connect. Your MCP client should open a browser window to authorize the connection.
-
On the Authorize MCP access page, check the name of the MCP client requesting access. The page offers two ways to authorize:
Sign in with Huntress — Recommended for most users. Choose this to use your normal Huntress portal login. Sign in if prompted, and complete your organization's SSO or MFA steps. Do not enter your portal password in the API Key or API Secret fields.
Continue with an API credential — Choose this only if you specifically want to authorize with an API key and secret instead of your Huntress login. Enter a user-based API credential. Account-wide keys are not supported for this OAuth option. For instructions on creating a user-based key, see Generating API Keys.
Return to your MCP client and confirm that the Huntress server is connected.
The API-credential choice on this page still authorizes the connection through OAuth. It is different from the deprecated Basic-auth setup below:
Claude Code using a Base64 Key (deprecated)
Run the following command, replacing <base64_credential> with your encoded value:
claude mcp add huntress https://api.huntress.io/v1/mcp -t http -s user -H "Authorization: Basic <base64_credential>"Verify with “claude mcp list” that the MCP server is listed and shows as connected.
Claude Desktop using a Base64 Key (deprecated)
In order to use the Huntress MCP server with Claude Desktop you will need to have Node.js installed and edit the configuration files as noted below.
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Add the following mcpServers entry (or add the huntress block to your existing mcpServers section):
{
"mcpServers": {
"huntress": {
"command": "npx",
"args": [
"mcp-remote",
"https://api.huntress.io/v1/mcp",
"--header",
"Authorization: Basic <base64_credential>"
]
}
}
}Fully exit and reopen Claude Desktop to apply the changes.
Other Platforms
Refer to the documentation on how to add an MCP server that uses Basic Authentication or Oauth.