apps-connect

# Connect Apps-mcp Set up the local Apps-mcp connection without exposing credentials. ## When to load this skill Read this skill before the first matching `apps_*` MCP call in each task. Once setup succeeds, switch to the skill for the user's next goal instead of treating this as an API-wide guide. ## Workflow 1. Confirm Node.js 20 or later and `npx` are available. 2. Direct the user to prepare the app ID and app secret in the Apps administration screen. 3. Run `npx -y theapps-mcp configure` in an interactive terminal. Enter credentials only in that prompt; never request or repeat them in chat, files, logs, or command arguments. 4. Register the MCP server for the selected client when prompted. 5. Tell the user to reload the MCP client if it does not detect the new server immediately. 6. Call `apps_auth_status` and report only whether credentials are configured. 7. If token errors persist, call `apps_clear_token_cache` and retry `apps_auth_status`. Use `apps_help` (`topic=setup|tools|skill`) when the next skill is unclear. ## Safety - Treat the app ID, app secret, and access token as secrets. - Do not print configuration files that contain credential values. - Keep writes disabled unless the user needs create, update, or delete operations. Writes require `APPS_MCP_ALLOW_WRITE=true`; do not ask the user to paste that value in chat. - Apps API connects to `https://api.theapps.jp`; it has no separate API sandbox. ## Result Report the configured client, whether Apps-mcp is detected, whether authentication is configured, and the exact unresolved setup step when connection fails.