Skip to content

Add SandBase CLI: MCP onboarding and 2,000+ model catalog #8

Description

@denial123789

Tool

SandBase CLI is an agent-first CLI and local stdio MCP bridge. It configures 25 AI client targets—including Codex, Claude Code, Cursor, Gemini CLI, Windsurf, OpenCode, Kiro, Warp, Amp, Hermes, and OpenClaw—then exposes discovery, schema inspection, execution, run history, and account tools for a catalog of 2,000+ AI models and APIs.

The read-only compatibility catalog can be inspected without authentication or configuration changes:

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

Suggested card

name: sandbase
binary: sandbase
aliases: []
category:
- mcp
- agent
- network
lang:
- all
platform:
- local
summary: Connect coding agents to a 2,000+ AI model and API catalog through a local MCP bridge.
homepage: https://github.com/sandbaseai/cli
docs: https://github.com/sandbaseai/cli#readme
detect:
  version_args:
  - --version
  local:
    files: []
    dirs:
    - .sandbase
    package_json:
      package_manager_prefixes:
      - "@sandbaseai/cli"
use_when:
- Configure a supported coding agent to use SandBase through MCP
- Discover model and API schemas before making a structured request
avoid_when:
- Client configuration ownership is unclear or existing entries have not been reviewed
- Model pricing, remote side effects, or data handling have not been inspected
risk:
  level: high
  effects:
  - network_access
  - read_files
  - write_files
  - remote_read
  - remote_write
  - secret_exposure
  requires_auth: true
  destructive: false
  confirmation_required_for:
  - authorizing an account and modifying client MCP configuration
  - running paid models or APIs with external side effects
guardrails:
- Run `sandbase catalog --json` before connecting to confirm client support without mutation.
- Use `sandbase_inspect` to review schemas and pricing before `sandbase_run`.
- Keep the credential store private and run `sandbase doctor` after configuration changes.

The project validates ownership before changing client configuration and removes only SandBase-managed state during rollback or unregister.

Disclosure: I am submitting this on behalf of the SandBase project, with AI assistance. The metadata above was checked against the public repository and v0.1.17 release.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions