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

# Configure the peeps MCP server with API keys and clients

> Configure the peeps MCP server with your API key and optional settings. Includes ready-to-paste configs for Claude Desktop, Cursor, and HTTP/SSE.

The peeps MCP server is configured through environment variables and your MCP client's own config file. You set your API key once, point your client at the server, and everything else uses sensible defaults. This page covers every available variable and provides ready-to-paste config files for Claude Desktop, Cursor, and generic HTTP/SSE clients.

## Environment variables

Pass these variables to the MCP server process — either inline before the command, in your shell profile, or through the `env` block of your MCP client's config file.

<ParamField path="PEEPS_API_KEY" type="string" required>
  Your peeps API key, used to authenticate every request to the peeps API. Find yours in **Settings → API Keys** in the [peeps dashboard](https://app.peeps.ai/settings/api-keys).
</ParamField>

<ParamField path="PEEPS_API_URL" type="string">
  Override the base URL for the peeps API. Defaults to `https://api.peeps.ai`. You only need this if you are connecting to a private or on-premises peeps deployment.
</ParamField>

<ParamField path="PEEPS_LOG_LEVEL" type="string">
  Controls the verbosity of server logs. Accepted values: `debug`, `info`, `warn`, `error`. Defaults to `info`. Set to `debug` when troubleshooting connection or tool-call issues.
</ParamField>

## Sample configurations

The examples below show complete, ready-to-use config files for the most common MCP clients. Replace `your-api-key-here` with your actual API key in each one.

<Warning>
  Never commit your API key to version control. If your config file lives inside a repository, load the key from an environment variable or a secrets manager instead of pasting it in plain text.
</Warning>

<CodeGroup>
  ```json Claude Desktop (claude_desktop_config.json) theme={null}
  {
    "mcpServers": {
      "peeps": {
        "command": "npx",
        "args": ["-y", "@peeps-ai/mcp"],
        "env": {
          "PEEPS_API_KEY": "your-api-key-here"
        }
      }
    }
  }
  ```

  ```json Cursor (.cursor/mcp.json) theme={null}
  {
    "mcpServers": {
      "peeps": {
        "command": "npx",
        "args": ["-y", "@peeps-ai/mcp"],
        "env": {
          "PEEPS_API_KEY": "your-api-key-here"
        }
      }
    }
  }
  ```

  ```json Remote HTTP/SSE (generic) theme={null}
  {
    "mcpServers": {
      "peeps": {
        "url": "https://mcp.peeps.ai/sse",
        "headers": {
          "Authorization": "Bearer your-api-key-here"
        }
      }
    }
  }
  ```
</CodeGroup>

### Claude Desktop

Claude Desktop reads its MCP server list from `claude_desktop_config.json`. The file location depends on your operating system:

| Platform | Path                                                              |
| -------- | ----------------------------------------------------------------- |
| macOS    | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows  | `%APPDATA%\Claude\claude_desktop_config.json`                     |

After saving the file, restart Claude Desktop. The peeps tools will appear as available tools in your next conversation.

### Cursor

Cursor reads MCP server configuration from `.cursor/mcp.json` relative to your project root. Create the file if it doesn't exist, then paste the Cursor example above.

Reload Cursor's MCP servers from **Settings → MCP** after saving the file.

### Remote HTTP/SSE (generic)

Use this format for any MCP client that supports HTTP/SSE transport. Point the `url` field at `https://mcp.peeps.ai/sse` and pass your API key as a `Bearer` token. No local process is started — your client connects directly to the peeps-hosted server.

<Tip>
  The remote server is always running the latest version of the peeps MCP server. If you need a pinned version for stability, use the npx or global install options and specify a version: `npx -y @peeps-ai/mcp@1.2.3`.
</Tip>

## Using environment variables instead of inline keys

To avoid putting your API key in a config file, set `PEEPS_API_KEY` in your shell environment and reference it from your config:

```bash theme={null}
# Add to ~/.zshrc or ~/.bashrc
export PEEPS_API_KEY="your-api-key-here"
```

Then omit the `env` block entirely from your Claude Desktop or Cursor config — the server process inherits the variable from your shell:

```json theme={null}
{
  "mcpServers": {
    "peeps": {
      "command": "npx",
      "args": ["-y", "@peeps-ai/mcp"]
    }
  }
}
```

<Note>
  Some MCP clients launch server processes in a minimal shell environment that may not inherit your shell profile exports. If the server fails to authenticate, try adding the `env` block explicitly rather than relying on shell inheritance.
</Note>