Skip to main content
Scrip MCP exposes task-oriented tools for operating a whole rewards program. Most tools answer a complete operator question, such as “why did this event fail?” or “where did this balance come from?” Every tool name starts with scrip_. Dedicated write tools do not register at https://mcp.scrip.dev/mcp while it is read-only. scrip_test_run and scrip_test_rule_configuration still register so you can fetch an existing run. Starting a run needs writes and is rejected.

Programs and reporting

Participants and groups

Redemptions and rewards

Rules

Documentation and API coverage

Use scrip_search_docs before drafting rules or calling unfamiliar endpoints. Prefer a dedicated tool when one covers the task. Use scrip_api_get or scrip_api_mutate only when no dedicated tool exists.

Changing data

The hosted server is currently read-only. Dedicated write tools, such as saving a rule, applying a configuration, adjusting a balance, and reversing a redemption, do not appear on https://mcp.scrip.dev/mcp. scrip_test_run and scrip_test_rule_configuration still appear. Starting a run needs writes and is rejected. Pass test_run_id to fetch a run that already exists. Dedicated write tools register only when the deployment enables writes, and only when the connection can write. Your MCP client may also ask for approval before a change runs. Scrip records changes through the same audited API paths used by the dashboard and REST API. On the hosted server, simulate one rule with scrip_test_rule and plan a draft with the configuration workflow above. Start a configuration test run from the REST API. Apply, save, adjust, and reverse from the dashboard or REST API until hosted write-mode is enabled.