> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connector Building

> Build, customize, test, and publish your own connectors.

Need a connector that isn't in the catalog yet? Request it from StackOne, or build it yourself.

## When to build a custom connector

<CardGroup cols={2}>
  <Card title="Internal Systems" icon="building">
    Connect proprietary APIs or custom-built tools
  </Card>

  <Card title="Provider-Specific Actions" icon="plus">
    Add actions not covered by standard connectors
  </Card>

  <Card title="Niche Providers" icon="puzzle-piece">
    Support vertical-specific SaaS not in our catalog
  </Card>

  <Card title="Custom Mappings" icon="arrows-rotate">
    Transform data to match your requirements
  </Card>
</CardGroup>

## How it works

A connector is a YAML definition of how to interact with a provider's API. Once published, StackOne exposes it through every protocol automatically:

<CardGroup cols={3}>
  <Card title="RPC/HTTP" icon="code" href="/embed/call-actions/rpc-http">
    REST endpoints at `api.stackone.com` for backend integrations
  </Card>

  <Card title="MCP" icon="robot" href="/embed/call-actions/mcp">
    Model Context Protocol for agents like Claude Code and Cursor
  </Card>

  <Card title="Agent SDK" icon="wrench" href="/embed/call-actions/agent-sdk">
    TypeScript and Python SDKs built for LLM tool calling
  </Card>
</CardGroup>

Write the connector once and it works across all of them, whether your users are building traditional apps, agents, or both.

## Two ways to add a connector

<Columns cols={2}>
  <Column>
    ### StackOne Request

    <Frame>
      <img src="https://mintcdn.com/stackone-60/eqCjS7m4FAN_3XTx/images/connectors/request-stackone.svg?fit=max&auto=format&n=eqCjS7m4FAN_3XTx&q=85&s=1329dfe7e442d80e4e9d578f3b2793b4" alt="StackOne connector build process: you request a connector, StackOne builds it through automated QA, AI optimization, and manual QA, then delivers it for you to use or fork" width="600" height="420" data-path="images/connectors/request-stackone.svg" />
    </Frame>

    <Card>
      StackOne builds and maintains the connector for you. Delivery defined for plans with SLAs.

      * **Fast turnaround:** typically days, not weeks (when API access is provided).
      * **Full support:** StackOne handles API mapping and authentication.
      * **QA pipeline:** AI-driven optimization and manual verification.
      * **Fork & customize:** optionally fork and edit actions after delivery.

      **[Request it from StackOne](https://www.stackone.com/demo)**
    </Card>
  </Column>

  <Column>
    ### Build it yourself

    <Frame>
      <img src="https://mintcdn.com/stackone-60/eqCjS7m4FAN_3XTx/images/connectors/build-your-own.svg?fit=max&auto=format&n=eqCjS7m4FAN_3XTx&q=85&s=02481cc7794c5e1759c2220e44f6507c" alt="AI-assisted connector development workflow: your prompt goes to your coding assistant, which uses StackOne's MCP and skills to research, build, and test a connector.yaml that you deploy through your own CI/CD" width="600" height="420" data-path="images/connectors/build-your-own.svg" />
    </Frame>

    <Card>
      Connectors are defined as code, so you build and publish them on your own schedule.

      * **AI-assisted:** use StackOne's MCP and skills to turn provider docs into YAML.
      * **Test locally:** run actions against a sandbox account before publishing.
      * **Full control:** version, test, and publish when you choose.
      * **Your environments:** publish through your existing CI/CD.

      **[Build it yourself](/connector-building/first-connector)**
    </Card>
  </Column>
</Columns>