OpenCode Setup

Overview

OpenCode is a free, open-source terminal coding agent that has been gaining ground fast. It speaks MCP natively — remote servers, OAuth discovery, dynamic client registration — so Tempreon connects with one config entry and zero credentials. Once connected, your AI in OpenCode loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns, across every tool you use.

OpenCode's standout feature is model freedom: it runs 75+ providers, including Claude, GPT, and Gemini alongside open models like GLM, Kimi, Qwen, and DeepSeek — via their own providers, OpenRouter, or local runtimes. Because MCP lives in the harness rather than the model, you can swap models mid-project and your Tempreon context stays exactly where it was. One Bridge covers all of them.

Quick path: add Tempreon to opencode.json → OpenCode discovers the OAuth endpoint and opens your browser → approve → done.

Prerequisites

• OpenCode installed, with at least one model provider configured
• A Tempreon account with at least one available Bridge slot
• A working default browser for the authorization step

Step-by-Step Setup

1. Add Tempreon to your config

OpenCode reads opencode.json in your project directory, or ~/.config/opencode/opencode.json for a global setup. Add an mcp block:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tempreon": {
      "type": "remote",
      "url": "https://api.tempreon.com/functions/v1/tempreon-mcp/mcp",
      "enabled": true
    }
  }
}

The URL is also shown in your Bridges dashboard. "type": "remote" is required — it tells OpenCode this is a hosted server, not a local subprocess.

2. Authorize the connection

Authentication is automatic: OpenCode discovers Tempreon's OAuth endpoint and registers itself via dynamic client registration. The first time it connects, your browser opens to the Tempreon consent screen — sign in if prompted and approve.

If you'd rather authenticate up front, run:

opencode mcp auth tempreon

3. Verify the connection

Two useful commands:

opencode mcp list
opencode mcp debug tempreon

list shows Tempreon's connection status; debug prints the details if something is off. Then start a session and ask "What Tempreon tools do you have access to?" — a list of tools means the Bridge is live.

Troubleshooting

Connection fails immediately. Check the URL ends in /mcp — no trailing slash. The full URL is https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Server ignored or treated as local. Confirm the entry has "type": "remote" and "enabled": true, and that the file is valid JSON.

Auth errors or expired tokens. Run opencode mcp auth tempreon to redo the OAuth flow. OpenCode stores tokens in ~/.local/share/opencode/mcp-auth.json — deleting the Tempreon entry there forces a clean re-auth.

Not sure what's failing. opencode mcp debug tempreon shows the connection attempt step by step — it usually names the problem directly.

Tools not appearing. Start a new OpenCode session after adding the config — the tool list is read at session start.

Also connect: Kiro · Claude Code · GLM

Try saying...

• "Start my session." — triggers session_start to load your Core Imprint
• "Remember: this repo uses pnpm, not npm — always." — stores a preference that follows you across models and sessions
• "Search my knowledge base for our API versioning decisions." — exercises the retrieval path end-to-end