GroupMixer

Create groups and rotations

Organize people into groups across rounds for workshops, classrooms, conferences, and networking events. Create or update a scenario in chat and generate rotations on your device.

What you can ask

Help me organize people into groups across several rounds.
Example path

MCP connector

Server URL: https://groupmixer.app/api/mcp
Login: None
Protocol: MCP 2026-07-28
Instructions: GroupMixer optimizes explicit groups across rounds, not workforce shifts. Interactive computation runs only in the open browser workspace. A prepared request is not a solved schedule. Use for all scenario creation and edits; prefer its browser equivalent when available. Read the workspace context for applied revisions and actual results. The server and its app-shell resource cannot read saved browser work. If the context attachment is unavailable to the model, ask the user to open Copy workspace context in the scenario menu and paste it into this chat. Use a fresh copy to read completed operation receipts. Never guess workspace identifiers or revisions. Preserve all user constraints. Updates require the latest workspace ID and revision. Reuse request_id only for identical retries. Use for externally constructed schedules and for the self-contained Python scorer. Both execute in the shared browser; awaiting-browser never means saved or exported. Present the returned operation_url as an Open in GroupMixer link when the host does not deliver a schedule request automatically. Wait for the browser receipt before reporting completion.

Tools

Reads data3

Changes data1

Deletes or can't be undone1

Skills

None in the store listings or on the server

MCP connector

Server URL

https://groupmixer.app/api/mcp

None

Protocol

MCP 2026-07-28

Instructions

GroupMixer optimizes explicit groups across rounds, not workforce shifts. Interactive computation runs only in the open browser workspace. A prepared request is not a solved schedule. Use for all scenario creation and edits; prefer its browser equivalent when available. Read the workspace context for applied revisions and actual results. The server and its app-shell resource cannot read saved browser work. If the context attachment is unavailable to the model, ask the user to open Copy workspace context in the scenario menu and paste it into this chat. Use a fresh copy to read completed operation receipts. Never guess workspace identifiers or revisions. Preserve all user constraints. Updates require the latest workspace ID and revision. Reuse request_id only for identical retries. Use for externally constructed schedules and for the self-contained Python scorer. Both execute in the shared browser; awaiting-browser never means saved or exported. Present the returned operation_url as an Open in GroupMixer link when the host does not deliver a schedule request automatically. Wait for the browser receipt before reporting completion.