Yes. The Slack CLI is free and open-source under the Apache 2.0 license. Develop and deploy apps at no CLI cost. Slack's managed hosting (`slack deploy`) has usage limits tied to your workspace plan. Self-hosted Bolt apps have no Slack-imposed limits.

What is the difference between Bolt and Deno Slack apps?

Bolt is Slack's framework for Node.js, Python, or Java. You host the app yourself. Deno apps run on Slack's managed platform with built-in hosting, datastores, and workflows. The CLI supports both. Bolt apps use manifest.json. Deno apps define manifests in TypeScript. Your agent can scaffold and deploy either type.

Can I use Slack CLI with an existing Slack app?

Yes. Run `slack app link` to connect the CLI to an existing app. Your agent can then manage the manifest, deploy updates, and use local development mode with apps originally created through the web UI. No need to recreate anything.

Does Slack CLI work with Slack Enterprise Grid?

Yes. The CLI supports org-level app deployments on Enterprise Grid. Authenticate with `slack login` using Enterprise Grid credentials and deploy apps across your organization. Admin approval workflows still apply as configured by your org admins.

Slack CLI

136 stars

official open-source Has MCP macOS Cross-platform Windows Actively maintained

Slack's official CLI for creating, developing, and deploying Slack apps from the command line. Supports Bolt and Deno frameworks.

Slack CLI has both a CLI and an MCP server. See when to use each

Part of the Slack CLI tools for AI agents

What your agent can do

Enterprise Slack orgs accumulate hundreds of channels. When a team reorganizes: create new channels, archive old ones, move members, update topics, set permissions, configure integrations. The web UI does one channel at a time. For a 50-channel reorganization, that's hours of clicking. Your agent handles bulk operations through the Admin API: `admin.conversations.bulkArchive`, `admin.conversations.bulkMove`, and SCIM provisioning for the entire user lifecycle.Your agent builds Slack apps from scratch. `slack create` scaffolds a project. `slack run` starts it locally with hot reload and connects to your workspace through socket mode. Test message handlers, slash commands, and interactive modals without deploying. Changes appear instantly. `slack deploy` pushes to Slack's managed infrastructure in one command. No servers to provision, no containers to configure.For teams building on Slack's next-generation platform (Deno runtime), the CLI is the only supported development path. It handles function definitions, workflow composition, trigger management, and datastore operations. Bolt framework users (Node.js, Python, Java) get first-class support with scaffolding and manifest management.The hybrid pattern most teams miss: Slack's Workflow Builder (1M+ users) handles simple no-code automations, but can trigger custom functions built with the CLI. A non-engineer sets up the trigger ("when someone posts in #bugs"). Your agent builds the TypeScript function that handles the complex logic (create a Jira ticket, assign based on labels, post confirmation). The CLI builds it, Workflow Builder runs it.Canva's finance team reported saving 64 hours per week by replacing async standup collection with automated Slack workflows. Your agent can build, deploy, and iterate on these automations without touching the Slack admin dashboard.

Limitations

This is an app development tool, not a workspace interaction tool. For agent-friendly message reading and sending, use community alternatives like slkcli or slack-agent-cli. `slack deploy` uses Slack's managed infrastructure, so teams with VPC/compliance hosting requirements lose the one-command deployment. Workspace administration (user provisioning, analytics) requires the Admin API directly.

Key Commands

slack create Create a new Slack app from a template (Bolt or Deno)

slack run Start the app in local development mode with hot reload

slack deploy Deploy the app to Slack's managed infrastructure

slack login Authenticate with your Slack workspace

slack trigger create Create a trigger to start a workflow (link, event, webhook, or schedule)

slack app list List all workspaces where the app is installed

slack activity Display app activity logs from the Slack Platform

GitHub Stats

repo slackapi/slack-cli

stars 136

language Go

license Apache-2.0

last commit Mar 13, 2026

Links

Official documentation docs.slack.dev/tools/slack-cli/ GitHub repository github.com/slackapi/slack-cli CLI command reference docs.slack.dev/tools/slack-cli/reference/commands/slack/ Release notes github.com/slackapi/slack-cli/releases Slack MCP server docs.slack.dev/ai/slack-mcp-server/

Alternatives

tool	description
Slack CLI	current tool
slkcli	Lightweight Slack CLI for macOS focused on agent-friendly message reading and sending. Not for app development.
slack-agent-cli	Third-party Go CLI for Slack designed for non-human (agent) usage. Focused on workspace interaction, not app development.
shaharia-lab/slackcli	Community Slack CLI with structured output formats (JSON, table, text) designed for AI tool integration and automation.

FAQ

Is Slack CLI free?: Yes. The Slack CLI is free and open-source under the Apache 2.0 license. Develop and deploy apps at no CLI cost. Slack's managed hosting (`slack deploy`) has usage limits tied to your workspace plan. Self-hosted Bolt apps have no Slack-imposed limits.
What is the difference between Bolt and Deno Slack apps?: Bolt is Slack's framework for Node.js, Python, or Java. You host the app yourself. Deno apps run on Slack's managed platform with built-in hosting, datastores, and workflows. The CLI supports both. Bolt apps use manifest.json. Deno apps define manifests in TypeScript. Your agent can scaffold and deploy either type.
Can I use Slack CLI with an existing Slack app?: Yes. Run `slack app link` to connect the CLI to an existing app. Your agent can then manage the manifest, deploy updates, and use local development mode with apps originally created through the web UI. No need to recreate anything.
Does Slack CLI work with Slack Enterprise Grid?: Yes. The CLI supports org-level app deployments on Enterprise Grid. Authenticate with `slack login` using Enterprise Grid credentials and deploy apps across your organization. Admin approval workflows still apply as configured by your org admins.