Skip to main content
Scrip MCP is a hosted Model Context Protocol server at https://mcp.scrip.dev/mcp. After you sign in and approve access, supported AI clients can operate your whole Scrip rewards program. That includes programs, assets, participants, groups, rules, the ledger, redemptions, and reporting. The same audited API paths used by the dashboard and REST API back every tool.

​
What you can do

  • Inspect a program’s assets, rule sets, rules, tiers, and configuration.
  • Explain participant and group balances, including lots, statements, and where value came from.
  • Trace why an event earned, failed, or created ledger entries.
  • Review redemptions, rewards, pending inventory, and reversal history.
  • Ground event fields, then draft, validate, lint, and test rules.
  • Plan a complete multi-set configuration and inspect the preview, diff, and warnings.
  • Inspect immutable configuration history and preview a forward rollback.
  • Pull program reporting for activity, liability, expiration, and ledger integrity.

​
How access works

The hosted connection uses OAuth through Scrip sign-in. It does not accept Scrip API keys. The hosted server at https://mcp.scrip.dev/mcp is currently read-only. Dedicated write tools do not register there. Saving a rule, applying a configuration, adjusting a balance, and reversing a redemption stay on the dashboard, the REST API, or a local MCP connection with writes enabled. scrip_test_run and scrip_test_rule_configuration still appear. Starting a run is rejected. Pass test_run_id to fetch a run that already exists.

​
Configure several rules

The hosted MCP server can read, lint, and plan. It cannot start a test run or apply a configuration. For a change that spans several rules or sets:
  1. scrip_get_rule_configuration reads the current revision.
  2. scrip_get_event_shapes checks schemaless event.* fields against recent traffic.
  3. scrip_lint_rule_configuration analyzes interactions across the draft.
  4. Start a rollback-only test run from the REST API. On the hosted server, scrip_test_rule_configuration only fetches an existing run when you pass test_run_id.
  5. scrip_plan_rule_configuration returns the server preview, diff, warnings, and final sequence.
  6. Apply the preview from the dashboard or REST API. scrip_apply_rule_configuration is a write tool and does not register on the hosted server.
  7. scrip_get_rule_configuration_history audits revisions or previews a rollback.
Express moves as first, last, before, or after. Do not calculate numeric order values. See Managing rule configuration for the same sequence in REST.

​
Connect

Connect a client

Add Scrip MCP to Claude Code, Claude, Cursor, Zed, or another OAuth-capable MCP client.

Tools

See the tools exposed by Scrip MCP and what each one is for.
For static AI context such as llms.txt and the OpenAPI schema, see AI resources.