{"id":"microck-opencode-studio","name":"opencode-studio","af_score":24.0,"security_score":31.2,"reliability_score":23.8,"what_it_does":"opencode-studio is a local web GUI plus an Express-based backend for managing local OpenCode configuration on disk. It supports managing MCP servers (enable/disable, add via npx), profiles (isolated config sets), editing skills and JS/TS plugins (including bulk import from URLs), managing custom slash commands, viewing usage/token cost dashboards from local logs, and handling authentication/credential profiles, with optional GitHub sync and backup/restore.","best_when":"You want a self-hosted, local, file-backed configuration UI for OpenCode (including MCP and plugin/skill management) running on a developer machine.","avoid_when":"You cannot trust the machine/browser runtime (it writes directly to local config directories) or you need a well-documented network API for third-party automated clients.","last_evaluated":"2026-03-30T13:38:46.455291+00:00","has_mcp":true,"has_api":false,"auth_methods":["Login/logout per provider via UI (exact provider mechanisms not specified in README)","Save/switch between credential profiles"],"has_free_tier":false,"known_gotchas":["Writes directly to local disk locations (opencode config and studio data directories), so repeated automated calls may overwrite/duplicate content unless the agent manages idempotency.","Deep links can trigger installs/imports; agent-controlled URL opening could execute commands or fetch remote resources, so treat these actions as potentially side-effectful.","No machine-readable API contract (OpenAPI) is provided in the README, so agent integration via HTTP endpoints is not clearly defined."],"error_quality":0.0}