### Building Pinecone Assistant MCP from Source (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command uses Cargo, the Rust package manager, to build the Pinecone Assistant MCP project in release mode. The resulting binary will be located in the `target/release/` directory. Requires Rust to be installed.

```sh
cargo build --release
```

--------------------------------

### Building Docker Image for Pinecone Assistant MCP (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command builds the Docker image for the Pinecone Assistant MCP server using the Dockerfile in the current directory. It tags the image as `pinecone/assistant-mcp`.

```sh
docker build -t pinecone/assistant-mcp .
```

--------------------------------

### Configuring Claude Desktop for Pinecone Assistant MCP (json)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This JSON snippet shows how to configure Claude Desktop's `mcpServers` to use the Pinecone Assistant MCP server running in a Docker container. It specifies the command (`docker`), arguments, and environment variables to pass.

```json
{
  "mcpServers": {
    "pinecone-assistant": {
      "command": "docker",
      "args": [
        "run", 
        "-i", 
        "--rm", 
        "-e", 
        "PINECONE_API_KEY", 
        "-e", 
        "PINECONE_ASSISTANT_HOST", 
        "pinecone/assistant-mcp"
      ],
      "env": {
        "PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY_HERE>",
        "PINECONE_ASSISTANT_HOST": "<YOUR_PINEOCNE_ASSISTANT_HOST_HERE>"
      }
    }
  }
}
```

--------------------------------

### Running Pinecone Assistant MCP Docker Container (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command runs the previously built Docker image. It runs interactively (`-i`), removes the container upon exit (`--rm`), and passes the required `PINECONE_API_KEY` and `PINECONE_ASSISTANT_HOST` environment variables to the container.

```sh
docker run -i --rm \
  -e PINECONE_API_KEY=<YOUR_PINECONE_API_KEY_HERE> \
  -e PINECONE_ASSISTANT_HOST=<YOUR_PINEOCNE_ASSISTANT_HOST_HERE> \
  pinecone/assistant-mcp
```

--------------------------------

### Running MCP Inspector with Cargo Build (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command runs the MCP inspector using `npx` and passes the command `cargo run` to it. This allows testing the server built and run directly via Cargo, assuming environment variables are set.

```sh
npx @modelcontextprotocol/inspector cargo run
```

--------------------------------

### Running MCP Inspector with Docker (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command runs the MCP inspector using `npx` and passes the Docker run command to it. This allows testing the server running inside a Docker container directly through the inspector, ensuring environment variables are passed correctly.

```sh
npx @modelcontextprotocol/inspector -- docker run -i --rm -e PINECONE_API_KEY -e PINECONE_ASSISTANT_HOST pinecone/assistant-mcp
```

--------------------------------

### Setting PINECONE_API_KEY Environment Variable (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command sets the `PINECONE_API_KEY` environment variable in the current shell session. This is required for the server or inspector to authenticate with Pinecone. Replace `<YOUR_PINECONE_API_KEY_HERE>` with your actual key.

```sh
export PINECONE_API_KEY=<YOUR_PINECONE_API_KEY_HERE>
```

--------------------------------

### Setting PINECONE_ASSISTANT_HOST Environment Variable (sh)

Source: https://github.com/pinecone-io/assistant-mcp/blob/main/README.md

This command sets the `PINECONE_ASSISTANT_HOST` environment variable in the current shell session. This specifies the host URL for the Pinecone Assistant API. Replace `<YOUR_PINEOCNE_ASSISTANT_HOST_HERE>` with the correct host.

```sh
export PINECONE_ASSISTANT_HOST=<YOUR_PINEOCNE_ASSISTANT_HOST_HERE>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.