Skip to main content

Environment Configuration

The WhaTap MCP server works out of the box in SaaS environments with just WHATAP_API_TOKEN. If you are using an on-premises environment, you must also set WHATAP_API_URL.

Environment variables

VariableRequiredDefaultDescription
WHATAP_API_TOKENO-WhaTap account API token
WHATAP_API_URLXhttps://api.whatap.ioAPI endpoint (no change needed for SaaS)

API endpoint

In the WhaTap SaaS environment, all regions (Seoul, Tokyo, Singapore, Frankfurt, etc.) use the same API URL (https://api.whatap.io). Region-based routing is handled automatically on the server side — no additional configuration is required.

Refer to the table below and update WHATAP_API_URL accordingly:

EnvironmentURLNotes
SaaS (default)https://api.whatap.ioNo change needed
On-premisesCustomer internal URLSet WHATAP_API_URL

On-premises configuration example (MCP server IP: 192.168.1.100)

Claude Desktop

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

Claude Code

Claude Code
claude mcp add whatap \
-e WHATAP_API_TOKEN=your_token_here \
-e WHATAP_API_URL=http://192.168.1.100 \
-- npx -y github:whatap/whatap-open-mcp

Codex CLI

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

[mcp_servers.whatap.env]
WHATAP_API_TOKEN = "your_token_here"
WHATAP_API_URL = "http://192.168.1.100"

Gemini CLI

Gemini CLI
gemini mcp -s user add whatap \
-e WHATAP_API_TOKEN=your_token_here \
-e WHATAP_API_URL=http://192.168.1.100 \
npx -- -y github:whatap/whatap-open-mcp

WhaTap service regions

The region is selected when creating a project in WhaTap Console. The API URL is the same regardless of region.

RegionLocationCloud
SeoulSouth KoreaAWS, Azure, Kakao Cloud
TokyoJapanAWS, Azure
SingaporeSingaporeAWS
JakartaIndonesiaAWS
MumbaiIndiaAWS
CaliforniaUS WestAWS
VirginiaUS EastAWS
FrankfurtGermanyAWS