> **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/)

---

# Add your own connector

Add custom connectors and extend coverage while keeping authentication and authorization in Scalekit.
Add your own connector when the API or MCP server you need is not available in Scalekit's built-in catalog — custom connectors support any SaaS API, partner system, internal API, or remote MCP server 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 perform tool calling.

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

> Image: Custom connector shown alongside built-in connectors in the connector selection view

## Why add your own connector

Adding your own connector lets you:

- Extend beyond the built-in connector catalog without inventing a separate auth stack
- Bring unsupported SaaS APIs, partner systems, internal APIs, and remote MCP servers 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 calls through Tool Proxy (REST) or tool calling (MCP) using the same runtime model as other integrations

## How adding your own connector works

Adding 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. Call tools — via Tool Proxy (`actions.request()`) for REST API connectors, or via MCP tool calling for MCP connectors

Creating the connector definition tells Scalekit how to authenticate to the upstream API or MCP server. After that, connections, connected accounts, user authorization, and the call runtime 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 |