



StackOne connectors are defined as simple YAML configuration files which gives you full programatic control over the integration logic. Once deployed, the StackOne Execution Engine automatically exposes your actions through the API, MCP servers, A2A protocol and AI Action SDK simultaneously—like it does for 200+ enterprise apps and 10,000 actions already available on the platform.
You may download existing connectors to understand the YAML structure:
# Download a connector as reference
stackone pull --connector notion --profile ProductionToday we're releasing the StackOne CLI, bringing connector management directly to your terminal. Pull connectors, validate configurations, test actions locally, and push updates - all without leaving your development environment. Let's dive in.
StackOne CLI: What's New:
stackone run, using inline configuration or linked account credentials for rapid iterationThe StackOne CLI uses the Execution Engine that runs actions for over 200+ pre-built connectors. Connectors you build work seamlessly across REST APIs, MCP servers and AI toolsets simultaneously - no separate implementations needed.
Whether you need to integrate with an internal system, add custom actions to existing connectors or build tenant-specific configurations, the CLI gives you the same powerful capabilities StackOne uses internally. Pull existing connectors as a starting point, customize them for your requirements and push updates back - all whilst maintaining quality and consistency.
The CLI is designed for rapid development cycle. The pull command works similar to Git - you can fork StackOne's connectors, maintain your customizations and selectively merge updates when they're released.
Use stackone validate --watch to catch errors as you type. Test actions locally with stackone run before pushing to production. Pull updates from StackOne's registry and merge them into your customised connectors using interactive conflict resolution.
Multiple profile support lets you manage different environments (staging, production) with separate configurations, making it straightforward to integrate the CLI into your existing CI/CD pipelines.
Ready to get started?
npm install -g @stackone/clistackone init with your API keystackone pull, edit, stackone validate, stackone run, then stackone push| Command | Description |
|---|---|
| init | Create and store configuration profiles with your API credentials |
| get | Retrieve a connector from the registry |
| pull | Fetch a connector from the registry and save it locally with conflict resolution |
| validate | Check that connector files are valid and properly formatted |
| run | Execute a connector action locally for testing and debugging |
| push | Upload connector files to the StackOne API registry |
| drop | Delete a specific connector version from the registry |
Want to learn more?