From bito-ai-architect
Guide the user through configuring BitoAIArchitect MCP credentials
How this skill is triggered — by the user, by Claude, or both
Slash command
/bito-ai-architect:setup-bitoThe 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.
Help the user configure their BitoAIArchitect MCP server credentials.
Ask for credentials — You need three values from the user:
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:
/mcp to check the BitoAIArchitect server appearslistRepositoriesnpx claudepluginhub agdas/bito-plugins-marketplace --plugin bito-ai-architectGenerates .mcp.json and .claude/settings.json to configure MCP servers, tokens, and tool permissions for agent-flow pipeline. Supports CLI flags for tracker type, instance URL, and source control remote.
Handles Claude Code MCP integration: installs/manages servers (HTTP/SSE/stdio), scopes, enterprise configs, OAuth auth, resources/@mentions, prompts, limits, security; delegates to docs-management.
Manages Model Context Protocol (MCP) servers for Claude Code projects: installs/configures .mcp.json, OAuth remotes, runtime enable/disable, troubleshooting connections.