Skip to content
Scalekit Docs
Talk to an Engineer Dashboard
DEVELOPER KIT
Tools and examples to accelerate your integration
Build with AIIntegrate auth with AI coding agents
Reference & toolingImplement auth with SDKs, REST APIs, OpenAPI specs, and Postman collections
Testing UtilitiesTest and debug auth integrations locally
RESOURCES
Guides, references, and community resources
IntegrationsConnect external identity providers and platforms
WorkflowsAutomate user lifecycle and auth events with webhooks
CookbooksImplement common patterns with step-by-step recipes
Code SamplesCopy and adapt code examples by language

Set up AgentKit with your coding agent

Add Scalekit AgentKit to your codebase using Claude Code, Codex, GitHub Copilot CLI, Cursor, or any of 40+ coding agents.

Install the authstack plugin into your coding agent and paste one prompt. The agent generates client initialization, connected account management, OAuth authorization, and token handling — no boilerplate required.

Before you start

Section titled “Before you start”
  • A Scalekit account at app.scalekit.com
  • A connector configured under AgentKit > Connections. The prompt defaults to GitHub (github-connect). Name another connector if you want that instead.
  • Your API credentials from Developers > Settings > API Credentials

Pick your coding agent

Section titled “Pick your coding agent”
Terminal
npx @scalekit-inc/cli setup

For repeated use: npm install -g @scalekit-inc/cli then scalekit setup.

The CLI installs the authstack plugin for your editor. Then load the shipped skill integrate-agentkit. Complete any browser OAuth prompt for the Scalekit MCP server.

Done: the command exits 0 and integrate-agentkit is available.

Then copy the AgentKit prompt below (or describe your goal naturally).

Using a coding agent?

Verify the setup

Section titled “Verify the setup”
  1. Set environment variables — copy SCALEKIT_CLIENT_ID, SCALEKIT_CLIENT_SECRET, and SCALEKIT_ENVIRONMENT_URL from Developers > Settings > API Credentials in the dashboard. Done: all three names are set in .env.
  2. Trigger the authorization flow — run the generated example and confirm the browser redirects to the connector’s consent page. Done: the consent page opens.
  3. Call a tool — after consent, run a read-only tool through Scalekit, such as github_user_get_authenticated for GitHub. Done: the tool call returns data from the connector.

Troubleshooting

Section titled “Troubleshooting”
The agent generated code for a connector I haven’t configured yet

The plugin uses the connector name you provide in the prompt. If that connector isn’t configured in your Scalekit Dashboard, creating the authorization link fails with connection not found for the given key.

Fix: in the Scalekit Dashboard, go to AgentKit > Connections > Create Connection, finish the connection, then re-run the agent prompt with the exact connection name from the dashboard.

I want to swap connectors after the initial generation

Re-run the implementation prompt with the new connector name. The agent updates the connector reference in the client initialization and regenerates the tool calls. Existing connected accounts for the old connector are not affected.

The scaffolded code references an SDK version that doesn’t match my lockfile

The plugin targets the latest stable Scalekit SDK. If your lockfile pins an older version, either upgrade the SDK (npm install @scalekit-sdk/node@latest or equivalent) or ask the agent to regenerate using your pinned version by adding “use SDK version X.Y.Z” to the prompt.