> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP server
> Connect AI clients to your Scrip organization
Scrip MCP is a hosted [Model Context Protocol](https://modelcontextprotocol.io) server at `https://mcp.scrip.dev/mcp`. It lets supported AI clients work with your Scrip organization after you sign in and approve access.
Use it when you want an assistant to inspect programs, explain balances, trace events, review rules, or make approved changes from your development tools.
## What you can do
* Inspect a program's assets, rules, tiers, and configuration.
* Explain participant and group balances, including where value came from.
* Trace why an event earned, failed, or created ledger entries.
* Review redemptions, rewards, and reversal history.
* Draft, validate, and test rules before saving them.
* Pull program reporting for activity, liability, expiration, and ledger integrity.
* Make approved changes, such as saving a rule, adjusting a balance, or reversing a redemption.
## How access works
The hosted connection uses OAuth through Scrip sign-in.
| Layer | What it controls |
| ---------------------- | -------------------------------------------------------------------- |
| Scrip sign-in | Confirms your identity. |
| Organization selection | Limits the connection to one Scrip organization. |
| Scrip role | Determines which data and actions your account can access. |
| Client permissions | Lets you allow, approve, or block individual tools in the AI client. |
Write tools only run when both Scrip and your MCP client allow them.
## Connect
Add Scrip MCP to Claude Code, Claude, Cursor, Zed, or another OAuth-capable MCP client.
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](/ai-resources).