01
Create your Faction organization
Sign up free and create an organization. This is where admins connect tools once, so teammates never wire up their own integrations.
DM @Faction in Slack or search channel history from any connected AI app. Same workspace tools in channels, threads, and chat.
Slack
Your team already lives in Slack. Admins install the @Faction bot once so linked teammates can DM it or @mention it for the same MCP-backed answers they get in the web app. Connect Slack to a workspace and chat can search messages, read threads, and draft replies through Slack's official MCP server.
Set up Slack a single time instead of asking everyone to paste their own keys into Claude.
Give marketing and other teams the Slack tools they need without one shared bundle for the whole company.
Each workspace URL exposes only the Slack actions admins turn on, not every connector in your org.
Use the same workspace URL in Claude, Cursor, ChatGPT, or any MCP client your team prefers.
Step by step
Six steps from a fresh organization to chatting with Slack inside Claude.
01
Sign up free and create an organization. This is where admins connect tools once, so teammates never wire up their own integrations.
02
Open the integration catalog in Faction and connect Slack with OAuth. Pick a shared org connection or let each teammate sign in with their own account.
03
Create a workspace for the team that needs it, such as marketing, and add Slack. Admins choose exactly which tools are on for that workspace.
04
Every workspace exposes one MCP URL with only the tools you enabled. Copy it from the workspace settings in Faction.
05
In Claude, go to Settings, then Connectors and add your Faction workspace URL.
06
Ask Claude to use Slack in plain language. Faction handles auth and scopes behind one URL.
Your workspace URL
Faction gives your team a shared AI workspace that plugs into the tools you already use. Each workspace gets one link (an MCP URL) that includes only the tools your admins turn on. Paste it into Claude once and everyone is connected. No keys to copy, nothing to set up per person.
https://yourcompany.runfaction.com/mcp/your-workspaceWhat the MCP server can do
DM the bot or @mention it in any channel. Same workspace tools, permissions, and thread memory as in-app chat. Replies stay in the thread.
Faction uses Slack's first-party MCP server so search, read, and send tools stay current with what Slack ships.
Find discussions by keyword, channel, or date across the workspaces you connected.
Pull thread context or Canvas content to answer what was decided, by whom, and where the doc lives.
Post updates or draft replies in Slack when admins enable write tools for the workspace.
Slack users match Faction members by email. Channel Q&A only works for linked teammates, scoped to what they can already read.
Use cases
Ask @faction in #launch for a recap before a go/no-go, or search the channel from Faction chat during prep.
Find prior Slack threads about an account before joining a customer call, without scrolling for an hour.
@mention Faction in #marketing for HubSpot pipeline context alongside what the channel decided this week.
FAQs
No. An admin connects Slack once at the org level. Teammates just add the workspace URL to Claude and start chatting.
OAuth sign-in. Each member typically connects their own Slack account for least-privilege access.
Yes. Claude supports remote MCP connectors, so you can point it at any Faction workspace URL and use the tools that workspace allows.
Yes. Each workspace exposes only the tools admins turn on, so the URL you share never grants more than intended.
For the MCP connector, yes in most setups. Each member connects their own Slack account so chat only sees channels they can already read. The @Faction bot links Slack users to Faction members by email after the org install.
Create an organization, connect Slack, and bundle it into a workspace your team can use from Claude.
Start free