Summary
The StockIQ extension for Claude Desktop connects the Claude Desktop app to your StockIQ instance, so you can ask Claude about your StockIQ data in an ordinary chat. You install it by opening a file and entering your StockIQ address and an MCP token. There is nothing else to install and no configuration file to edit.
The extension uses the StockIQ MCP Service, with the same tools, permissions and rate limits as any other MCP client. MCP Service - Getting Started covers creating the token and choosing its roles: https://support.stockiqtech.com/hc/en-us/articles/54955746398739.
NOTE: This article is for Claude Desktop only. Claude Code, Cursor, Codex and VS Code connect without the extension, as described in MCP Service - Getting Started. The claude.ai website and the Claude mobile apps cannot connect to StockIQ with an MCP token.
Before You Start
You need the following.
- Claude Desktop- The Claude app for Windows or macOS, installed and signed in.
- An MCP token- Created by your StockIQ administrator under Admin > Manage Security > MCP Tokens. Use a token for this connection only, not one that another app already uses.
- Your StockIQ address- The address you use to open StockIQ in your browser, for example https://contoso.stockiqtech.net.
- The extension file- stockiq.mcpb, downloaded in the first step below.
IMPORTANT: If your company uses Claude Team or Enterprise, your Claude administrator may limit which extensions can be installed. In that case Claude Desktop will not install the file, and your administrator needs to add the StockIQ extension for your organization instead. See For Claude Team and Enterprise Administrators below.
Installing the Extension
- Download stockiq.mcpb. The link always gives you the latest version.
- Open the file. Claude Desktop shows the StockIQ extension. Click Install.
- Fill in the extension's settings:
- StockIQ URL- Your StockIQ address. You can leave /mcp off the end; the extension adds it.
- MCP token- Paste the token exactly as StockIQ showed it.
- Click Save, and confirm when Claude Desktop asks.
- Go to Settings > Extensions and make sure StockIQ is turned on.
NOTE: Claude Desktop stores the token encrypted on your computer, not in a plain-text file, and the extension never writes it to a log.
Checking the Connection
Start a new chat and ask:
What StockIQ tools do you have available, and what can you tell me about this instance?
If Claude answers with your instance's details, you are connected. If Claude shows a message beginning StockIQ MCP bridge:, see Troubleshooting below.
Connecting a Sandbox
To use your StockIQ sandbox as well, download stockiq-sandbox.mcpb and install it the same way. It appears in Claude Desktop as StockIQ Sandbox, separate from StockIQ, and both can be turned on at the same time.
- StockIQ sandbox URL- The address of your sandbox.
- MCP token- A token created in the sandbox. A production token does not work in the sandbox, and a sandbox token does not work in production.
IMPORTANT: When both are turned on, tell Claude which one you mean, for example "in the sandbox". Sandbox data is not production data, so don't base business decisions on it.
Updating or Removing the Extension
- Update- Open the newer stockiq.mcpb file the same way. Your saved address and token are kept. The installed version is shown under Settings > Extensions. If your Claude administrator added the extension for your organization, they update it instead.
- Turn off- Turn StockIQ off under Settings > Extensions. Claude stops using StockIQ until you turn it back on.
- Remove- Uninstall StockIQ under Settings > Extensions.
NOTE: Removing the extension does not revoke the token. If nobody needs it any more, delete it under Admin > Manage Security > MCP Tokens.
For Claude Team and Enterprise Administrators
A Claude organization Owner can add the StockIQ extension for the whole organization, so users install it from Claude Desktop without the file. This is required if your organization uses the desktop extension allowlist, which stops users from installing extensions by opening a file.
- In Claude, go to Organization settings > Connectors > Desktop.
- Click Add custom extension and select stockiq.mcpb. It appears under Custom team extensions.
- Click ... next to StockIQ, then Add to team.
- To offer the sandbox as well, repeat these steps with stockiq-sandbox.mcpb.
Users then install StockIQ from the extensions in Claude Desktop and enter their own StockIQ URL and MCP token, as in Installing the Extension. Each user needs their own token.
To update the extension, click ... next to StockIQ, choose Upload new version, and select the newer stockiq.mcpb.
IMPORTANT: Turning on the allowlist removes installed extensions that are not on it. Add StockIQ first so users keep their connection. Anthropic describes the allowlist in Enabling and using the desktop extension allowlist: https://support.claude.com/en/articles/12592343.
NOTE: If your IT team has turned off desktop extensions through device management, users cannot install the StockIQ extension either way.
Troubleshooting
When the extension cannot complete a request, Claude shows a message beginning StockIQ MCP bridge:. The rest of the message says what went wrong:
- StockIQ rejected the MCP token (401)- The token was mistyped, or it has expired, been rotated or been deleted. It may also belong to a different StockIQ instance, such as a sandbox token entered for production. Check the token under Settings > Extensions > StockIQ against Admin > Manage Security > MCP Tokens, and paste it again if needed.
- StockIQ refused the request (403)- Your StockIQ license does not include the MCP add-on, or the token's roles do not allow the request. Contact your StockIQ administrator.
- There is no MCP endpoint at … (404)- The StockIQ URL is wrong. Check it under Settings > Extensions > StockIQ; it should be the address you use to open StockIQ.
- StockIQ no longer recognizes this MCP session- StockIQ was restarted or ended the connection. Turn the extension off and on again under Settings > Extensions, or restart Claude Desktop.
- StockIQ's rate limit for this MCP token was reached- The token made too many requests in a short time. Wait for the time the message gives, then try again. Every app using the same token shares its limit, so give each app its own token. See Rate limits in MCP Service - Getting Started.
- Cannot connect to …, Cannot find …, or Timed out connecting to …- Your computer cannot reach StockIQ. Check the StockIQ URL, your network connection, and your VPN if StockIQ is only reachable through one.
- The TLS certificate for … is not trusted- Your computer does not trust the certificate StockIQ presents. If your company issues its own certificates, your IT team needs to install the company's certificate authority on your computer.
- StockIQ returned an error- A problem on the StockIQ side. Try again in a few minutes; if it continues, contact StockIQ Support.
- Connected, but Claude finds no StockIQ tools- The token has no roles, or its roles grant no tool permissions. Ask your StockIQ administrator to assign roles to the token.
IMPORTANT: The extension cannot use a self-signed server certificate, even if it is installed in your computer's certificate store. A self-hosted StockIQ needs a certificate issued by a certificate authority, either a public one or your company's own.
Getting Help
If you get stuck, contact StockIQ Support and include:
- The Name of the MCP token, never the token itself.
- The extension's version, from Settings > Extensions.
- The exact message Claude showed.
- Roughly when you tried, so we can find the request on our side.
Support may also ask for the extension's log. It is part of Claude Desktop's main.log file. On Windows that file is in %LOCALAPPDATA%\Claude\Logs (Microsoft Store version) or %APPDATA%\Claude\logs; on macOS it is in ~/Library/Logs/Claude. The extension's lines contain stockiq-mcp-bridge, and they never contain your token.
NOTE: The rest of main.log records other Claude Desktop activity. Review the file before you send it, or send only the lines that contain stockiq-mcp-bridge.