@kadam-net/mcp-server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@kadam-net/mcp-serverlist my active campaigns"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@kadam-net/mcp-server
MCP server for Kadam ad network — manage campaigns, creatives, audiences, sites, and analytics via AI agents.
Built on the Model Context Protocol (MCP), the open standard for connecting LLMs to external tools and data.
Install (one click)
Cursor
Or add manually to .cursor/mcp.json:
{
"mcpServers": {
"kadam": {
"command": "npx",
"args": ["-y", "@kadam-net/mcp-server"],
"env": {
"KADAM_ADV_API_KEY": "your-advertiser-api-key",
"KADAM_PUB_API_KEY": "your-publisher-api-key"
}
}
}
}Claude Code
claude mcp add kadam -- npx -y @kadam-net/mcp-serverThen set the env var: export KADAM_ADV_API_KEY=your-key
Claude Desktop
Download → double-click → Install. Or add manually to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"kadam": {
"command": "npx",
"args": ["-y", "@kadam-net/mcp-server"],
"env": {
"KADAM_ADV_API_KEY": "your-advertiser-api-key",
"KADAM_PUB_API_KEY": "your-publisher-api-key"
}
}
}
}Any MCP client (universal one-liner)
npx add-mcp @kadam-net/mcp-serverDocker
docker run -i --rm \
-e KADAM_ADV_API_KEY=your-key \
kadam/mcp-server:latestnpm global
npm install -g @kadam-net/mcp-server
KADAM_ADV_API_KEY=your-key kadam-mcp-serverConfiguration
Variable | Required | Description |
| One of two | Advertiser API key from partners.kadam.net -> Profile -> API |
| One of two | Publisher API key from pub.kadam.net -> Profile -> API |
| No | Advertiser API URL (default: |
| No | Publisher API URL (default: |
| No | Log level: |
At least one API key must be provided. Tools for both products are always listed (for discoverability), but calling a tool without the corresponding key returns a clear setup instruction.
Tools (30)
Advertiser Tools (21)
Requires KADAM_ADV_API_KEY.
Campaigns
Tool | Description | Annotations |
| List campaigns with filters (folder, status, type, date, search) and pagination | readOnly |
| Create campaign with full targeting (countries, devices, OS, browsers, age, gender, audiences) | — |
| Update any campaign fields by ID | — |
| Bulk status change (active/paused/archived) for comma-separated IDs | idempotent |
Bid Management
Tool | Description | Annotations |
| Update bid for a single campaign (lightweight, no full payload). Falls back to current countries if omitted | idempotent |
| Update bids for multiple campaigns at once (all must share the same pricing model) | idempotent |
| Set per-site (zone) bids: static ( | idempotent |
Campaign Folders
Tool | Description | Annotations |
| List folders with campaign counts and budgets | readOnly |
| Create a new folder (name min 4 chars) | — |
| Update folder budgets and distribution | — |
Creatives
Tool | Description | Annotations |
| List creatives by campaign, status, or search query | readOnly |
| Create creative for a campaign (goes through moderation) | — |
| Update creative fields | — |
| Bulk status change for creatives | idempotent |
Audiences
Tool | Description | Annotations |
| List audiences with search and sorting | readOnly |
| Get detailed audience info by ID | readOnly |
| Create audience (pixel, code, fingerprint, or S2S) | — |
| Update audience settings | — |
| Delete audience permanently (requires | destructive |
Finance & Statistics
Tool | Description | Annotations |
| Transaction history (deposits, charges, refunds) | readOnly |
| Unified statistics — 3 report types via | readOnly |
Publisher Tools (9)
Requires KADAM_PUB_API_KEY.
Sites (Sources)
Tool | Description | Annotations |
| List publisher sites with stats | readOnly |
| Add a new site (starts verification flow) | — |
| Get detailed site info | readOnly |
| Update site name | — |
| Change site status (active/paused/archived/unarchived) | idempotent |
Ad Units
Tool | Description | Annotations |
| List ad units for a site, filter by format (native/banner/push/popunder/inpagepush) | readOnly |
| Change ad unit status (active/paused/archived/restored) | idempotent |
User & Statistics
Tool | Description | Annotations |
| Get publisher account info and balance | readOnly |
| Publisher statistics with human-readable dimension/metric mapping | readOnly |
Resources (7)
Static reference data the agent can read before calling tools:
URI | Description |
| All ad format types with IDs, features, pricing, and creative specs |
| CPC, CPM, CPV, CPA Target with IDs and descriptions |
| Creative requirements per campaign type |
| Publisher ad unit formats with IDs |
| Publisher site lifecycle states |
| Available dimensions and metrics for statistics tools |
| General Kadam API capabilities overview |
Prompts (4)
Pre-built workflow templates that guide the agent through multi-step operations:
Prompt | Description | Arguments |
| Step-by-step campaign creation (check types -> create folder -> create campaign -> add creatives) |
|
| Campaign performance analysis with optimization recommendations |
|
| Analyze site performance and suggest blacklist/whitelist changes |
|
| Full account overview — campaigns, spend, top performers | — |
Architecture
src/
├── index.ts # Entry point, server instructions, transport
├── config.ts # Zod-validated env config with cache
├── errors.ts # AuthError class
├── logger.ts # Pino structured logging (stderr)
├── output-formatter.ts # Text formatting + 50KB truncation
├── middleware/
│ └── tool-wrapper.ts # Auth, error handling, logging middleware
├── api/
│ ├── http-client.ts # Generic HTTP client with retry/429/timeout
│ ├── partners-client.ts # Advertiser API (lazy singleton)
│ └── pub-client.ts # Publisher API (lazy singleton)
├── utils/
│ ├── pagination.ts # Shared pagination extraction
│ ├── cache-once.ts # Generic async cache-once utility
│ └── dimension-mapper.ts # Stats dimension name→ID resolution
├── types/
│ ├── common.ts # Shared types (ApiListResponse, ReportConfig)
│ ├── advertiser.ts # Campaign, Creative, Audience types + maps
│ ├── publisher.ts # Source, AdUnit, PubUser types + maps
│ └── tool-module.ts # ToolModule interface
├── tools/
│ ├── advertiser/ # 21 tools across 6 modules
│ └── publisher/ # 9 tools across 4 modules
├── resources/ # 7 static reference resources
└── prompts/ # 4 workflow promptsKey Design Decisions
ToolWrapper middleware — centralized auth validation, error formatting, and logging for all 30 tools
Lazy singleton API clients — one
HttpClientinstance per product, created on first useOutput truncation — hard 50KB limit per response with
maxResults(default 25, max 100) to prevent LLM context overflowHuman-readable output — formatted tables, aligned entities, pagination metadata instead of raw JSON
Tool annotations —
readOnlyHint,destructiveHint,idempotentHintto guide agent behaviorServer instructions — usage patterns and constraints sent to the LLM on connection
Dimension mapping — stats tools accept human-readable names ("clicks", "spend") and resolve them to API IDs internally
Development
Prerequisites
Node.js >= 18
npm
Setup
git clone https://github.com/kadam-official/mcp-server.git
cd mcp-server
npm install
cp .env.example .env # Fill in your API keysCommands
npm run dev # Watch mode with tsx
npm run build # Production build with Vite
npm run start # Run built server
npm run typecheck # TypeScript check
npm run lint # ESLint
npm run format # Prettier
npm test # Run 82 tests
npm run test:coverage # Tests with V8 coverage
npm run inspect # MCP Inspector (visual debugger)Testing
202 tests across 23 files using Vitest + MCP SDK InMemoryTransport:
Unit tests — output formatter, config, HTTP client (mocked fetch)
Middleware tests — ToolWrapper auth, error formatting, logging
Integration tests — full server with all 30 tools, 7 resources, 4 prompts via in-memory MCP client
Tool handler tests — each tool module with mocked API clients
npm test
# Test Files 23 passed (23)
# Tests 202 passed (202)MCP Inspector
The MCP Inspector provides a visual interface for testing:
npm run build
npm run inspectDeployment
Docker
docker build -t kadam-mcp-server .
docker run -i --rm -e KADAM_ADV_API_KEY=... kadam-mcp-serverCI/CD
The .gitlab-ci.yml pipeline includes:
lint — ESLint + TypeScript check
test — Vitest with coverage
build — Vite production build
publish — npm publish + Docker push (manual trigger)
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/kadam-official/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server