Help verify SandBase CLI installation in Cline

[denial123789]

Goal

Verify whether a clean Cline installation can configure and use the SandBase CLI v0.1.17 local MCP server using only the repository's README.md and/or llms-install.md.

This evidence is required before SandBase can truthfully request inclusion in Cline's official MCP Marketplace.

Test source

Use the immutable GitHub Release artifact, not npm latest (which is still v0.1.14):

npx -y https://github.com/sandbaseai/cli/releases/download/v0.1.17/sandbaseai-cli-0.1.17.tgz catalog --json

Release: https://github.com/sandbaseai/cli/releases/tag/v0.1.17

Acceptance criteria

• Start from a clean or newly created Cline MCP configuration.
• Give Cline only README.md and/or llms-install.md as setup guidance.
• Record the exact Cline version and operating system.
• Confirm Cline can start the stdio MCP server and enumerate all six tools.
• Complete browser OAuth without placing credentials in an Issue, terminal transcript, screenshot, URL, or CLI argument.
• Successfully run a non-destructive discovery or account-status call.
• Document the resulting configuration shape with all secrets redacted.
• Remove or disable the configuration and confirm rollback/cleanup succeeds.
• Report any manual intervention Cline required beyond the two documentation files.

Expected MCP tools:

• sandbase_discover
• sandbase_inspect
• sandbase_run
• sandbase_run_get
• sandbase_runs
• sandbase_account

Safety

Do not post tokens, OAuth codes, account balances, private prompts, or provider responses. A redacted configuration and concise command/result summary are sufficient.

If the test passes reproducibly, we can add Cline to the verified client catalog and submit the server to the official Cline Marketplace with an evidence-backed installation claim.

Coordination

Questions about other client targets and requests for the next verified integration belong in Which AI client should SandBase CLI support next?. This issue remains focused on reproducible Cline evidence.