Endpoint URL
The Polarity MCP server is available at:
https://<polarity-host>/mcp
For example:
https://polarity.dataminr.com/mcp
The server uses StreamableHTTP transport. This transport supports both standard HTTP POST requests (for single-turn exchanges) and SSE streaming (for incremental responses). Your MCP client must support this transport mode.
Connecting with Claude Desktop
Claude Desktop does not natively support remote HTTP MCP transport. Use the @polarityio/mcp-connector NPM package as a STDIO bridge.
Add the following entry to your Claude Desktop MCP configuration file (claude\_desktop\_config.json):
{
"mcpServers": {
"polarity": {
"command": "npx",
"args": ["-y", "@polarityio/mcp-connector"],
"env": {
"POLARITY_SERVER_URL": "https://polarity.yourcompany.com",
"POLARITY_TOKEN": "your-api-key-here"
}
}
}
}Connecting with mcp-remote or a Custom Agent
If your agent framework uses mcp-remote or a custom HTTP MCP transport:
npx -y mcp-remote https://<polarity-host>/mcp \ --header "Authorization: Bearer <your-polarity-jwt>"
Connecting with GitHub Copilot CLI
GitHub Copilot CLI loads MCP servers from a JSON configuration file. Edit (or create) ~/.copilot/mcp-config.json.
Add a polarity entry under mcpServers:
{
"mcpServers": {
"polarity": {
"type": "http",
"url": "https://<polarity-host>/mcp",
"headers": {
"Authorization": "Bearer <your-polarity-jwt>"
}
}
}
}Save the file and run /restart inside an active Copilot CLI session (or relaunch Copilot) so the new server is registered. The three Polarity tools then appear alongside any other MCP tools in your session.
Connecting with Gemini Code Assist (VS Code)
Gemini Code Assist agent mode reads MCP server configuration from ~/.gemini/settings.json (the same file used by the Gemini CLI).
Add a polarity entry under mcpServers:
{
"mcpServers": {
"polarity": {
"httpUrl": "https://<polarity-host>/mcp",
"headers": {
"Authorization": "Bearer <your-polarity-jwt>"
}
}
}
}In VS Code, open the command palette and run Developer: Reload Window. Open the Gemini Code Assist chat panel, click the Agent toggle to enter agent mode, and the Polarity tools become available to the agent.
Connecting with ChatGPT Desktop
ChatGPT (desktop and web) supports remote MCP servers as "apps" (formerly called connectors).
Because the Polarity MCP endpoint is already a remote HTTPS service, no local bridge is required: ChatGPT connects directly.
A paid plan (Plus, Pro, Business, Enterprise, or Edu) is required, and a workspace admin may need to enable Developer Mode for your account.
Enable Developer Mode.
Open ChatGPT Settings.
Navigate to “Apps & Connectors → Advanced”, and toggle “Developer mode” on.
Add the Polarity connector.
Still under “Apps & Connectors”, click “Create”.
In the dialog, enter:
Name: Polarity MCP Server URL: https://<polarity-host>/mcp Authentication: Custom #(or "No authentication" if you will pass the bearer token via the Authorization header) Header: Authorization: Bearer <your-polarity-jwt>
Save and enable.
The connector appears on the “Apps & Connectors” page.
In a chat, click “+” in the composer and select “Polarity” to make its tools available for that conversation.
Note: ChatGPT's Deep Research and Company Knowledge modes require MCP servers to expose specific search and fetch tools and will not invoke Polarity's integration-lookup tools in those modes.
Use a standard chat (with Developer mode connectors enabled) to call Polarity tools directly.
Verifying the Connection
After connecting, request the tool list. The server should respond with the three available tools.
Confirm you see list\_available\_integrations, do\_integration\_lookup, and parse\_entities in the tools list. If the tool list is empty or the connection fails, review the authentication steps in "Authenticating with the MCP Endpoint".