Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nippy.la/llms.txt

Use this file to discover all available pages before exploring further.

What is the Nippy MCP

Nippy’s MCP (Model Context Protocol) exposes the entire operational engine of the platform as tools that any AI agent can invoke. Instead of opening the console, navigating menus, and exporting reports, you ask directly:
  • “How many active campaigns do we have this week and which one has the best conversion?”
  • “Create a roulette for the summer campaign with 500 points as the main prize”
  • “Which products are below minimum stock at the Monterrey center?”
The agent executes the operations, fetches data, and acts — all in seconds.

How it relates to the SDK

The SDK and MCP access the same engine. They are two perspectives on the same system:
SDKMCP
Who uses itThe end user (in your app)Your team or AI agent
How it’s accessednpm package embedded in your appMCP client: Claude, Cursor, OpenClaw, Hermes
What it doesThe user spins, wins, claimsThe agent creates campaigns, analyzes, manages
Real-timeYes — every spin is synchronousYes — operations happen instantly
A bank can use both simultaneously: the SDK runs in the customer’s app, the MCP runs in the marketing team’s workspace.

Available verticals

The Nippy MCP exposes six operational areas. Each vertical has its own tools that the agent discovers automatically upon connecting.

Analytics

Query roulette, supply, course, and attendance data. Your agent builds the query and returns results — no SQL, no Excel.

Supply

Stock levels by center, withdrawals, low inventory alerts. Create and update from chat.

Roulettes

Create and manage gamification campaigns from the agent. Full flow: proposal, inventory validation, publishing.

Flows

Registration landing pages for campaigns. Configure fields, redirects, and review conversion in real-time.

Learning

Courses, enrollments, exams, and certificates. Create and update without opening the platform.

Compatible clients

The server uses MCP over HTTP streamable (JSON-RPC 2.0). It works with any client that implements the protocol:
  • Claude Desktop — native integration, tools appear in chat
  • Cursor — agent with direct engine access from the editor
  • OpenClaw — MCP-compatible local runtime
  • Hermes Agent (NousResearch) — open source agent with native MCP client

Connect in 3 steps

API key → configure client → first operation. Ready in minutes.