Skill

setup-bito

Guide the user through configuring BitoAIArchitect MCP credentials

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/bito-ai-architect:setup-bito

User invocable

Model invocable

Inline context

Default effort

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Help the user configure their BitoAIArchitect MCP server credentials.

40 lines · ~401 tokens

Stats

Parent stars0

MaintenanceGood

Last CommitMar 9, 2026

Actions

Stats

Actions

Help the user configure their BitoAIArchitect MCP server credentials.

Ask for credentials — You need three values from the user:
- Workspace ID: Their Bito workspace identifier (found at https://app.bito.ai under workspace settings)
- Bearer Token: Their MCP authentication token (found in Bito workspace under API/MCP settings)
- Email: The email address associated with their Bito account
Validate the endpoint — Once you have all three values, test the connection by describing what a test call would look like:
```
URL: https://mcp.bito.ai/{WORKSPACE_ID}/mcp
Headers: Authorization: Bearer {TOKEN}, x-email-id: {EMAIL}
```

Set environment variables — Guide the user to add these to their shell profile (~/.zshrc, ~/.bashrc, or equivalent):

export BITO_WORKSPACE_ID="<their-workspace-id>"
export BITO_MCP_TOKEN="<their-token>"
export BITO_EMAIL="<their-email>"

Verify plugin activation — After setting env vars and restarting Claude Code:
- Run /mcp to check the BitoAIArchitect server appears
- Try a simple test: ask to list repositories using listRepositories

If the MCP server shows as disconnected, check that env vars are exported (not just set)
If auth fails, verify the token hasn't expired
If workspace ID is wrong, the URL will return a 404
Remind users to restart Claude Code after changing environment variables