> **Building with AI coding agents?** If you're using an AI coding agent, install the official Scalekit plugin. It gives your agent full awareness of the Scalekit API — reducing hallucinations and enabling faster, more accurate code generation.
>
> - **Claude Code**: `/plugin marketplace add scalekit-inc/claude-code-authstack` then `/plugin install <auth-type>@scalekit-auth-stack`
> - **GitHub Copilot CLI**: `copilot plugin marketplace add scalekit-inc/github-copilot-authstack` then `copilot plugin install <auth-type>@scalekit-auth-stack`
> - **Codex**: run the bash installer, restart, then open Plugin Directory and enable `<auth-type>`
> - **Skills CLI** (Windsurf, Cline, 40+ agents): `npx skills add scalekit-inc/skills --list` then `--skill <skill-name>`
>
> `<auth-type>` / `<skill-name>`: `agentkit`, `full-stack-auth`, `mcp-auth`, `modular-sso`, `modular-scim` — [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Bring your own connector

Bring your own connector lets you add custom connectors when the API you need is not available as a built-in connector.

Use bring your own connector to support unsupported SaaS APIs, partner systems, and internal APIs while keeping authentication, authorization, and secure API access in Scalekit.

Once the connector is created, you use the same flow as other connectors: create a connection, create or fetch a connected account, authorize the user, and call the upstream API through Tool Proxy.

Custom connectors appear alongside built-in connectors when you create a connection in Scalekit:

![Custom connector shown alongside built-in connectors in the connector selection view](@/assets/docs/agentkit/bring-your-own-connector/custom-provider-in-catalog.png)

## Why use bring your own connector

Bring your own connector lets you:

- Extend beyond the built-in connector catalog without inventing a separate auth stack
- Bring unsupported SaaS APIs, partner systems, and internal APIs into the same secure access model
- Reuse connections, connected accounts, and user authorization instead of building one-off auth plumbing
- Keep credential handling, authorization, and governed API access centralized in Scalekit
- Move from connector definition to live upstream API calls through Tool Proxy using the same runtime model as other integrations
**Note:** Custom connectors route all API calls through Tool Proxy. Direct SDK calls to the upstream API are not supported.

## How bring your own connector works

Bring your own connector uses the same model as built-in connectors:

1. Create a connector definition
2. Create a connection in Scalekit Dashboard
3. Create a connected account and authorize the user
4. Use Tool Proxy to call the upstream API

Creating the connector defines how Scalekit should authenticate to the upstream API. After that, connections, connected accounts, user authorization, and Tool Proxy work the same way as they do for built-in connectors.

---

## 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 |