---
title: "Prerequisites"
slug: "polarity-mcp-prerequisites"
description: "Review the prerequisites for using the Polarity MCP, including server access, active integrations, and authentication requirements."
tags: ["configuration", "Getting Started", "HTTPS", "integrations", "MCP", "prerequisites", "requirements", "setup"]
updated: 2026-07-29T18:49:04Z
published: 2026-07-29T18:49:04Z
canonical: "knowledge.threatconnect.com/polarity-mcp-prerequisites"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.threatconnect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prerequisites

**Before you can use the Polarity MCP, confirm the following conditions are met:**

- [ ] **Polarity Server is running and accessible over HTTPS.**
- [ ] **At least one integration is running on the server.** - [ ] The MCP only returns useful data if integrations are active and subscribed to by the authenticated user.
- [ ] **AI is enabled in the server's Model Settings in the UI** (see [**Enabling the MCP Server**](/v1/docs/polarity-mcp-enabling-the-ai-feature))**.** - [ ] Without this, the conversations/chat API and MCP reducers will not function, though the MCP endpoint itself will still route.
- [ ] **You have a valid Polarity user account and can obtain a JWT token for API authentication** (see [**Authenticating with the MCP Endpoint**](/v1/docs/polarity-mcp-authentication))**.**
- [ ] **Ensure MCP is enabled in the Server by navigating to the** `.env` **file and adding in the line** `HERMES\_MCP\_SERVER=true`
- [ ] **Your MCP client supports** `StreamableHTTP` **transport.** - [ ] The Polarity MCP does not use `STDIO`transport. Confirm that your client or SDK supports HTTP-based MCP connections.
