> ## 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.

# Connect a client

> Add Scrip MCP to Claude Code, Claude, Cursor, and other clients

Add `https://mcp.scrip.dev/mcp` as a remote HTTP MCP server. Your client opens Scrip sign-in, then stores the OAuth token after you approve access.

## Connection settings

| Setting        | Value                       |
| -------------- | --------------------------- |
| Server URL     | `https://mcp.scrip.dev/mcp` |
| Transport      | HTTP                        |
| Authentication | OAuth through Scrip sign-in |

## Claude Code

Run this command from your project:

```bash theme={null}
claude mcp add --transport http scrip https://mcp.scrip.dev/mcp
```

Then open Claude Code, run `/mcp`, and authenticate the `scrip` server.

## Claude, Cursor, Zed, and other clients

Add a custom MCP server with:

| Field | Value                       |
| ----- | --------------------------- |
| Name  | `Scrip`                     |
| URL   | `https://mcp.scrip.dev/mcp` |

For clients that use an `mcpServers` config block:

```json theme={null}
{
  "mcpServers": {
    "scrip": {
      "url": "https://mcp.scrip.dev/mcp"
    }
  }
}
```

OAuth-capable clients open the Scrip authorization flow in your browser.

## Approve access

<Steps>
  <Step title="Sign in to Scrip">
    Use the same Scrip account you use in the dashboard.
  </Step>

  <Step title="Choose an organization">
    Select the organization this client can access.
  </Step>

  <Step title="Approve access">
    Review what the client can view or change, then approve the connection.
  </Step>

  <Step title="Return to the client">
    Your MCP client completes the connection and loads the Scrip tools.
  </Step>
</Steps>

## Verify the connection

Ask the client to run `scrip_ping`. It confirms that the server is reachable and your Scrip connection is active.

A good first prompt is:

```text theme={null}
Use scrip_get_program_overview to show me the programs this connection can access.
```

## Manage access

The connection follows your Scrip account, organization, and role. It cannot access organizations your account cannot access.

Your MCP client still controls when individual tools can run. Most clients let you allow tools automatically, require approval, or block them.

Remove connected MCP clients from **Settings** > **Connected apps** in the Scrip dashboard.