Skip to main content
Need a connector that isn’t in the catalog yet? Request it from StackOne, or build it yourself.

​
When to build a custom connector

Internal Systems

Connect proprietary APIs or custom-built tools

Provider-Specific Actions

Add actions not covered by standard connectors

Niche Providers

Support vertical-specific SaaS not in our catalog

Custom Mappings

Transform data to match your requirements

​
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:

RPC/HTTP

REST endpoints at api.stackone.com for backend integrations

MCP

Model Context Protocol for agents like Claude Code and Cursor

Agent SDK

TypeScript and Python SDKs built for LLM tool calling
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

​
StackOne Request

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

​
Build it yourself

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