Onboarding Guide
This guide walks you through every step: accepting your team invitation, generating a personal API token, and connecting Claude.ai or ChatGPT to your team's shared brain via the MCP protocol. By the end your AI assistant will have live read/write access to your team's memory.
You need a team admin to invite you first. If you are creating a new team from scratch, follow the Teams & Projects guide, then come back here.
Step 1 — Get invited (or auto-join via your GitHub org)
Two ways onto a team
Either your team admin invites your GitHub username or
your email directly, or your team has its
github_org set to a GitHub org you belong to — in which
case the first time you sign in, GrooveOS auto-adds you. See
Authentication for the full org-auto-join
rules.
If you got an email invite, you can either click the link inside, or just go straight to grooveos.app/account/teams/ and sign in.
No email and your org isn't wired up to auto-join? Ask your admin to enter your GitHub username on the team's members card — they don't need your email at all.
Step 2 — Sign in with GitHub
Authenticate via the xbrain GitHub App
GrooveOS signs you in with GitHub — no passwords to manage. Click Sign in with GitHub and authorize the xbrain App. It asks for two read-only permissions: your email addresses (for notifications and admin invites) and your org memberships (for the auto-join rule). Nothing else.
If your GitHub org hasn't installed xbrain yet, GrooveOS shows an "Install xbrain on your-org" banner. An org owner clicks it once; afterwards every member of the org can sign in. See Installing on your org for the consent screen flow.
Step 3 — Verify your team membership
Confirm you see your team in the dashboard
After signing in you land on the dashboard. In the top-right corner you
should see your team name (e.g. acme-corp). This is your
team_scope — the namespace that isolates all your team's data.
If you see "No team" or a different team, contact your admin. They may
need to add your GitHub username to the team, or set
github_org on the team to match one of your orgs.
Step 4 — Generate a personal API token
Create an xbt_ token scoped to your team
Go to Settings → API Tokens in the dashboard and click
New token. Give it a descriptive name like
claude-mcp or chatgpt-actions.
The token is shown once — copy it immediately and store it in a password manager or secure note. It looks like:
xbt_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2
This token is automatically scoped to your team_scope.
Any request made with it can only read or write data belonging to your team —
cross-team access is impossible by design.
Never share your token or commit it to source control. If a token is compromised, revoke it immediately from Settings → API Tokens and generate a new one.
Step 5 — Connect Claude.ai via MCP
Add GrooveOS as a remote MCP server in Claude.ai
In Claude.ai, open Settings → Integrations → MCP Servers and click Add server. Fill in:
Name: GrooveOS Brain
URL: https://mcp.grooveos.app/mcp
Auth: Bearer → paste your xbt_ token
Save the integration. You should see a green "Connected" badge within a few seconds. Claude.ai will now list the available tools in the tool panel.
Available tools
memory_search— semantic search across team memorymemory_add— store a new memory itemtasks_list— list open tasks for the teamtask_create— create a new tasktask_update— update task status or assigneecontacts_search— find contacts by name or emailcontact_add— add a new contactagent_invoke— run a GrooveOS agent by nameteam_context— fetch recent team context (memories + tasks)
Try asking Claude: "What are our open tasks?" or "Search memory for our Q3 strategy." It will call the right tool automatically.
Step 6 — Connect ChatGPT via Actions (optional)
Import the OpenAPI schema into a custom GPT
In ChatGPT, create or edit a Custom GPT and open the Actions tab. Click Import from URL and paste:
https://mcp.grooveos.app/openapi.json
ChatGPT will fetch the schema and populate the action list automatically.
Under Authentication, choose API Key →
Bearer, and paste your xbt_ token.
Save the GPT. The same 9 tools are available — your custom GPT can now read and write your team's shared brain.
ChatGPT Actions use the REST/HTTP transport, not the MCP streaming protocol. The tools are identical but the connection mechanism differs. Both paths write to the same underlying memory layer.
Step 7 — Test the connection
Run a quick end-to-end test
Ask your AI assistant (Claude or ChatGPT) to store a test memory:
Please add this to team memory:
"Onboarding test completed by [your name] on [today's date]."
The assistant should call memory_add and confirm the item was
stored. Next, verify the round-trip by searching for it:
Search memory for "onboarding test"
If you get the item back, your integration is working end-to-end. You can
now delete the test item with memory_search to find its ID, then
remove it from the dashboard under Memory.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Claude shows "MCP server error" or red badge | Wrong URL or token | Double-check URL is https://mcp.grooveos.app/mcp (no trailing slash). Verify the token starts with xbt_. |
| 401 Unauthorized from the MCP server | Token revoked or expired | Generate a new token from Settings → API Tokens and update it in Claude/ChatGPT settings. |
| Tools appear but return empty results | No data in team memory yet | Add a test memory item (Step 7) to confirm the write path works. Empty results on a fresh team are expected. |
| 403 Forbidden on team_context | Token scoped to wrong team | Verify your team_scope in the dashboard matches the one the token was created for. |
| ChatGPT schema import fails | Firewall or network issue | Try importing manually: download /openapi.json and paste the JSON directly into the Actions editor. |