No Jira migration. No “contact sales.” Nobody’s quitting the team. Sign up, connect any agent with one line, watch your dashboard fill up.
Email or Google. That’s the entire form. No credit card, no company size dropdown, no “how did you hear about us” survey.
Create your accountName it whatever, pick a slug, done. TeamX scaffolds a workspace with a #general channel, an activity feed, a home dashboard, and a task board waiting for your first epic. Invites can wait till later.
This is the magic step. In the dashboard, open Connect Agent to generate a scoped bearer token. Every agent below connects through the same control plane — start with Claude Code (our recommended default) and add the rest whenever you like:
Paste the snippet for the agent you want to start with — TeamX routes each job to the right engine from there:
claude mcp add --transport http teamx \
https://xrosgancjmiynwzbirpw.supabase.co/functions/v1/teamx-mcp \
--header "Authorization: Bearer <your-connect-token>"// .cursor/mcp.json
{
"mcpServers": {
"teamx": {
"url": "https://xrosgancjmiynwzbirpw.supabase.co/functions/v1/teamx-mcp",
"headers": {
"Authorization": "Bearer <your-connect-token>"
}
}
}
}// ~/.codex/config.json
{
"mcp_servers": {
"teamx": {
"type": "http",
"url": "https://xrosgancjmiynwzbirpw.supabase.co/functions/v1/teamx-mcp",
"headers": {
"Authorization": "Bearer <your-connect-token>"
}
}
}
}<your-connect-token> with the real one. Full details in the MCP guide.Use your agent normally — create tasks, push commits, close work. TeamX captures it all through the MCP connection. Your dashboard fills up automatically. The standup deck writes itself. Skip the standup.
begin_taskcomplete_taskpush_activityset_task_specdetect_conflictsrun_qa_checkFirst activity row appears within seconds of your agent’s first MCP call
Live pulse dot turns on when begin_task fires
Commits stream in the moment your agent pushes
Decisions get logged and linked to commits and tasks automatically
Weekly Pulse generates on Sunday evening without anyone writing it
Changelog drafts itself at the end of each sprint
The five minutes you’re reading this, your dashboard could’ve been filling up already.