Connect your tools once, use them with every coding agent
Each coding agent has its own way of connecting to tools, so teams end up setting up GitHub, Slack and the rest again for every agent and every person. In Friday a workspace admin connects a tool once, and you choose which agents may use it.
What is Friday Work?
Friday Work is a multiplayer AI workspace for coding teams. Your people and your coding agents work in one live session: the same task, the same record, the same tools. It is a desktop app for Windows and Mac.
- Teammates join a session by link, watch every step, suggest changes and take control when it is their turn.
- Claude Code, Codex and Cursor run on your own machine and your own accounts, side by side in one session, with Friday’s own agent when you want it.
- Continue a Claude Code or Codex session you already have, instead of starting over.
- Plan, Manual or Auto: you decide what an agent may do, and approve its commands as a team.
- Connect GitHub, Slack, Linear and 50+ more tools over MCP once, and choose which agents may use them.
- Free to start. Pro is $20 a month ($18 a month billed yearly).
What goes wrong when every agent has its own setup?
- The same tool is configured separately in Claude Code, Codex and Cursor.
- Each teammate sets it up again on their own machine.
- Nobody knows which agent can reach which tool, or who approved it.
How does it work in Friday?
MCP, the Model Context Protocol, is the open standard for connecting agents to tools and data. Friday has a catalog of more than 50 connections, including Google Workspace, Slack, GitHub, Linear, Notion and Stripe.
- A workspace admin adds a connection once.
- Its tools are offered to sessions in the workspace.
- You limit each agent to all connections, none, or a chosen few. A session can switch connections off.
- Every tool call shows up in the session feed, so the team sees what an agent used and when.
How should a team decide what to connect?
Connect only what the work needs. An agent can use a connected tool within the permissions you approved, including tools that change data, so start with read access and add more when a task needs it. Keep the connection list short and review it when the team changes.
Common questions
Do all agents in a session use the same connections?
Connections belong to the workspace, and each agent has its own allowed list, so you can give one agent GitHub and another none.
Are MCP connections extra on a paid plan?
No. They are included on Free, Pro and Max.
Can I see what an agent did with a tool?
Yes. Tool calls appear in the shared session feed.