Configuration

Follow the setup instructions for your AI client. All clients use the same MCP server — only the configuration format differs.

Note

All clients reference the GitHub repository directly: npx -y github:whatap/whatap-open-mcp

Referencing the repository requires Git, so install it first on Windows. For more details, refer to the Getting Started > Install Git document.

AI Client	Format	Config file	Command
Claude Desktop	JSON	claude_desktop_config.json	Edit file directly
Claude Code	-	-	claude mcp add whatap -e WHATAP_API_TOKEN=... -- npx -y github:whatap/whatap-open-mcp
Codex CLI	TOML	~/.codex/config.toml	codex mcp add whatap --env ... -- npx -y github:whatap/whatap-open-mcp
Gemini CLI	JSON	~/.gemini/settings.json	gemini mcp -s user add whatap -e ... -- npx -y github:whatap/whatap-open-mcp

Claude Desktop

Add the WhaTap MCP server to your configuration file.

OS	Path
macOS	~/Library/Application Support/Claude/claude_desktop_config.json
Linux	~/.config/Claude/claude_desktop_config.json
Windows	%APPDATA%\Claude\claude_desktop_config.json

Add configuration

Open the config file and add the following content.

Claude Desktop configuration

{
  "mcpServers": {
    "whatap": {
      "command": "npx",
      "args": ["-y", "github:whatap/whatap-open-mcp"],
      "env": {
        "WHATAP_API_TOKEN": "your_token_here"
      }
    }
  }
}

Note

If other MCP servers are already configured, add only the "whatap": { ... } block inside the existing "mcpServers" object.

Verify registration

Save the config file and restart Claude Desktop to connect the WhaTap MCP server.

Caution

Claude Desktop must be fully quit (not just the window closed) and restarted for the configuration to take effect.

Claude Code (CLI)

Register the WhaTap MCP server using a terminal command.

Choose scope

Decide the scope before registering.

Scope	Option	Description
All projects	-s user	Available across all projects in your account
Current project	-s project	Available only in the current project (saved to .mcp.json)

Register via command

Claude Code (CLI) registration

# All projects (user scope)
claude mcp add whatap -s user \
  -e WHATAP_API_TOKEN=your_token_here \
  -- npx -y github:whatap/whatap-open-mcp

# Current project (project scope)
claude mcp add whatap -s project \
  -e WHATAP_API_TOKEN=your_token_here \
  -- npx -y github:whatap/whatap-open-mcp

Verify registration

Claude Code (CLI) verification

claude mcp list

Codex CLI (OpenAI)

Register the WhaTap MCP server via command or config file.

Register

Choose one of the two methods below.

Register via command

Codex CLI (OpenAI) command registration

codex mcp add whatap \
  --env WHATAP_API_TOKEN=your_token_here \
  -- npx -y github:whatap/whatap-open-mcp

Register by editing config file

~/.codex/config.toml

[mcp_servers.whatap]
command = "npx"
args = ["-y", "github:whatap/whatap-open-mcp"]

[mcp_servers.whatap.env]
WHATAP_API_TOKEN = "your_token_here"

Note

Codex uses TOML format, not JSON.

Verify registration

Codex CLI (OpenAI) verification

codex mcp list

Gemini CLI (Google)

Register the WhaTap MCP server via command or config file.

Choose scope

Decide the scope before registering.

Scope	File location	Purpose
User (global)	~/.gemini/settings.json	Personal settings, all projects
Project	.gemini/settings.json (project root)	Shared with team

Register

Choose one of the two methods below.

Register via command

Gemini CLI (Google) registration

gemini mcp -s user add whatap \
  -e WHATAP_API_TOKEN=your_token_here \
  npx -- -y github:whatap/whatap-open-mcp

Register by editing config file

~/.gemini/settings.json

{
  "mcpServers": {
    "whatap": {
      "command": "npx",
      "args": ["-y", "github:whatap/whatap-open-mcp"],
      "env": {
        "WHATAP_API_TOKEN": "your_token_here"
      }
    }
  }
}

Verify registration

Gemini CLI (Google) verification

gemini mcp list

---

Verify connection

1. After completing the setup, open your AI client.

2. Enter the following:

   Show me my WhaTap project list

3. If a list with project codes (pcode), names, platforms, and product types appears, the connection is successful. If nothing appears, refer to the troubleshooting guide.