> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended**:
> ```bash
> npx @scalekit-inc/cli setup
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for 40+ agents.
> Features: full-stack-auth, agent-auth, mcp-auth, modular-sso, modular-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Set up AgentKit with your coding agent

Add Scalekit Agent Auth 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

- A Scalekit account at [app.scalekit.com](https://app.scalekit.com)
- A connector configured under **AgentKit** > **Connections** (for example, `gmail`)
- Your API credentials from **Developers → API Credentials**

## Pick your coding agent

  ### Recommended: one command

```bash title="Terminal" frame="terminal" showLineNumbers=false
npx @scalekit-inc/cli setup
```

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

The CLI installs the authstack plugin (including Agent Auth skills) for your editor. Complete any browser OAuth prompt for the Scalekit MCP server.

Then paste the implementation prompt (or describe your goal naturally).

  ### Per-tool details

After the CLI (or if you prefer tool-native flows):

- Claude Code / Copilot: marketplace + plugin install is handled by the CLI.
- Cursor / Codex: plugins are installed locally by the CLI.
- 40+ agents: use the skills option in the CLI or `npx skills add scalekit-inc/authstack --skill integrating-agentkit`.

Use the prompt below.

## Verify the setup

1. **Set environment variables** — copy `SCALEKIT_CLIENT_ID`, `SCALEKIT_CLIENT_SECRET`, and `SCALEKIT_ENV_URL` from the dashboard → **API Credentials**.
2. **Trigger the authorization flow** — run the generated example and confirm the browser redirects to the connector's consent page.
3. **Fetch a token** — after consent, call the token-fetch function and confirm you receive a valid response.

> caution: Review generated code before deploying
>
> Verify that token validation logic, error handling, and environment variable references match your application's requirements. The generated code is a foundation, not a finished implementation.

## 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, the OAuth flow will fail at runtime with a "connector not found" error.

Fix: in the [Scalekit Dashboard](https://app.scalekit.com), 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 token-fetch call. 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.


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |