Get the FREE Ultimate OpenClaw Setup Guide →

opencode-ultimate-starter

The Ultimate OpenCode Starter Kit. Includes Oh My OpenCode config, Superpowers installation fix, MCP Setup, and Windows Crash Fix (exit_code: -1073740791). Panduan lengkap Bahasa Indonesia & English.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio bruhismyname-opencode-ultimate-starter node path/to/server.js \
  --env SUPABASE_TOKEN="Your Supabase token for MCP God-Mode tools" \
  --env OPENCODE_CONFIG_DIR="Path to OpenCode config directory (default: .config/opencode)"

How to use

This MCP server kit provides a pre-configured environment for OpenCode workflows with MCP support. It bundles front-end and back-end tooling to enable Shadcn component usage, a Supabase-backed data layer for migrations and data queries, and a web-enabled search capability to browse real-time docs. The included AGENTS.md and Planner/Sisyphus strategies automate project governance tasks such as maintaining a master todos.md, updating CHANGELOG.md, and enforcing consistent git commit standards. To start using the tools, run the server via the MCP entry point and follow the MCP_SETUP guide to connect your Supabase token. Once running, you can enable the Shadcn UI scaffolding, query your Postgres-backed data, and perform web searches for up-to-date documentation directly from the planner.

How to install

Prerequisites:

  • Node.js and npm/yarn installed on your system
  • Git installed
  • Optional: a Supabase project for MCP tools

Installation steps:

  1. Clone the repository git clone https://github.com/your-organization/opencode-ultimate-starter.git cd opencode-ultimate-starter

  2. Install dependencies npm install

    or

    yarn install

  3. Configure environment (example)

    • Create a .env file or set env vars as needed
    • SUPABASE_TOKEN=your-supabase-token
    • OPENCODE_CONFIG_DIR=path/to/.config/opencode
  4. Run the MCP server npm run start

    or if using a direct node entry

    node path/to/server.js

  5. Verify setup

    • Access the local server UI/tools
    • Follow guides under guides/MCP_SETUP.md and configs/ to finalize Tool integrations
  6. Optional: apply configs

    • Copy configs/ contents to your local .config/opencode folder as described in Quick Start

Additional notes

Tips and common issues:

  • Ensure your Supabase token has the proper permissions for MCP operations; missing tokens commonly cause MCP_SETUP failures.
  • If you encounter crashes on Windows, review guides in guides/FIX_CRASH_AND_BUGS.md.
  • The AGENTS.md automation helps keep planning docs up to date; customize as needed for your project rules.
  • When switching between configurations (e.g., oh-my-opencode.json vs opencode.json), back up your existing .config/opencode folder first.
  • This kit emphasizes token-saving strategies; use Planner-Sisyphus mode to reduce token usage while maintaining code quality.
  • The web search tool relies on an active internet connection and proper integration per MCP_SETUP.md.

Related MCP Servers

Sponsor this space

Reach thousands of developers