Scalekit Auth Stack for coding agents
Setting up enterprise auth in a new codebase used to mean reading docs, copying boilerplate, and wiring up SDKs by hand. We've packaged that entire workflow into a plugin for every major coding agent.
One command installs the Scalekit Auth Stack into Claude Code, GitHub Copilot CLI, Codex, Cursor, Windsurf, Cline, and 40+ agents via the Vercel Skills CLI. The plugin gives your agent full awareness of the Scalekit API — reducing hallucinations and generating production-ready code from a single natural-language prompt.
Supported auth types: full-stack auth, MCP auth, modular SSO, modular SCIM, and agent auth.
Learn more: docs.scalekit.com/dev-kit/build-with-ai

If you are building Agents: Add delegated OAuth within coding agents
When your agent needs to act on behalf of a real user — reading their inbox, posting to Slack, updating a CRM record — it needs a token. Getting, storing, and refreshing that token is auth plumbing. AgentKit handles it so your agent doesn't have to.
The flow is four steps: initialize the SDK, create a connected account per user, generate an authorization link for them to complete the OAuth flow, then call execute_tool. Scalekit manages the token lifecycle, credential storage, and API proxy. Credentials never touch the agent runtime.
Gmail is enabled by default. Every other connector — Slack, Salesforce, Notion, and 100+ more — follows the same pattern: one connection, one authorization link, one tool call.
Quickstart: docs.scalekit.com/agentkit/quickstart
.png)