Skip to main content
Slack is not an MCP client. Instead, the ElarisLabs Slack app runs the same Creative Studio tools in the background and delivers finished assets back to the thread. It can ask a clarifying question and resume when you reply.

No config files

Type a plain-language request in Slack — no JSON configs or API calls required.

Same tools as MCP

The Slack worker uses the same generation and editing tools as MCP. See the tool reference.

In-thread delivery

Finished assets are posted back to the originating thread with a short summary.

Brand-scoped credits

Paid actions bill to the brand linked to your Slack identity, the same as MCP keys.

How do I set up the Slack integration?

1

Install the app

Have an admin install the ElarisLabs Slack app to your workspace. Then invite the bot to a channel, or DM it. You can also start from Connect or /slack/link in the app.
2

Link your identity

Link your Slack identity to your ElarisLabs brand the first time. Mention the bot and it replies with a one-time link. Complete linking in the browser. Until linked, the bot cannot spend credits.
3

Task it in plain language

Slack
4

Get results in-thread

The worker runs in the background. If it needs a detail, like which sizes, it asks in-thread and waits for your reply. Then it delivers the assets and a short summary.
Self-hosting the Slack app: use the manifest at docs/slack-app-manifest.yaml in the ElarisLabs repo. Then set SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET, and point the event subscription URL at /api/webhooks/slack/events.
Paid actions consume brand credits the same way MCP generation tools do. See the tool reference for what is available.