Skip to main content
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

SettingValue
Server URLhttps://mcp.scrip.dev/mcp
TransportHTTP
AuthenticationOAuth through Scrip sign-in

​
Claude Code

Run this command from your project: 
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:
FieldValue
NameScrip
URLhttps://mcp.scrip.dev/mcp
For clients that use an mcpServers config block: 
{
  "mcpServers": {
    "scrip": {
      "url": "https://mcp.scrip.dev/mcp"
    }
  }
}
OAuth-capable clients open the Scrip authorization flow in your browser.

​
Approve access

1

Sign in to Scrip

Use the same Scrip account you use in the dashboard.
2

Choose an organization

Select the organization this client can access.
3

Approve access

Review what the client can view or change, then approve the connection.
4

Return to the client

Your MCP client completes the connection and loads the Scrip tools.

​
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: 
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.