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

> ## Agent Instructions
> The PartFinder API is served at https://api.partfinder.dev. Authenticate with `Authorization: Bearer $PARTFINDER_API_KEY`; create an account at https://console.partfinder.dev/sign-up and pick pay as you go or a monthly or yearly plan (see https://partfinder.dev/pricing), then create a key. Pay as you go starts with 100 free credits, once per person and per company.
> Install the PartFinder agent skill with `npx skills add https://docs.partfinder.dev` (skill file: https://docs.partfinder.dev/skill.md).
> The OpenAPI document at https://api.partfinder.dev/v1/openapi.json is the source of truth for request and response schemas.
> What each call costs and current plans: https://api.partfinder.dev/llms.txt.

# Connect Claude and Claude Desktop to the PartFinder MCP server

> Add the PartFinder MCP server to Claude as a custom connector and sign in, or use your own API key in Claude Desktop's claude_desktop_config.json.

Claude connects to the PartFinder server as a custom connector, on claude.ai and in Claude Desktop. The
server itself is described in [MCP server](https://docs.partfinder.dev/mcp-server.md).

## Add the connector and sign in

On a Pro or Max plan:

1. Open **Customize > Connectors**.
2. Select **+ Add**, then **Add custom connector**.
3. Enter `PartFinder` as the name and `https://api.partfinder.dev/mcp` as the remote MCP server URL.
   Select **Continue**.
4. Under **Authentication**, choose **Sign in now**. Under **OAuth client**, choose **Use Claude's
   published identity (Recommended)**.
5. Select **Add**.
6. When the PartFinder sign-in page opens, sign in, choose your organization and approve the two
   [permissions](https://docs.partfinder.dev/mcp-server.md#the-two-permissions).

On a Team or Enterprise plan, an owner adds the connector in **Organization settings > Connectors** with
the same values. Each member then finds it in **Customize > Connectors**, selects **Connect** and signs
in to PartFinder.

## Check the connection

Ask Claude "Is PartFinder connected?". Claude calls the `ping` tool, which is free.

## Can I use my own API key?

Yes, in Claude Desktop. Its configuration file only starts local servers, so it connects to the
PartFinder server through `mcp-remote`, a small program that `npx` runs. You need
[Node.js](https://nodejs.org) installed. The API key goes in the file's `env` block, so no environment
variable needs to be set.

1. In Claude Desktop, open the **Claude** menu and select **Settings...**.

2. Select **Developer**, then **Edit Config**. The file opens:
   * macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
   * Windows: `%APPDATA%\Claude\claude_desktop_config.json`

3. Add the `partfinder` entry under `mcpServers`:

   ```json theme={null}
   {
     "mcpServers": {
       "partfinder": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://api.partfinder.dev/mcp",
           "--header",
           "Authorization:${AUTH_HEADER}"
         ],
         "env": {
           "AUTH_HEADER": "Bearer <your API key>"
         }
       }
     }
   }
   ```

4. Replace `<your API key>` with your key. Keep the space after `Bearer`. Write no space around the `:` in
   `Authorization:${AUTH_HEADER}`.

5. Save the file, then quit Claude Desktop completely and open it again.

The key sits in this file's `env` block. Keep the file on your computer, and never share or commit it.

> [!NOTE]
>
> If Claude Desktop cannot find `npx`, for example because Node.js was installed through nvm, set
> `command` to the full path to `npx` and add the folder that holds it to `PATH` in the same `env`
> block.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.