Builder setup
Builders need Claude and their normal work account. They do not need Azure CLI, cloud accounts, npm, or a local Sprig configuration file.
Before the first build, a Claude tenant administrator uploads the current sprig-data,
sprig-publish, and sprig-diagnostics archives from Admin > Setup > Skills. See
How Claude knows what to do. Builders do not download skills from the
private Sprig repository or install a personal marketplace plugin.
claude.ai
Section titled “claude.ai”Open the Sprig connector and send a message that needs Sprig, such as “build a dashboard from claims data.” The first request starts a normal Microsoft sign-in. If the connector is absent, ask an organization administrator to follow Claude connector and admin consent.
Claude Code
Section titled “Claude Code”Connect the gateway as a native MCP server:
claude mcp add --transport http sprig https://gateway.<apps-domain>/mcp \ --client-id <cli-client-id> --callback-port 8899claude mcp login sprig<cli-client-id> is the public sprig-cli client id from the install descriptor. Ask Ops for it.
It is not a secret. The sign-in opens in a browser and Claude Code caches the resulting token.
Ask Claude to check the Sprig skill version before the first build and after a Sprig upgrade.