What problem does it solve? Setting up an MCP server involves client-specific configuration formats, API token handling, toolset selection, and verification steps that are easy to get wrong. This Skill guides an agent through connecting Claude Code, Claude Desktop, Cursor, or VS Code to the hosted Capawesome MCP server so documentation search and Capawesome Cloud management tools work correctly on the first attempt. ## Core Features & Use Cases - Client auto-detection and setup: Detects the MCP client from project files (.mcp.json, .cursor/, .vscode/) and applies the correct configuration for Claude Code, Claude Desktop, Cursor, or VS Code. - Toolset and read-only configuration: Builds the server URL with the right toolsets query parameter (docs, cloud, all, or named subsets) and optional readonly mode for shared or CI setups. - Secure token handling: Guides API token creation in the Capawesome Cloud Console and keeps tokens out of Git-tracked files using user-scoped config, environment variables, or VS Code input prompts. - Verification and troubleshooting: Verifies the connection with search_docs and cloud_get_current_user, and resolves common errors like 401 Unauthorized, missing cloud tools, and unquoted URLs. - Use Case: A developer wants their AI assistant to search current Capawesome plugin documentation and trigger cloud builds. The agent detects they use Cursor, writes the mcp.json entry with toolsets=all, and verifies the connection. ## Quick Start Connect my MCP client to the hosted Capawesome MCP server with documentation search and Cloud tools enabled.
