Repository navigation
Help verify SandBase CLI installation in Cline #23
Description
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 --jsonRelease: 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.mdand/orllms-install.mdas 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_discoversandbase_inspectsandbase_runsandbase_run_getsandbase_runssandbase_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.
Activity
liyangbing commentedon Aug 23, 2026
Current evidence: Cline is not in the CLI v0.1.17 catalog, so
sandbase connect --client clineis intentionally not a supported path. The CLI can only manage the client IDs in the immutable catalog (sandbase catalog --json); do not reuse another client identity or credential as a workaround.\n\nCline documents MCP configuration under~/.cline/data/settings/cline_mcp_settings.jsonfor shared settings and.cline/mcp.jsonfor project settings: https://docs.cline.bot/getting-started/config and https://docs.cline.bot/cli/cli-reference\n\nI would treat a manual Cline adapter as a separate feature request until we can test its actual stdio config, credential ownership, doctor output, and unregister behavior. For now, the supported setup remains the catalog output plussandbase doctorfor a listed client.