@perkamo/mcp
v0.7.0
Published
Model Context Protocol server for Perkamo loyalty and gamification operations.
Readme
Perkamo MCP Server
Perkamo MCP exposes loyalty and gamification operations to MCP-compatible clients such as Claude Desktop and Codex.
The adapter supports the stable MCP 2026-07-28 protocol and legacy clients
through 2025-11-25. Modern HTTP requests are stateless; existing legacy
Streamable HTTP sessions remain compatible.
Hosted OAuth MCP
Use the hosted Perkamo MCP endpoint when your client supports remote MCP servers. No npm package or server API key is required on your machine.
https://api.perkamo.com/mcpClaude and Claude Desktop
For Claude.ai or Claude Desktop, add a custom connector with the hosted URL above. Claude will connect to the remote MCP server and open the Perkamo OAuth flow when you connect the integration.
In Claude Code, add the remote HTTP server from a terminal:
claude mcp add --transport http perkamo https://api.perkamo.com/mcpThen start Claude Code, run /mcp, choose Perkamo and complete the browser
login. Add --scope user if you want the connector available in every project.
Codex
In Codex CLI, add the Streamable HTTP server and authenticate it:
codex mcp add perkamo --url https://api.perkamo.com/mcp
codex mcp login perkamo --scopes mcp:readReconnect with --scopes mcp:read,mcp:write only for an
operator-supervised change.
Hosted OAuth works across every Space available to the connected console user.
Call get_connection_status and list_spaces, then pass spaceId directly to
tools. Browser Space switching or another sign-in is not required.
Local stdio adapter
Use the npm package only when your client cannot connect to the hosted remote MCP endpoint, or when you need a private bridge deployment:
npm install -g @perkamo/mcp
PERKAMO_SERVER_API_KEY=sk_test_... \
perkamo-mcpMutating tools require PERKAMO_MCP_ALLOW_MUTATIONS=true. Server API keys that
target a Live Space also require confirmProduction: true after explicit user
approval; Test Space work does not require repetitive confirmations. The key
must include the API scope required by each operation.
A server API key belongs to exactly one Space. The local adapter can read that
Space's program, usage and customers; ingest trusted events; redeem rewards;
adjust customer state; validate config locally; and upload config modules.
list_spaces returns only the keyed Space, and explicit spaceId targeting is
rejected.
Organization discovery, multi-Space access, program copying, entity duplication, whole-program validation, event simulation, transaction receipts and customer ledger reads require the hosted OAuth MCP endpoint. Run one separately keyed local adapter per Space only when hosted OAuth is not suitable.
