Use PartLogic in Claude

Choose your Claude setup

Recommended: Claude Code. It supports an HTTP MCP connection with an Authorization header and environment-variable credentials. Install and sign in using the official Claude Code quickstart.

Claude web and Desktop custom connectors describe an OAuth flow. This adapter uses a portal key; that OAuth connection has not been verified. Follow the Code route below. See Claude's custom connector guide.

You need a portal API key with access to the intended devices and the deployed adapter version that accepts portal keys directly. The MCP uses your PartLogic key; any Claude account or billing setup is separate.

1. Generate a portal API key

1. Sign in to the PartLogic portal. New users can follow the signup guide.
2. Open Integrations and select New API Key.

3. Enter a name such as Claude stock lookup.
4. Select the devices Claude should be able to query. Use the filter to find devices by name or site.
5. Set an optional expiry, then select Generate.

6. Copy the key to a secure store before leaving; the complete value is shown only once. Select Return when finished.

See the full portal API-key guide. Do not paste a key into a conversation or tool argument.

The current adapter forwards the bearer credential to the Stock API as X-API-Key. Use your actual portal key, without a second Bearer prefix. Older mapped MCP tokens require the legacy deployment; they are not the credential described here.

2. Configure the MCP connection

Create a dedicated folder for your PartLogic conversations. Save this JSON there as .mcp.json. If that folder already has a configuration, add the partlogic entry to its existing mcpServers object rather than replacing it.

{
  "mcpServers": {
    "partlogic": {
      "type": "http",
      "url": "https://partlogicmcp-a3b8bvfqhwdnf3ez.ukwest-01.azurewebsites.net/mcp",
      "headers": {
        "Authorization": "Bearer ${PARTLOGIC_API_KEY}"
      }
    }
  }
}

PARTLOGIC_API_KEY is a session environment variable. Keep its reference in the JSON; the actual key is entered when starting Claude. See Claude Code's MCP reference.

Use the endpoint supplied by your administrator if your organisation has a different deployment.

3. Start Claude Code on Windows

Save this PowerShell launcher beside .mcp.json. It prompts for your key locally, supplies it to Claude for that session and restores the previous environment value when Claude exits. The launcher does not write the key into either file.

Open PowerShell in that folder and run:

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\Start-PartLogic.ps1

This command permits the launcher in that process only. Review the downloaded script first. Enter the actual portal key at its hidden prompt.

You can also download the configuration. Check that its saved name is .mcp.json, including the leading dot, rather than .mcp.json.txt.

If your organisation manages software or script execution, use its approved setup process.

4. Verify stock access

Review folder-trust and MCP prompts. In Claude Code, type /mcp and check partlogic. Then request a fresh stock sample:

Use PartLogic list_stock to retrieve three stock rows. Show the original field names and any source or device context. Report retrieval errors accurately.

A connected server or visible tool list does not prove that the key can retrieve stock. The adapter checks the key upstream when list_stock runs. Compare the successful result with the intended portal devices.

The supplied Claude Code screenshot shows a successful stock lookup. Check your own returned rows against your portal device access. The configuration and launcher syntax were also checked locally; a failed request is not an empty inventory.

Example prompts

Replace the example reference with your own:

Search PartLogic stock for ABC-123. Compare returned identifier fields with ABC-123. Preserve leading zeros and show all variants or packs separately.

Retrieve all accessible PartLogic stock rows. Follow next_offset until there are no more pages. Label the results partial if any request fails.

Search matches all query tokens somewhere in a stored row. Try fewer words if a successful search has no matches. A search hit is a candidate, not exact product resolution.

Rows may represent device holdings rather than distinct products. Missing identifiers and quantities stay unknown. Stock rows do not establish supplier availability or a complete product master; offset pages may shift as stock changes.

Troubleshooting

Report errors without including keys. Do not disable authentication to get connected.