Install PipiAds for your AI with MCP or CLI

Claude Desktop

Open Settings → Developer → Edit Config in Claude Desktop. Save the configuration in the file below.

mac: ~/Library/Application Support/Claude/claude_desktop_config.json

windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "pipiads": {
      "command": "npx",
      "args": ["-y", "pipiads-mcp-server"],
      "env": {"PIPIADS_API_KEY": "YOUR_PIPIADS_API_KEY"}
    }
  }
}

Fully quit and reopen Claude Desktop. Start a new chat and check that PipiAds tools are available.

Already have MCP servers? Add the pipiads entry to your existing mcpServers object; keep the other entries.

ChatGPT

In the ChatGPT desktop app, open Settings → MCP servers → Add server and choose STDIO. Use npx with arguments -y and pipiads-mcp-server, and add the PIPIADS_API_KEY environment variable. Alternatively, add the TOML to your config file.

all: ~/.codex/config.toml

[mcp_servers.pipiads]
command = "npx"
args = ["-y", "pipiads-mcp-server"]

[mcp_servers.pipiads.env]
PIPIADS_API_KEY = "YOUR_PIPIADS_API_KEY"

Save, select Restart in MCP servers, and start a local Work task. Type /mcp to inspect pipiads, then try a research example below.

Add this to ~/.codex/config.toml, keeping your existing settings. Update an existing [mcp_servers.pipiads] entry instead of adding it twice. ChatGPT desktop and Codex share this file on the same host.

Codex

For the Codex app, add the TOML to ~/.codex/config.toml and replace the API key placeholder. The CLI and IDE extension share this configuration. If you use the CLI, the command below is an alternative.

all: ~/.codex/config.toml

[mcp_servers.pipiads]
command = "npx"
args = ["-y", "pipiads-mcp-server"]

[mcp_servers.pipiads.env]
PIPIADS_API_KEY = "YOUR_PIPIADS_API_KEY"

Restart the Codex app and check PipiAds in MCP servers settings. In the CLI, start a new session and use /mcp to inspect the connection; codex mcp list shows the saved configuration.

Add this to ~/.codex/config.toml, keeping your existing settings. Update an existing [mcp_servers.pipiads] entry instead of adding it twice. ChatGPT desktop and Codex share this file on the same host.

Claude Code

Run this command in your project terminal after replacing the API key placeholder. It adds the server to Claude Code.

claude mcp add pipiads -e PIPIADS_API_KEY=YOUR_PIPIADS_API_KEY -- npx -y pipiads-mcp-server

Run claude mcp list to check the server, then open Claude Code in that project. Use /mcp to inspect its connection.

Cursor

Create or open .cursor/mcp.json in your project. Add the configuration below and save.

all: .cursor/mcp.json

{
  "mcpServers": {
    "pipiads": {
      "command": "npx",
      "args": ["-y", "pipiads-mcp-server"],
      "env": {"PIPIADS_API_KEY": "YOUR_PIPIADS_API_KEY"}
    }
  }
}

Open Cursor Settings → Tools & MCP (MCP in some versions). Enable pipiads, restart Cursor if needed, then use Agent chat.

Already have MCP servers? Add the pipiads entry to your existing mcpServers object; keep the other entries.

Windsurf

Open the MCP configuration file and add PipiAds. The path below is relative to your home directory.

all: ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "pipiads": {
      "command": "npx",
      "args": ["-y", "pipiads-mcp-server"],
      "env": {"PIPIADS_API_KEY": "YOUR_PIPIADS_API_KEY"}
    }
  }
}

Refresh MCP servers in Windsurf or restart the app. Check that pipiads is available in Cascade.

Already have MCP servers? Add the pipiads entry to your existing mcpServers object; keep the other entries.

OpenClaw

Add pipiads under mcp.servers in ~/.openclaw/openclaw.json, keeping your existing settings. This example requires an OpenClaw version with native MCP support.

all: ~/.openclaw/openclaw.json

{
  "mcp": {
    "servers": {
      "pipiads": {
        "command": "npx",
        "args": [
          "-y",
          "pipiads-mcp-server"
        ],
        "env": {
          "PIPIADS_API_KEY": "YOUR_PIPIADS_API_KEY"
        }
      }
    }
  }
}

Run openclaw mcp list to confirm pipiads is saved; this does not verify a connection. Apply the configuration through the reload or restart procedure of the Gateway or agent process that will use it. To verify tool discovery separately, stop the local Gateway and run openclaw mcp probe pipiads, then restart the Gateway and check PipiAds in a new agent conversation.

Merge the pipiads entry into your existing mcp.servers object, keeping other servers and settings. Do not add a top-level mcpServers field.

Other clients

Use a client that supports local stdio MCP servers. Set command to npx, arguments to -y and pipiads-mcp-server, and environment variable PIPIADS_API_KEY to your key. JSON format varies by client.

npx -y pipiads-mcp-server

Restart or reconnect the MCP server in your client. This package uses local stdio; it does not provide a hosted HTTP or SSE connection URL.

Grok Build

Add the configuration to ~/.grok/config.toml and set your API key locally. This setup is for Grok Build.

all: ~/.grok/config.toml

[mcp_servers.pipiads]
command = "npx"
args = ["-y", "pipiads-mcp-server"]

[mcp_servers.pipiads.env]
PIPIADS_API_KEY = "YOUR_PIPIADS_API_KEY"

Open /mcps in Grok Build, refresh PipiAds, then start a conversation.

Merge this into ~/.grok/config.toml, keeping your existing settings. Update an existing [mcp_servers.pipiads] entry instead of adding it twice.