Connect a client - Scrip Docs

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

Authentication

The hosted server accepts OAuth access tokens only. A Scrip API key sent as Authorization: Bearer sk_... or X-API-Key: sk_... returns 401 with the error code direct_api_key_not_supported and a WWW-Authenticate header pointing at the OAuth metadata. The key is not used against the Scrip API. Sign-in requests openid email profile from Scrip auth. After you choose an organization, Scrip stores scrip:read and optionally scrip:write on the MCP grant. Those are Scrip permissions, not OAuth scopes. Clients must not request scrip:read or scrip:write from the sign-in server. To call Scrip with an API key, use the REST API.

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:

Field	Value
Name	`Scrip`
URL	`https://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

Use the same Scrip account you use in the dashboard.

Choose an organization

Select the organization this client can access.

Approve access

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

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.

Troubleshooting

Keep one Cursor window open while connecting. Approve access in your browser within two minutes. If Cursor still shows Needs login after approval, quit Cursor completely, then reopen it. Reload Window is not enough. Check ~/.cursor/projects/<workspace>/mcps/user-scrip/tools/. If it has files, you’re already connected. Restart Cursor instead of reconnecting Scrip.

Authorization expired or already used

Restart the connection from the MCP client. Do not retry Authorize on a leftover consent page. If the client still fails, disconnect the server and add it again.

Wrong organization

Authorizing the same client for another organization replaces the previous grant for that user and client. Remove the app from Settings > Connected apps, then reconnect and choose the organization you want.

Tools missing or writes blocked

Hosted https://mcp.scrip.dev/mcp is currently read-only. Dedicated write tools do not appear. scrip_test_run and scrip_test_rule_configuration still appear, but starting a run is rejected. If view tools fail, confirm you signed in with an account that can access that organization. For local write tools, first set SCRIP_MCP_ENABLE_WRITES=true on that process. Local API-key and stdio connections have no OAuth consent step. Writes then follow the API key’s Scrip capabilities. A local OAuth HTTP connection still needs a grant with scrip:write after you approve access.

The client blocked a tool

Your MCP client can allow, require approval, or block individual tools. Unblock the tool in the client, then retry.

Disconnect the client

Remove the connection from Settings > Connected apps, then remove the server from the MCP client.

​Connection settings

​Authentication

​Claude Code

​Claude, Cursor, Zed, and other clients

​Approve access

​Verify the connection

​Manage access

​Troubleshooting

​Cursor still shows “Needs login”

​Authorization expired or already used

​Wrong organization

​Tools missing or writes blocked

​The client blocked a tool

​Disconnect the client

Connection settings

Authentication

Claude Code

Claude, Cursor, Zed, and other clients

Approve access

Verify the connection

Manage access

Troubleshooting

Cursor still shows “Needs login”

Authorization expired or already used

Wrong organization

Tools missing or writes blocked

The client blocked a tool

Disconnect the client