Skip to main content
PlayCamp provides Claude Code agents that automate SDK integration. Instead of manually writing API calls, you can describe what you need in natural language — the agent will install the SDK, implement APIs, configure webhooks, and verify your setup.

​
Supported Categories

One all-in-one agent per language. Each agent covers the full integration lifecycle — setup, mandatory + extended APIs, webhooks, raw-HTTP migration, code audit, and build verification.
CategoryAgentDescription
Node SDK@agent-playcamp-nodeIntegration with @playcamp/node-sdk
Go SDK@agent-playcamp-goIntegration with github.com/playcamp/playcamp-go-sdk
API@agent-playcamp-apiDirect HTTP API guide for Python, Java, C#, PHP, etc.

​
Quick Start

1

Install agents

Run the installer in your game server project:
cd your-game-server
bash <(curl -fsSL https://raw.githubusercontent.com/PlayCamp/playcamp-sdk-agents/main/scripts/install.sh)
2

Launch Claude Code

claude
3

Ask

Integrate PlayCamp SDK with sponsor, coupon, and payment APIs
The agent automatically sets up the SDK, implements the required APIs, and configures error handling.

​
Install Options

# Install to current project (default)
bash <(curl -fsSL https://raw.githubusercontent.com/PlayCamp/playcamp-sdk-agents/main/scripts/install.sh)

# Install globally (~/.claude/agents/)
bash <(curl -fsSL ...install.sh) --global

# Install specific category only
bash <(curl -fsSL ...install.sh) --platform=node
bash <(curl -fsSL ...install.sh) --platform=go
bash <(curl -fsSL ...install.sh) --platform=api

# Uninstall (removes agents + routing rules from CLAUDE.md)
bash <(curl -fsSL ...install.sh) --uninstall

​
Agents

Each agent is a single, comprehensive agent that handles every role for its language. Just describe what you need — the agent selects the right mode.
ModeWhat it does
IntegrateSDK install, client init, mandatory + extended APIs (sponsors, coupons, payments, playtime, WebView OTT, bulk)
WebhooksEndpoint setup, signature verification, batch event handling (7 event types)
MigrateConvert raw HTTP (fetch/axios, net/http) to SDK methods
AuditRead-only code review for correctness, security, and best practices
VerifyBuild/compile, dependency, and environment-config checks

​
@agent-playcamp-node — Node SDK

Covers @playcamp/node-sdk: setup & client init, mandatory APIs (sponsor/coupon/payment), playtime sessions, bulk payments, WebView OTT, webhook reception & signature verification, raw HTTP → SDK migration, code audit, and TypeScript build/config verification.

​
@agent-playcamp-go — Go SDK

Same coverage for github.com/playcamp/playcamp-go-sdk, with Go idioms — errors.As(), context.Context, pointer helpers, webhookutil.Verify() signature verification, and go build/go vet verification.

​
@agent-playcamp-api — Direct HTTP API

For non-SDK languages (Python, Java, C#, PHP, Ruby, curl): endpoint docs, Bearer auth, request/response examples, webhook verification, and error handling.

​
Usage Examples

​
Node.js

Set up PlayCamp SDK in my Express server with payment, coupon, and sponsor endpoints

Add PlayCamp webhook handling with signature verification to my server

Record sponsored players' playtime sessions with PlayCamp

Review my PlayCamp integration for security issues, then verify the build

​
Go

Set up PlayCamp Go SDK in my server with sponsor, coupon, and payment APIs

Add PlayCamp webhook verification to my Go server using webhookutil

​
Direct API Integration (non-SDK)

Show me how to integrate PlayCamp payment API in Python

Set up PlayCamp sponsor and coupon APIs in my Java server

​
Migration

Migrate my raw fetch() calls to PlayCamp SDK methods

Migrate my net/http PlayCamp calls to the Go SDK

​
Explicit Agent Invocation

You can also call the agent directly by name: 
Use @agent-playcamp-node to integrate PlayCamp SDK with server key configuration

Use @agent-playcamp-go to set up webhook endpoints and verify the build
A full integration runs through one agent, switching modes as you ask:
  1. Integrate — install SDK, initialize clients, implement mandatory + extended APIs
  2. Webhooks — configure webhook endpoints and signature verification
  3. Audit — review the full integration for correctness and security (read-only)
  4. Verify — validate build, config, and environment setup
Use @agent-playcamp-node for every step. For a migration, start with “Migrate my raw fetch/axios calls to the PlayCamp SDK”, then ask it to audit and verify.
The same agent handles each step — no hand-off between separate agents required.

​
How It Works

The installer adds the agent file to .claude/agents/ and appends routing rules to your project’s CLAUDE.md. When you ask Claude Code about PlayCamp integration, the routing rules automatically delegate to the correct language agent. 
User: "Add PlayCamp payment processing"
  → Claude reads CLAUDE.md routing rules
    → Delegates to @agent-playcamp-node (or -go / -api)
      → Agent implements payment API with SDK
Agents have full access to read, write, and edit files in your project. They can install npm/Go packages, create modules, and modify your server code. In Audit and Verify modes the agent only reads and reports — it does not modify code.