Set up a workspace with your agent

Hand workspace setup to Claude Code or another MCP agent: what it does, in what order, and what stays with you.

Workspace administrators and the agents they run

Read as Markdown All guides as text Agent documentation index

Have your agent do thisPaste the prompt into Claude Code, Cursor or another agent. It follows this guide over MCP and asks before it changes anything others will see.Show the prompt

Help me with "Set up a workspace with your agent" in my Shuffl workspace.

1. Read the guide: https://shuffl-rebuild.vercel.app/docs/markdown/agent-setup
2. Add Shuffl's MCP server: https://shuffl-rebuild.vercel.app/api/mcp
   Claude Code: claude mcp add --transport http shuffl https://shuffl-rebuild.vercel.app/api/mcp
   When the browser opens, choose my workspace and allow the access the guide needs.
3. Work through the steps in order: What you do; Work through setup. Do what you can over MCP and tell me which steps only I can do in the browser or in Slack.

Show me what you will change and who it affects, and wait for my yes before publishing, inviting or sending anything.

App links open your signed-in workspace. Check the selected workspace before making changes.

What you do

Create your account and name your company. Shuffl creates its first workspace with it.
In Workspace setup, under the steps, choose Show prompt, then Copy prompt, and paste it into your agent.
When your browser opens, pick the workspace, choose Choose what setup needs, and allow access.
Answer your agent when it asks: approve Slack, and say yes before it publishes knowledge or invites anyone.

Connect the agent

The agent connects to Shuffl’s MCP server and signs in with OAuth in your browser, so no API key is needed. It works as you, with your role, in the one workspace you choose. The connection lasts 30 days unless you revoke it in Settings → API keys.

claude mcp add --transport http shuffl https://shuffl-rebuild.vercel.app/api/mcp

Connect another MCP client

Work through setup

slack: you can’t install Slack. Send the person to Workspace setup → Connect Slack and wait. A Slack admin may need to approve it.
knowledge: ask for the handbook or policy as a file or a web page. For a file, call knowledge_uploads_create, send it in parts with knowledge_uploads_appendPart (base64), then knowledge_uploads_complete, and poll knowledge_uploads_get until it is read. For a web page, call knowledge_sources_importWebsite. Each section becomes a private draft. Show the person the draft titles and the audience (everyone in the workspace), and publish with knowledge_sources_publish only after they say yes.
preview: call assistant_send with a question the published source answers, and check the answer cites it. The step counts your own cited answer.
employees: ask for one coworker’s email and, after a yes, call invitations_create. They accept by email, then the person turns on their access in People.
Optional, each after a yes: pulse_saveProgram turns on Pulse; channels_list, programs_options and programs_create start coffee chats; onboarding_saveProgram welcomes new hires; celebrations_preview then celebrations_save turns on birthdays and anniversaries.
If another Slack app already runs intros, shoutouts or celebrations, teams_slackChannels lists those channels with a guess for each, plus public channels named for praise (fromApp false; only praise or leave it apply). Show the list, then call teams_moveSlackChannels with the person’s choices. Programs it creates start paused.

Instructions for the agent. Call teams_setup first and again after each step. Its steps list is the checklist: steps with required true count toward progress, and the rest are optional programs. Access and HR steps appear only when something needs fixing; tell the person what the step says. Never publish, invite, send or turn on a program without the person’s yes in this conversation.

Actions setup uses

Choose what setup needs on the consent screen selects these actions. Each tool is the permission with dots replaced by underscores, such as knowledge_sources_publish. Granting HR responders, deleting the workspace and transferring ownership stay in the app.

assistant.send
Write · Ask Mello a question in a conversation
Exact grant required. Underlying role scope: assistant:write.
celebrations.preview
Read · Preview a celebration message
Exact grant required. Underlying role scope: celebrations:read.
celebrations.program
Read · Read the Celebrations settings
Exact grant required. Underlying role scope: celebrations:read.
celebrations.save
Write · Save celebration settings; enabling them schedules messages
Exact grant required. Underlying role scope: celebrations:write.
channels.list
Read · List available Slack channels
Exact grant required. Underlying role scope: programs:read.
invitations.list
Read · List pending workspace invitations
Exact grant required. Underlying role scope: access:read.
invitations.create
Write · Invite this person with the selected team role
Exact grant required. Underlying role scope: access:write.
knowledge.sources.get
Read · Read a Knowledge source
Exact grant required. Underlying role scope: knowledge:manage.
knowledge.sources.list
Read · List Knowledge sources
Exact grant required. Underlying role scope: knowledge:manage.
knowledge.sources.importWebsite
Write · Import a website page into Knowledge for review
Exact grant required. Underlying role scope: knowledge:write.
knowledge.sources.publish
Write · Publish this knowledge version to its audience
Exact grant required. Underlying role scope: knowledge:write.
knowledge.sources.write
Write · Write a Knowledge page with Mello from its title and a request; nothing is saved
Exact grant required. Underlying role scope: knowledge:write.
knowledge.uploads.get
Read · Read the progress of a Knowledge file upload
Exact grant required. Underlying role scope: knowledge:write.
knowledge.uploads.appendPart
Write · Upload the next part of a Knowledge file
Exact grant required. Underlying role scope: knowledge:write.
knowledge.uploads.complete
Write · Finish a Knowledge file upload and start reading it
Exact grant required. Underlying role scope: knowledge:write.
knowledge.uploads.create
Write · Start uploading a file to Knowledge
Exact grant required. Underlying role scope: knowledge:write.
onboarding.program
Read · Read the Onboarding program settings
Exact grant required. Underlying role scope: onboarding:read.
onboarding.saveProgram
Write · Save the onboarding program and its messages
Exact grant required. Underlying role scope: onboarding:write.
programs.options
Read · List program setting choices
Exact grant required. Underlying role scope: programs:read.
programs.create
Write · Create a program
Exact grant required. Underlying role scope: programs:write.
pulse.program
Read · Read the Pulse settings
Exact grant required. Underlying role scope: pulse:read.
pulse.saveProgram
Write · Save Pulse settings; enabling Pulse schedules questions to everyone
Exact grant required. Underlying role scope: pulse:write.
teams.setup
Read · Read the workspace's setup checklist
Exact grant required. Underlying role scope: team:read.
teams.slackChannels
Read · List community channels in the connected Slack and what each would become
Exact grant required. Underlying role scope: integrations:read.
teams.moveSlackChannels
Write · Set up each channel in Shuffl: paused intros, praise and celebrations
Exact grant required. Underlying role scope: integrations:write.
teams.saveAgentSetup
Write · Choose the built-in assistant or an external agent for the workspace
Exact grant required. Underlying role scope: team:write.

Endpoint permission reference